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

The SPF record analysis was performed on 04.03.2024 at 06:49:24 clock.

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

Nameserverset:
a.ns14.net
b.ns14.net
c.ns14.net
d.ns14.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
52.101.170.1 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.168.0 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.170.0 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.170.2 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
89.238.73.69 manitu GmbH blacklist 
217.110.33.34 COLT Technology Services Group Limited blacklist 
78.46.88.157 Hetzner Online GmbH blacklist 
62.138.82.64/26
PlusServer GmbH blacklist 
62.138.86.8/29
PlusServer GmbH blacklist 
62.138.91.0/29
PlusServer GmbH blacklist 
62.138.120.184/29
PlusServer GmbH blacklist 
62.138.121.0/26
PlusServer GmbH blacklist 
46.4.133.24 Hetzner Online GmbH blacklist 
176.9.2.230 Hetzner Online GmbH blacklist 
46.4.133.19 Hetzner Online GmbH blacklist 
62.138.90.192/26
PlusServer GmbH blacklist 
91.228.144.0/24
NovoServe B.V. blacklist 
185.182.80.48/29
NovoServe B.V. blacklist 
185.182.80.144/29
NovoServe B.V. blacklist 
185.182.80.248/29
NovoServe B.V. blacklist 
185.182.83.240/29
NovoServe B.V. blacklist 
78.47.39.96/28
Hetzner Online GmbH blacklist 
78.46.88.146 Hetzner Online GmbH blacklist 
78.46.88.156 Hetzner Online GmbH blacklist 
213.239.217.189 Hetzner Online GmbH blacklist 
78.46.114.185 Hetzner Online GmbH blacklist 
176.9.2.231 Hetzner Online GmbH blacklist 
46.4.133.23 Hetzner Online GmbH blacklist 
88.198.181.208/28
Hetzner Online GmbH blacklist 
88.198.96.0/27
Hetzner Online GmbH blacklist 
178.63.169.208/28
Hetzner Online GmbH blacklist 
88.198.249.64/28
Hetzner Online GmbH blacklist 
46.4.145.64/28
Hetzner Online GmbH blacklist 
178.63.165.160/28
Hetzner Online GmbH blacklist 
185.41.28.0/22
Sendinblue SAS blacklist 
94.143.16.0/21
Sendinblue SAS blacklist 
185.24.144.0/22
Sendinblue SAS blacklist 
153.92.224.0/19
Sendinblue SAS blacklist 
213.32.128.0/18
Sendinblue SAS blacklist 
185.107.232.0/22
Sendinblue SAS blacklist 
77.32.128.0/18
Sendinblue SAS blacklist 
77.32.192.0/19
Sendinblue SAS blacklist 
212.146.192.0/18
Sendinblue SAS blacklist 
172.246.0.0/18
Sendinblue SAS 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/14
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 
20.79.220.33 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.79.222.204 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.94.95.171 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
137.116.240.241 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: byon.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

89.238.73.69

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

byon-de.mail.protection.outlook.com
byon-de.mail.protection.outlook.com
byon-de.mail.protection.outlook.com
byon-de.mail.protection.outlook.com

Additionally authorized IPv4 addresses

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

217.110.33.34

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.nl2go.com
v=spf1 include:spf1.nl2go.com include:spf2.nl2go.com include:spf3.nl2go.com ip4:88.198.181.208/28 ip4:88.198.96.0/27 ip4:178.63.169.208/28 ip4:88.198.249.64/28 ip4:46.4.145.64/28 ip4:178.63.165.160/28 ~all
ipv4:
88.198.181.208/28
ipv4:
88.198.96.0/27
ipv4:
178.63.169.208/28
ipv4:
88.198.249.64/28
ipv4:
46.4.145.64/28
ipv4:
178.63.165.160/28
include:spf1.nl2go.com
v=spf1 ip4:78.46.88.157 ip4:62.138.82.64/26 ip4:62.138.86.8/29 ip4:62.138.91.0/29 ip4:62.138.120.184/29 ip4:62.138.121.0/26 ip4:46.4.133.24 ip4:176.9.2.230 ~all
ipv4:
78.46.88.157
ipv4:
62.138.82.64/26
ipv4:
62.138.86.8/29
ipv4:
62.138.91.0/29
ipv4:
62.138.120.184/29
ipv4:
62.138.121.0/26
ipv4:
46.4.133.24
ipv4:
176.9.2.230
include:spf2.nl2go.com
v=spf1 ip4:46.4.133.19 ip4:62.138.90.192/26 ip4:91.228.144.0/24 ~all
ipv4:
46.4.133.19
ipv4:
62.138.90.192/26
ipv4:
91.228.144.0/24
include:spf3.nl2go.com
v=spf1 ip4:185.182.80.48/29 ip4:185.182.80.144/29 ip4:185.182.80.248/29 ip4:185.182.83.240/29 ip4:78.47.39.96/28 ip4:78.46.88.146 ip4:78.46.88.156 ip4:213.239.217.189 ip4:78.46.114.185 ip4:176.9.2.231 ip4:46.4.133.23 ~all
ipv4:
185.182.80.48/29
ipv4:
185.182.80.144/29
ipv4:
185.182.80.248/29
ipv4:
185.182.83.240/29
ipv4:
78.47.39.96/28
ipv4:
78.46.88.146
ipv4:
78.46.88.156
ipv4:
213.239.217.189
ipv4:
78.46.114.185
ipv4:
176.9.2.231
ipv4:
46.4.133.23
include:spf.sendinblue.com
v=spf1 ip4:185.41.28.0/22 ip4:94.143.16.0/21 ip4:185.24.144.0/22 ip4:153.92.224.0/19 ip4:213.32.128.0/18 ip4:185.107.232.0/22 ip4:77.32.128.0/18 ip4:77.32.192.0/19 ip4:212.146.192.0/18 ip4:172.246.0.0/18 -all
ipv4:
185.41.28.0/22
ipv4:
94.143.16.0/21
ipv4:
185.24.144.0/22
ipv4:
153.92.224.0/19
ipv4:
213.32.128.0/18
ipv4:
185.107.232.0/22
ipv4:
77.32.128.0/18
ipv4:
77.32.192.0/19
ipv4:
212.146.192.0/18
ipv4:
172.246.0.0/18
include:spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/14 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/14
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-de.emailsignatures365.com
v=spf1 ip4:20.79.220.33 ip4:20.79.222.204 ip4:13.94.95.171 ip4:137.116.240.241 -all
ipv4:
20.79.220.33
ipv4:
20.79.222.204
ipv4:
13.94.95.171
ipv4:
137.116.240.241

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

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

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:

ngcobalt369.manitu.net

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   Powered by Team Internet