SPF Check:
amsterdam.nl

1. Specify domain name

Enter a domain to be checked for the SPF record
2. Specify IP address (optional)
Enter any IP address to check if it is authorized to send e-mails by the SPF record

What is the SPF lookup for?

With the SPF lookup you analyze the SPF record of a domain for errors, security risks and authorized IP addresses. Optionally, you can specify an IP address to check if it is authorized to send e-mail on behalf of the domain. The SPF lookup analyzes registered TXT records in real time. If you want to specify an SPF record manually, use the SPF Analyzer.

Loading...

SPF check passed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 0 errors
  •   Email Anti-Spoofing: Good
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain amsterdam.nl.
The SPF record for amsterdam.nl is valid.
The syntax check of the SPF record shows no obvious errors.

Which IP-s are legitimate to send emails?
The SPF record contains a reference to external rules, which means that the validity of the SPF record depends on at least one other domain. A detailed list of the rules used externally can be found in the analysis result. In total, 38 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 28.12.2024 at 06:08:05 clock.

Lookup for the domain:
amsterdam.nl
IP address to be checked:
no IP address specified
Solve your problems in no time
Guaranteed measurable improvement for email deliverability and domain security
Solve your problems in no time

Evaluation for the domain amsterdam.nl 

Nameserverset:
a6-64.akam.net
a5-65.akam.net
a1-140.akam.net
a11-64.akam.net
a12-67.akam.net
a26-65.akam.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
81.30.47.97 Signet B.V. blacklist 
176.74.239.242 Signet B.V. blacklist 
2a00:1fb8:a13:1:0:0:0:25 Destiny N.V blacklist 
37.17.212.82 Signet B.V. blacklist 
2001:4cb8:59c:1:0:0:0:25 Signet B.V. blacklist 
185.38.232.240 Comsenso BV blacklist 
195.80.226.28 Comsenso BV blacklist 
80.73.130.222/32
Network Operations B.V blacklist 
2a01:5140:a:1::100/128
Network Operations B.V blacklist 
77.87.162.30 Comsenso BV blacklist 
2a02:720:9:a1::8002 Comsenso BV blacklist 
92.42.235.1/24
Open Line BV blacklist 
195.88.136.38 Stichting Zorgring Noord Holland Noord blacklist 
195.88.136.39 Stichting Zorgring Noord Holland Noord blacklist 
195.88.137.114 Stichting Zorgring Noord Holland Noord blacklist 
195.88.137.208 Stichting Zorgring Noord Holland Noord blacklist 
213.201.213.229 GTT Communications Inc. blacklist 
40.92.0.0/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.107.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.100.0.0/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.102.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.103.0.0/17
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.47.0.0/17
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f400::/48
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403::/49
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:8000::/51
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:c000::/51
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:f000::/52
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.101.192.132 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.101.192.146 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.50.129.173 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.103.134.61 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.103.87.180 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.103.83.233 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
185.108.112.76 Signet B.V. blacklist 
20.76.46.41 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.54.177.205 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
49.12.39.70 Hetzner Online GmbH blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: amsterdam.nl

SPF record available?

We found an SPF record for the domain.

v=spf1

Additionally authorized A-records?

In addition to the A-records stored in the DNS, we were able to find further records authorized in the SPF-record

176.74.239.242
2a00:1fb8:a13:1:0:0:0:25
37.17.212.82
2001:4cb8:59c:1:0:0:0:25

Additionally authorized IPv4 addresses

Explicit IPv4 addresses in the SPF record have been authorized to send

81.30.47.97

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.iprox.nl
v=spf1 ip4:185.38.232.240 ip4:195.80.226.28 ip4:80.73.130.222/32 ip6:2a01:5140:a:1::100/128 ip4:77.87.162.30 ip6:2a02:720:9:a1::8002 -all
ipv4:
185.38.232.240
ipv4:
195.80.226.28
ipv4:
80.73.130.222/32
ipv4:
77.87.162.30
ipv6:
2a01:5140:a:1::100/128
ipv6:
2a02:720:9:a1::8002
include:_spf.zorgmail.nl
v=spf1 ip4:92.42.235.1/24 include:_spf.mailrelay.zorgring.nl -all
ipv4:
92.42.235.1/24
include:_spf.mailrelay.zorgring.nl
v=spf1 ip4:195.88.136.38 ip4:195.88.136.39 ip4:195.88.137.114 ip4:195.88.137.208 ip4:213.201.213.229 -all
ipv4:
195.88.136.38
ipv4:
195.88.136.39
ipv4:
195.88.137.114
ipv4:
195.88.137.208
ipv4:
213.201.213.229
include:spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all
ipv4:
40.92.0.0/15
ipv4:
40.107.0.0/16
ipv4:
52.100.0.0/15
ipv4:
52.102.0.0/16
ipv4:
52.103.0.0/17
ipv4:
104.47.0.0/17
ipv6:
2a01:111:f400::/48
ipv6:
2a01:111:f403::/49
ipv6:
2a01:111:f403:8000::/51
ipv6:
2a01:111:f403:c000::/51
ipv6:
2a01:111:f403:f000::/52
include:_spf.mail.services.bastion365.net
v=spf1 ip4:20.101.192.132 ip4:20.101.192.146 ip4:20.50.129.173 ip4:20.103.134.61 ip4:20.103.87.180 ip4:20.103.83.233 ip4:185.108.112.76 ip4:20.76.46.41 ip4:20.54.177.205 ip4:49.12.39.70 -all
ipv4:
20.101.192.132
ipv4:
20.101.192.146
ipv4:
20.50.129.173
ipv4:
20.103.134.61
ipv4:
20.103.87.180
ipv4:
20.103.83.233
ipv4:
185.108.112.76
ipv4:
20.76.46.41
ipv4:
20.54.177.205
ipv4:
49.12.39.70

E-Mail handling

How should the checkHost() function of the e-mail server handle the e-mail? (syntax )

-all
Fail (non-compliant e-mails are rejected)

Will be forwarded to another SPF record?

There is no reference to any other SPF record

Are the server addresses allowed to send e-mails?

In the SPF entry the mechanism 'a' has not been set.

Are the registered mail servers allowed to send e-mails?

In the SPF entry the mechanism 'mx' has not been set

Additionally authorized MX records

We could not find any other records authorized in the SPF record besides the MX records stored in the DNS

Additionally authorized IPv6 addresses

No explicit IPv6 addresses in the SPF record have been authorised to send

How is the sender informed?

The exp mechanism acts as a return to the sender if the IP address was not authorized to send and notify them. None was found.

PTR (obsolete mechanism)

The ptr mechanism is deprecated, slow and insecure and should not be used

PTR:

The ptr mechanism is deprecated, slow and insecure and should not be used

Authorize IP addresses with markers

When SPF is evaluated, macros can specifically authorize Ip addresses based on the request or connection of the user or client (RFC7208 )

Receiver address

analysis.ra-missing

Amount of reports

analysis.rp-missing

Report selection

analysis.rr-missing

Unknown mechanisms

No unknown mechanisms were found in the SPF record.

Recently performed SPF lookups

Server IP Address

We have determined the following IP address for the domain:

No domain specified

Reverse address

We have determined the following name for the server IP address:

46.17.24.110

Free whitepaper

How secure is your domain?

  • Practical with many examples
  • the basics of domain risk management summarized in 20 pages
  • Checklist with 53 questions on 14 risk areas

Get a first impression of the risk potential in your company

⮩ Download "Domain Risk Management" for free
All offers are aimed at traders, not end consumers and do not include VAT.
© 2024 nicmanager.com.   All rights reserved.
nicmanager