SPF Check:
continental-corporation.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 continental-corporation.com.
The SPF record for continental-corporation.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, 66 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 23.11.2024 at 03:31:14 clock.

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

Nameserverset:
dns2.cscdns.net
dns1.cscdns.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 
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 
192.109.198.20 Continental AG blacklist 
193.29.3.213 Continental AG blacklist 
192.109.198.20 Continental AG blacklist 
174.143.181.180 RMH-14 blacklist 
193.29.3.132 Continental AG blacklist 
204.197.215.44 - blacklist 
54.66.142.68 AMAZON-02 blacklist 
93.190.68.67 dogado GmbH blacklist 
46.28.184.125 COLT Technology Services Group Limited blacklist 
192.109.216.137 - blacklist 
192.109.216.138 - blacklist 
192.109.216.139 - blacklist 
192.109.216.140 - blacklist 
198.2.128.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.132.0/22
THEROCKETSCIENCEGROUP blacklist 
198.2.136.0/23
THEROCKETSCIENCEGROUP blacklist 
198.2.186.0/23
THEROCKETSCIENCEGROUP blacklist 
205.201.131.128/25
THEROCKETSCIENCEGROUP blacklist 
205.201.134.128/25
THEROCKETSCIENCEGROUP blacklist 
205.201.136.0/23
THEROCKETSCIENCEGROUP blacklist 
205.201.139.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.180.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.179.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.178.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.177.0/24
THEROCKETSCIENCEGROUP blacklist 
167.89.0.0/17
SENDGRID blacklist 
208.117.48.0/20
SENDGRID blacklist 
50.31.32.0/19
SENDGRID blacklist 
198.37.144.0/20
SENDGRID blacklist 
198.21.0.0/21
SENDGRID blacklist 
192.254.112.0/20
SENDGRID blacklist 
168.245.0.0/17
SENDGRID blacklist 
149.72.0.0/16
AMAZON-AES blacklist 
195.66.99.135 Datagroup Se blacklist 
62.75.247.44 Host Europe GmbH blacklist 
212.227.89.57 IONOS SE blacklist 
217.160.226.166 IONOS SE blacklist 
82.165.193.1 IONOS SE blacklist 
87.79.30.25 NetCologne Gesellschaft fur Telekommunikation mbH blacklist 
85.25.144.9 velia.net Internetdienste GmbH blacklist 
91.217.141.0/24
Datagroup Se blacklist 
81.14.180.92 htp GmbH blacklist 
52.29.43.134 AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: continental-corporation.com

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

174.143.181.180
193.29.3.132
204.197.215.44
54.66.142.68
93.190.68.67
46.28.184.125
192.109.216.137
192.109.216.138
192.109.216.139
192.109.216.140
198.2.128.0/24
198.2.132.0/22
198.2.136.0/23
198.2.186.0/23
205.201.131.128/25
205.201.134.128/25
205.201.136.0/23
205.201.139.0/24
198.2.180.0/24
198.2.179.0/24
198.2.178.0/24
198.2.177.0/24
167.89.0.0/17
208.117.48.0/20
50.31.32.0/19
198.37.144.0/20
198.21.0.0/21
192.254.112.0/20
168.245.0.0/17
149.72.0.0/16
195.66.99.135
62.75.247.44
212.227.89.57
217.160.226.166
82.165.193.1
87.79.30.25
85.25.144.9
91.217.141.0/24
81.14.180.92
52.29.43.134

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.contiwan.com
v=spf1 include:spf.protection.outlook.com include:_spf.general.transactional-mail-a.com ip4:192.109.198.20 ip4:193.29.3.213 a:edge.contiwan.com -all
ipv4:
192.109.198.20
ipv4:
193.29.3.213
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.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

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:

ec2-3-65-150-226.eu-central-1.compute.amazonaws.com

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