SPF Check:
schott.com

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

The SPF record analysis was performed on 04.11.2024 at 19:23:39 clock.

Lookup for the domain:
schott.com
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 schott.com 

Nameserverset:
ns01.brandshelter.com
ns02.brandshelter.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
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 
130.214.193.83/32
SAP SE blacklist 
130.214.193.93/32
SAP SE blacklist 
130.214.193.78/32
SAP SE blacklist 
130.214.193.85/32
SAP SE blacklist 
130.214.156.205/32
SAP SE blacklist 
130.214.156.249/32
SAP SE blacklist 
212.184.68.48 Deutsche Telekom AG blacklist 
91.207.162.23 Atos Information Technology GmbH blacklist 
162.55.222.93 Hetzner Online GmbH blacklist 
212.113.29.157 LEVEL3 blacklist 
212.113.29.158 LEVEL3 blacklist 
91.207.162.20 Atos Information Technology GmbH blacklist 
212.71.111.45 EveryWare AG blacklist 
212.103.71.210 NTS workspace AG blacklist 
146.177.4.183 Rackspace Ltd. blacklist 
89.202.109.2 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
217.92.158.246 Deutsche Telekom AG blacklist 
62.26.194.3 ecotel communication ag blacklist 
62.27.11.133 ecotel communication ag blacklist 
148.139.1.31 SNC blacklist 
37.98.232.12 - blacklist 
199.91.137.2 - blacklist 
199.91.136.26 SNC blacklist 
148.139.142.17 SNC blacklist 
199.91.139.22 SNC blacklist 
148.139.142.19 SNC blacklist 
199.91.139.24 SNC blacklist 
148.139.2.2 SNC blacklist 
199.91.139.23 SNC blacklist 
199.91.137.26 - blacklist 
199.91.141.23 SNC blacklist 
199.91.140.26 SNC blacklist 
148.139.142.18 SNC blacklist 
148.139.1.2 SNC blacklist 
37.98.232.2 - blacklist 
199.91.136.28 SNC blacklist 
148.139.143.19 SNC blacklist 
37.98.234.2 SNC blacklist 
199.91.139.145 SNC blacklist 
148.139.143.20 SNC blacklist 
148.139.142.20 SNC blacklist 
199.91.141.22 SNC blacklist 
148.139.143.17 SNC blacklist 
148.139.143.18 SNC blacklist 
37.98.235.2 SNC blacklist 
199.91.141.24 SNC blacklist 
37.98.232.26 - blacklist 
199.91.141.145 SNC blacklist 
148.139.0.31 SNC blacklist 
148.139.3.2 SNC blacklist 
149.96.13.2 SNC blacklist 
148.139.0.2 SNC blacklist 
199.91.140.28 SNC blacklist 
149.96.14.2 SNC blacklist 
46.29.101.2 T-Systems International GmbH blacklist 
217.150.155.10 T-Systems International GmbH blacklist 
46.29.101.1 T-Systems International GmbH blacklist 
94.100.254.155 T-Systems International GmbH blacklist 
217.150.155.12 T-Systems International GmbH blacklist 
103.28.42.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
146.88.28.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
163.47.180.0/22
AMAZON-AES blacklist 
203.55.21.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
204.75.142.0/24
CAMPAIGN MONITOR PTY LTD blacklist 
27.126.146.0/24
CAMPAIGN MONITOR PTY LTD 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 
198.207.147.224/27
AMAZON-02 blacklist 
204.239.0.224/27
AMAZON-02 blacklist 
216.230.14.224/27
AMAZON-AES blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: schott.com

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

212.184.68.48
91.207.162.23
162.55.222.93
212.113.29.157
212.113.29.158
91.207.162.20
212.71.111.45
212.103.71.210
146.177.4.183
89.202.109.2
217.92.158.246
62.26.194.3
62.27.11.133
148.139.1.31
37.98.232.12
199.91.137.2
199.91.136.26
148.139.142.17
199.91.139.22
148.139.142.19
199.91.139.24
148.139.2.2
199.91.139.23
199.91.137.26
199.91.141.23
199.91.140.26
148.139.142.18
148.139.1.2
37.98.232.2
199.91.136.28
148.139.143.19
37.98.234.2
199.91.139.145
148.139.143.20
148.139.142.20
199.91.141.22
148.139.143.17
148.139.143.18
37.98.235.2
199.91.141.24
37.98.232.26
199.91.141.145
148.139.0.31
148.139.3.2
149.96.13.2
148.139.0.2
199.91.140.28
149.96.14.2
46.29.101.2
217.150.155.10
46.29.101.1
94.100.254.155
217.150.155.12

Additionally authorized IPv4 addresses

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

198.207.147.224/27
204.239.0.224/27
216.230.14.224/27

Additional external SPF records

We could find other records authorized in the SPF record

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-dc33.sapsf.eu
v=spf1 ip4:130.214.193.83/32 ip4:130.214.193.93/32 ip4:130.214.193.78/32 ip4:130.214.193.85/32 ip4:130.214.156.205/32 ip4:130.214.156.249/32 -all
ipv4:
130.214.193.83/32
ipv4:
130.214.193.93/32
ipv4:
130.214.193.78/32
ipv4:
130.214.193.85/32
ipv4:
130.214.156.205/32
ipv4:
130.214.156.249/32
include:_spf.createsend.com
v=spf1 ip4:103.28.42.0/24 ip4:146.88.28.0/24 ip4:163.47.180.0/22 ip4:203.55.21.0/24 ip4:204.75.142.0/24 ip4:27.126.146.0/24 ~all
ipv4:
103.28.42.0/24
ipv4:
146.88.28.0/24
ipv4:
163.47.180.0/22
ipv4:
203.55.21.0/24
ipv4:
204.75.142.0/24
ipv4:
27.126.146.0/24
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

E-Mail handling

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

~all
SoftFail (non-compliant e-mails are accepted but marked)

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:

51.124.138.175

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