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

The SPF record analysis was performed on 15.11.2024 at 05:49:13 clock.

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

Nameserverset:
pdns2.cscdns.net
pdns1.cscdns.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
75.2.28.136 AMAZON-02 blacklist 
52.101.68.12 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.68.5 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.73.1 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.73.22 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
192.237.159.170 RACKSPACE blacklist 
166.78.71.146 RACKSPACE blacklist 
192.237.159.44 RACKSPACE blacklist 
23.253.183.59 RACKSPACE blacklist 
212.64.225.225 Bayer AG blacklist 
212.64.225.226 Bayer AG blacklist 
192.237.159.170 RACKSPACE blacklist 
166.78.71.146 RACKSPACE blacklist 
192.237.159.44 RACKSPACE blacklist 
23.253.183.59 RACKSPACE blacklist 
164.59.136.161 Bayer AG blacklist 
164.59.136.162 Bayer AG blacklist 
164.59.136.210 Bayer AG blacklist 
164.59.136.211 Bayer AG blacklist 
164.59.136.212 Bayer AG blacklist 
164.59.136.213 Bayer AG blacklist 
164.59.136.214 Bayer AG blacklist 
164.59.136.156 Bayer AG blacklist 
164.59.136.215 Bayer AG blacklist 
164.59.136.216 Bayer AG blacklist 
164.59.136.217 Bayer AG blacklist 
164.59.136.218 Bayer AG 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 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: bayer.com

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

75.2.28.136

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

The mechanism 'mx' was set in the SPF entry. The following hosts are allowed to send

bayer-com.mail.protection.outlook.com
bayer-com.mail.protection.outlook.com
bayer-com.mail.protection.outlook.com
bayer-com.mail.protection.outlook.com

Additionally authorized IPv4 addresses

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

192.237.159.170
166.78.71.146
192.237.159.44
23.253.183.59
212.64.225.225
212.64.225.226

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.bayer.com
v=spf1 ip4:192.237.159.170 ip4:166.78.71.146 ip4:192.237.159.44 ip4:23.253.183.59 ip4:164.59.136.161 ip4:164.59.136.162 ip4:164.59.136.210 ip4:164.59.136.211 ip4:164.59.136.212 ip4:164.59.136.213 ip4:164.59.136.214 ip4:164.59.136.156 ip4:164.59.136.215 ip4:164.59.136.216 ip4:164.59.136.217 ip4:164.59.136.218 include:spf.protection.outlook.com -all
ipv4:
192.237.159.170
ipv4:
166.78.71.146
ipv4:
192.237.159.44
ipv4:
23.253.183.59
ipv4:
164.59.136.161
ipv4:
164.59.136.162
ipv4:
164.59.136.210
ipv4:
164.59.136.211
ipv4:
164.59.136.212
ipv4:
164.59.136.213
ipv4:
164.59.136.214
ipv4:
164.59.136.156
ipv4:
164.59.136.215
ipv4:
164.59.136.216
ipv4:
164.59.136.217
ipv4:
164.59.136.218
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

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)

Unknown mechanisms

Unknown mechanisms were found in the SPF record


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.

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

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:

a2466701e7639ebf3.awsglobalaccelerator.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