SPF Check:
noz-mhn.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: 3 Error
  •   Email Spoofing Protection: Poor
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain noz-mhn.de.
The SPF record for noz-mhn.de is not valid.
The syntax check resulted in a total of 3 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, 103 IP address(es) were authorized by the SPF record to send emails. 20 of these are not taken into account by the Mail Transfer Agent evaluation and are not authorized to send emails on behalf of the domain.

The SPF record analysis was performed on 09.10.2024 at 11:27:08 clock.

Lookup for the domain:
noz-mhn.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 noz-mhn.de 

Nameserverset:
ns2.basecom.de
ns1.basecom.de
ns3.basecom.de
ns4.basecom.de
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
5.75.215.54 Hetzner Online GmbH blacklist 
77.72.11.64/28
medien holding:nord gmbh blacklist 
77.72.14.64/28
medien holding:nord gmbh blacklist 
77.72.13.80/28
medien holding:nord gmbh blacklist 
212.95.117.8 EWE-Tel GmbH blacklist 
194.223.48.16/28
TPG Telecom Limited blacklist 
194.195.3.64/28
PlusServer GmbH blacklist 
194.64.241.66/32
PlusServer GmbH blacklist 
85.222.138.224/28
SALESFORCE blacklist 
46.189.58.169/32
1&1 Versatel Deutschland GmbH blacklist 
85.199.66.169/32
e.discom Telekommunikation GmbH blacklist 
195.50.178.169/32
Vodafone GmbH blacklist 
91.90.156.215/32
WIIT AG blacklist 
178.77.111.91/32
Host Europe GmbH blacklist 
157.97.106.193 IONOS SE blacklist 
80.190.118.0/24
NorthC Deutschland GmbH blacklist 
80.190.129.128/25
NorthC Deutschland GmbH blacklist 
80.190.157.128/25
NorthC Deutschland GmbH blacklist 
35.190.247.0/24
GOOGLE-CLOUD-PLATFORM blacklist 
64.233.160.0/19
GOOGLE blacklist 
66.102.0.0/20
GOOGLE blacklist 
66.249.80.0/20
GOOGLE blacklist 
72.14.192.0/18
GOOGLE blacklist 
74.125.0.0/16
GOOGLE blacklist 
108.177.8.0/21
GOOGLE blacklist 
173.194.0.0/16
GOOGLE blacklist 
209.85.128.0/17
GOOGLE blacklist 
216.58.192.0/19
GOOGLE blacklist 
216.239.32.0/19
GOOGLE blacklist 
2001:4860:4000::/36
GOOGLE blacklist 
2404:6800:4000::/36
GOOGLE blacklist 
2607:f8b0:4000::/36
GOOGLE blacklist 
2800:3f0:4000::/36
GOOGLE blacklist 
2a00:1450:4000::/36
GOOGLE blacklist 
2c0f:fb50:4000::/36
GOOGLE blacklist 
172.217.0.0/19
GOOGLE blacklist 
172.217.32.0/20
GOOGLE blacklist 
172.217.128.0/19
GOOGLE blacklist 
172.217.160.0/20
GOOGLE blacklist 
172.217.192.0/19
GOOGLE blacklist 
172.253.56.0/21
GOOGLE blacklist 
172.253.112.0/20
GOOGLE blacklist 
108.177.96.0/19
GOOGLE blacklist 
35.191.0.0/16
GOOGLE blacklist 
130.211.0.0/22
GOOGLE-CLOUD-PLATFORM blacklist 
94.199.92.0/23
retarus GmbH blacklist 
103.196.252.0/23
retarus GmbH blacklist 
185.93.140.0/22
retarus GmbH blacklist 
185.215.216.0/22
retarus GmbH blacklist 
207.126.136.0/22
retarus GmbH blacklist 
199.204.12.0/22
retarus GmbH blacklist 
2a02:7b01:0:42::1:0/114
retarus GmbH blacklist 
2a02:7b01:1000:42::1:0/114
retarus GmbH blacklist 
2a02:7b01:2000:42::1:0/114
retarus GmbH blacklist 
2a02:7b02:2000:42::1:0/114
retarus GmbH blacklist 
2a02:7b02:0:42::1:0/114
retarus GmbH blacklist 
2a02:7b03:0:42::1:0/114
retarus GmbH blacklist 
62.204.93.131 Prolocation B.V. blacklist 
207.244.98.227 LEASEWEB-USA-WDC blacklist 
83.149.98.72 LeaseWeb Netherlands B.V. blacklist 
81.17.56.1 Leaseweb UK Limited blacklist 
83.149.98.73 LeaseWeb Netherlands B.V. blacklist 
13.88.226.191 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.115.66.46 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.94.232.90 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
191.238.213.99 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.13.102.144 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
178.162.177.161 LeaseWeb Netherlands B.V. blacklist 
13.74.56.125 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
4.185.96.20 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.162.206.62 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
172.172.139.18 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
4.223.229.111 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
209.61.151.0/24
RMH-14 blacklist 
166.78.68.0/22
RACKSPACE blacklist 
198.61.254.0/23
RACKSPACE blacklist 
192.237.158.0/23
RACKSPACE blacklist 
23.253.182.0/23
RACKSPACE blacklist 
104.130.96.0/28
RACKSPACE blacklist 
146.20.113.0/24
RACKSPACE blacklist 
146.20.191.0/24
RACKSPACE blacklist 
159.135.224.0/20
RACKSPACE blacklist 
69.72.32.0/20
RACKSPACE blacklist 
104.130.122.0/23
RACKSPACE blacklist 
146.20.112.0/26
RACKSPACE blacklist 
161.38.192.0/20
MAILGUN blacklist 
143.55.224.0/21
MAILGUN blacklist 
143.55.232.0/22
MAILGUN blacklist 
159.112.240.0/20
MAILGUN blacklist 
198.244.48.0/20
MAILGUN blacklist 
204.220.168.0/21
VOYANT blacklist 
204.220.176.0/20
MAILGUN blacklist 
141.193.32.0/23
AMAZON-02 blacklist 
159.135.140.80/29
Rackspace Ltd. blacklist 
159.135.132.128/25
Rackspace Ltd. blacklist 
161.38.204.0/22
AMAZON-02 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 
143.55.236.0/22
Mailjet SAS blacklist 
198.244.60.0/22
Mailjet SAS blacklist 
204.220.160.0/21
Mailjet SAS blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: noz-mhn.de

SPF record available?

We found an SPF record for the domain.

v=spf1

Are the server addresses allowed to send e-mails?

The mechanism 'a' was set in the SPF record. The following IP addresses are allowed to send

5.75.215.54

Additionally authorized IPv4 addresses

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

77.72.11.64/28
77.72.14.64/28
77.72.13.80/28
212.95.117.8
194.223.48.16/28
194.195.3.64/28
194.64.241.66/32
85.222.138.224/28
46.189.58.169/32
85.199.66.169/32
195.50.178.169/32
91.90.156.215/32
178.77.111.91/32
157.97.106.193

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.senders.scnem.com
v=spf1 ip4:80.190.118.0/24 ip4:80.190.129.128/25 ip4:80.190.157.128/25 -all
ipv4:
80.190.118.0/24
ipv4:
80.190.129.128/25
ipv4:
80.190.157.128/25
include:_spf.google.com
v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com ~all
include:_netblocks.google.com
v=spf1 ip4:35.190.247.0/24 ip4:64.233.160.0/19 ip4:66.102.0.0/20 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:74.125.0.0/16 ip4:108.177.8.0/21 ip4:173.194.0.0/16 ip4:209.85.128.0/17 ip4:216.58.192.0/19 ip4:216.239.32.0/19 ~all
ipv4:
35.190.247.0/24
ipv4:
64.233.160.0/19
ipv4:
66.102.0.0/20
ipv4:
66.249.80.0/20
ipv4:
72.14.192.0/18
ipv4:
74.125.0.0/16
ipv4:
108.177.8.0/21
ipv4:
173.194.0.0/16
ipv4:
209.85.128.0/17
ipv4:
216.58.192.0/19
ipv4:
216.239.32.0/19
include:_netblocks2.google.com
v=spf1 ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 ip6:2607:f8b0:4000::/36 ip6:2800:3f0:4000::/36 ip6:2a00:1450:4000::/36 ip6:2c0f:fb50:4000::/36 ~all
ipv6:
2001:4860:4000::/36
ipv6:
2404:6800:4000::/36
ipv6:
2607:f8b0:4000::/36
ipv6:
2800:3f0:4000::/36
ipv6:
2a00:1450:4000::/36
ipv6:
2c0f:fb50:4000::/36
include:_netblocks3.google.com
v=spf1 ip4:172.217.0.0/19 ip4:172.217.32.0/20 ip4:172.217.128.0/19 ip4:172.217.160.0/20 ip4:172.217.192.0/19 ip4:172.253.56.0/21 ip4:172.253.112.0/20 ip4:108.177.96.0/19 ip4:35.191.0.0/16 ip4:130.211.0.0/22 ~all
ipv4:
172.217.0.0/19
ipv4:
172.217.32.0/20
ipv4:
172.217.128.0/19
ipv4:
172.217.160.0/20
ipv4:
172.217.192.0/19
ipv4:
172.253.56.0/21
ipv4:
172.253.112.0/20
ipv4:
108.177.96.0/19
ipv4:
35.191.0.0/16
ipv4:
130.211.0.0/22
include:_spf.general.transactional-mail-a.com
v=spf1 ip4:94.199.92.0/23 ip4:103.196.252.0/23 ip4:185.93.140.0/22 ip4:185.215.216.0/22 ip4:207.126.136.0/22 ip4:199.204.12.0/22 ip6:2a02:7b01:0:42::1:0/114 ip6:2a02:7b01:1000:42::1:0/114 ip6:2a02:7b01:2000:42::1:0/114 ip6:2a02:7b02:2000:42::1:0/114 ip6:2a02:7b02:0:42::1:0/114 ip6:2a02:7b03:0:42::1:0/114 ~all
ipv4:
94.199.92.0/23
ipv4:
103.196.252.0/23
ipv4:
185.93.140.0/22
ipv4:
185.215.216.0/22
ipv4:
207.126.136.0/22
ipv4:
199.204.12.0/22
ipv6:
2a02:7b01:0:42::1:0/114
ipv6:
2a02:7b01:1000:42::1:0/114
ipv6:
2a02:7b01:2000:42::1:0/114
ipv6:
2a02:7b02:2000:42::1:0/114
ipv6:
2a02:7b02:0:42::1:0/114
ipv6:
2a02:7b03:0:42::1:0/114
include:spf.topdesk.net
v=spf1 ip4:62.204.93.131 ip4:207.244.98.227 ip4:83.149.98.72 ip4:81.17.56.1 ip4:83.149.98.73 ip4:13.88.226.191 ip4:40.115.66.46 ip4:13.94.232.90 ip4:191.238.213.99 ip4:51.13.102.144 ip4:178.162.177.161 ip4:13.74.56.125 ip4:4.185.96.20 ip4:20.162.206.62 ip4:172.172.139.18 ip4:4.223.229.111 -all
ipv4:
62.204.93.131
ipv4:
207.244.98.227
ipv4:
83.149.98.72
ipv4:
81.17.56.1
ipv4:
83.149.98.73
ipv4:
13.88.226.191
ipv4:
40.115.66.46
ipv4:
13.94.232.90
ipv4:
191.238.213.99
ipv4:
51.13.102.144
ipv4:
178.162.177.161
ipv4:
13.74.56.125
ipv4:
4.185.96.20
ipv4:
20.162.206.62
ipv4:
172.172.139.18
ipv4:
4.223.229.111
include:_spf.mailgun.org
v=spf1 include:_spf1.mailgun.org include:_spf2.mailgun.org ~all
include:_spf1.mailgun.org
v=spf1 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ~all
ipv4:
209.61.151.0/24
ipv4:
166.78.68.0/22
ipv4:
198.61.254.0/23
ipv4:
192.237.158.0/23
ipv4:
23.253.182.0/23
ipv4:
104.130.96.0/28
ipv4:
146.20.113.0/24
ipv4:
146.20.191.0/24
ipv4:
159.135.224.0/20
ipv4:
69.72.32.0/20
include:_spf2.mailgun.org
v=spf1 ip4:104.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ~all
ipv4:
104.130.122.0/23
ipv4:
146.20.112.0/26
ipv4:
161.38.192.0/20
ipv4:
143.55.224.0/21
ipv4:
143.55.232.0/22
ipv4:
159.112.240.0/20
ipv4:
198.244.48.0/20
ipv4:
204.220.168.0/21
ipv4:
204.220.176.0/20
include:_spf.eu.mailgun.org
v=spf1 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.60.0/22 ip4:204.220.160.0/21 ~all
ipv4:
141.193.32.0/23
ipv4:
159.135.140.80/29
ipv4:
159.135.132.128/25
ipv4:
161.38.204.0/22
ipv4:
87.253.232.0/21
ipv4:
185.189.236.0/22
ipv4:
185.211.120.0/22
ipv4:
185.250.236.0/22
ipv4:
143.55.236.0/22
ipv4:
198.244.60.0/22
ipv4:
204.220.160.0/21

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

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:

sa17.serverdomain.org

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