SPF Check:
atlantic-hotels.de

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 failed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 1 Error
  •   Email Spoofing Protection: Poor
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain atlantic-hotels.de.
The SPF record for atlantic-hotels.de is not valid.
The syntax check resulted in a total of 1 errors.
of the email -Spoofing protection for this domain is not or not sufficiently provided.

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, 64 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 24.12.2024 at 01:25:09 clock.

Lookup for the domain:
atlantic-hotels.de
IP address to be checked:
no IP address specified

Have secure SPF record created by expert
from 749€

Order SPF record
  • 1. You send an email to our analysis system
  • 2. We will send you the finished SPF record
  • 3. You implement the SPF record
  • 4. We check the setup final
Have secure SPF record created by expert
from 749€

Evaluation for the domain atlantic-hotels.de 

Nameserverset:
ns2.plutex.de
ns1.plutex.de
ns3.plutex.de
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
85.25.89.5 PlusServer GmbH blacklist 
85.25.89.0/24
PlusServer GmbH blacklist 
91.250.95.64/26
PlusServer GmbH blacklist 
87.230.74.128/28
PlusServer GmbH blacklist 
91.250.74.128/27
PlusServer GmbH blacklist 
80.237.187.32/28
PlusServer GmbH blacklist 
92.51.187.64/27
PlusServer GmbH blacklist 
83.169.51.224/27
PlusServer GmbH blacklist 
104.47.14.36 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.47.12.36 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
213.23.90.98 Vodafone GmbH blacklist 
129.146.123.44 ORACLE-BMC-31898 blacklist 
129.146.58.65 ORACLE-BMC-31898 blacklist 
151.193.20.41 - blacklist 
45.132.247.71 netcup GmbH blacklist 
45.90.5.136 netcup GmbH blacklist 
45.90.5.139 netcup GmbH blacklist 
83.136.84.37 WIIT AG blacklist 
80.149.46.2 Deutsche Telekom AG blacklist 
151.193.18.41 - blacklist 
87.253.232.0/21
Mailjet SAS blacklist 
185.189.236.0/22
Mailjet SAS blacklist 
185.211.120.0/22
Mailjet SAS blacklist 
185.250.236.0/22
Mailjet SAS blacklist 
31.24.145.37 PLUTEX GmbH blacklist 
31.24.145.37 PLUTEX GmbH blacklist 
31.24.146.137 PLUTEX GmbH blacklist 
40.95.89.42 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
80.245.137.115 Bremen Briteline GmbH blacklist 
80.245.137.126 Bremen Briteline GmbH blacklist 
176.95.82.11 Vodafone GmbH blacklist 
176.95.82.16 Vodafone GmbH blacklist 
213.155.74.173 noris network AG blacklist 
212.53.206.156 Artfiles New Media GmbH blacklist 
212.53.206.157 Artfiles New Media GmbH blacklist 
212.53.206.155 Artfiles New Media GmbH blacklist 
212.53.206.155/29
Artfiles New Media GmbH 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 
35.192.181.145 GOOGLE-CLOUD-PLATFORM blacklist 
35.222.49.21 GOOGLE-CLOUD-PLATFORM blacklist 
34.132.184.222 GOOGLE-CLOUD-PLATFORM blacklist 
34.69.44.134 GOOGLE-CLOUD-PLATFORM blacklist 
35.223.170.93 GOOGLE-CLOUD-PLATFORM blacklist 
34.86.254.203 GOOGLE-CLOUD-PLATFORM blacklist 
34.85.182.168 GOOGLE-CLOUD-PLATFORM blacklist 
34.145.244.232 GOOGLE-CLOUD-PLATFORM blacklist 
34.150.215.45 GOOGLE-CLOUD-PLATFORM blacklist 
35.245.27.80 GOOGLE-CLOUD-PLATFORM blacklist 
62.113.218.162 23M GmbH blacklist 
62.113.218.163 23M GmbH blacklist 
62.113.218.164 23M GmbH blacklist 
212.83.34.223 23M GmbH blacklist 
212.83.34.224 23M GmbH blacklist 
212.83.35.22 23M GmbH blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: atlantic-hotels.de

SPF record available?

We found an SPF record for the domain.

v=spf1

Additionally authorized IPv4 addresses

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

85.25.89.5
85.25.89.0/24
91.250.95.64/26
87.230.74.128/28
91.250.74.128/27
80.237.187.32/28
92.51.187.64/27
83.169.51.224/27
104.47.14.36
104.47.12.36
213.23.90.98
129.146.123.44
129.146.58.65
151.193.20.41
45.132.247.71
45.90.5.136
45.90.5.139
83.136.84.37
80.149.46.2
151.193.18.41
87.253.232.0/21
185.189.236.0/22
185.211.120.0/22
185.250.236.0/22
31.24.145.37

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.myzechit.com
v=spf1 ip4:31.24.145.37 ip4:31.24.146.137 ip4:40.95.89.42 ip4:80.245.137.115 ip4:80.245.137.126 ip4:176.95.82.11 ip4:176.95.82.16 ip4:213.155.74.173 -all
ipv4:
31.24.145.37
ipv4:
31.24.146.137
ipv4:
40.95.89.42
ipv4:
80.245.137.115
ipv4:
80.245.137.126
ipv4:
176.95.82.11
ipv4:
176.95.82.16
ipv4:
213.155.74.173
include:reservision.com
v=spf1 mx ip4:212.53.206.155/29 -all
mx:
mail02.reservision.cmpsrv.com
mx:
mail03.reservision.cmpsrv.com
mx:
mail01.reservision.cmpsrv.com
ipv4:
212.53.206.155/29
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.synxis.com
v=spf1 ip4:35.192.181.145 ip4:35.222.49.21 ip4:34.132.184.222 ip4:34.69.44.134 ip4:35.223.170.93 ip4:34.86.254.203 ip4:34.85.182.168 ip4:34.145.244.232 ip4:34.150.215.45 ip4:35.245.27.80 include:spf.sabre.com ~all
ipv4:
35.192.181.145
ipv4:
35.222.49.21
ipv4:
34.132.184.222
ipv4:
34.69.44.134
ipv4:
35.223.170.93
ipv4:
34.86.254.203
ipv4:
34.85.182.168
ipv4:
34.145.244.232
ipv4:
34.150.215.45
ipv4:
35.245.27.80
include:spf.sabre.com
v=spf1 include:%{ir}.%{v}.spf.sabre.com.spf.has.pphosted.com -all
unknown:
include:%{ir}.%{v}.spf.sabre.com.spf.has.pphosted.com
include:spf.myincert.com
v=spf1 ip4:62.113.218.162 ip4:62.113.218.163 ip4:62.113.218.164 ip4:212.83.34.223 ip4:212.83.34.224 ip4:212.83.35.22 ~all
ipv4:
62.113.218.162
ipv4:
62.113.218.163
ipv4:
62.113.218.164
ipv4:
212.83.34.223
ipv4:
212.83.34.224
ipv4:
212.83.35.22

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.

Additionally authorized A-records?

In addition to the A-Records stored in the DNS, we could not find any other records authorized in the SPF-Record.

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:

p02.zechbau.hosting.plutex.de

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