SPF Check: bekum.de

Check SPF record for bekum.de: ⊳Does a valid SPF record exist? ⊳What does it do? ⊳Which IPs are legitimate to send emails?

1. Specify domain name

Your data

Change specifications
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
Lookup for the domain:
bekum.de
IP address to be checked:
no IP address specified
Loading...
Summary
An SPF record was found for the domain bekum.de. The syntax check resulted in a total 1 error. The SPF record for bekum.de is not valid. The e-mail spoofing protection for this domain is not or not sufficiently available. 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 externally used "includes" can be found in the analysis result. In total 61 IP address(es) were authorized by the SPF record to send emails. The SPF record analysis was performed on 21.04.2021 at 13:42:32 clock.

Let us check your SPF record or create a valid entry
Our experts will advise you at a fixed price including risk check for your domain. Avoid the risk of third parties misusing your domain. 30 days free reviews with functional guarantee.

Evaluation for the domain bekum.de 

Nameserverset:
ns2.bytecamp.net
ns1.bytecamp.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
195.185.171.138 ecotel communication ag blacklist 
212.204.60.2 e.discom Telekommunikation GmbH blacklist 
176.9.2.16/28
Hetzner Online GmbH blacklist 
176.9.2.224/27
Hetzner Online GmbH blacklist 
176.9.9.96/27
Hetzner Online GmbH blacklist 
213.239.193.16/28
Hetzner Online GmbH blacklist 
213.239.211.16/28
Hetzner Online GmbH blacklist 
213.239.217.160/27
Hetzner Online GmbH blacklist 
213.239.218.64/27
Hetzner Online GmbH blacklist 
46.4.133.0/27
Hetzner Online GmbH blacklist 
46.4.145.79 Hetzner Online GmbH blacklist 
46.4.90.213 Hetzner Online GmbH blacklist 
78.46.111.11 Hetzner Online GmbH blacklist 
78.46.114.185 Hetzner Online GmbH blacklist 
78.46.69.0/27
Hetzner Online GmbH blacklist 
78.46.72.176/28
Hetzner Online GmbH blacklist 
78.46.88.155 Hetzner Online GmbH blacklist 
78.46.94.0/27
Hetzner Online GmbH blacklist 
78.47.17.144/29
Hetzner Online GmbH blacklist 
78.47.39.96/28
Hetzner Online GmbH blacklist 
85.10.192.136 Hetzner Online GmbH blacklist 
85.10.205.192/27
Hetzner Online GmbH blacklist 
85.10.219.104/29
Hetzner Online GmbH blacklist 
88.198.16.192/28
Hetzner Online GmbH blacklist 
88.198.244.108/30
Hetzner Online GmbH blacklist 
88.198.33.144/28
Hetzner Online GmbH blacklist 
88.198.44.92 Hetzner Online GmbH blacklist 
88.198.51.64/28
Hetzner Online GmbH blacklist 
88.198.59.96/27
Hetzner Online GmbH blacklist 
62.138.121.0/26
PlusServer GmbH blacklist 
88.198.249.64/28
Hetzner Online GmbH blacklist 
88.198.96.0/27
Hetzner Online GmbH blacklist 
212.204.60.0/24
e.discom Telekommunikation GmbH blacklist 
23.96.254.246 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.116.175.232 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.86.231.206 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.79.146.65 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
94.245.94.31 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
65.52.215.36 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.81.10.179 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.126.245.16 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.101.59.148 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.42.74.121 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.116.232.68 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.140.186.177 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.75.218.232 MICROSOFT-CORP-MSN-AS-BLOCK 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::/48
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.4.72.0/24
Microsoft Deutschland MCIO GmbH blacklist 
51.5.72.0/24
Microsoft Deutschland MCIO GmbH blacklist 
51.5.80.0/27
Microsoft Deutschland MCIO GmbH blacklist 
20.47.149.138/32
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.4.80.0/27
Microsoft Deutschland MCIO GmbH blacklist 
2a01:4180:4051:0800::/64
Microsoft Deutschland MCIO GmbH blacklist 
2a01:4180:4050:0800::/64
Microsoft Deutschland MCIO GmbH blacklist 
2a01:4180:4051:0400::/64
Microsoft Deutschland MCIO GmbH blacklist 
2a01:4180:4050:0400::/64
Microsoft Deutschland MCIO GmbH blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: bekum.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

212.204.60.2

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

mail.bekum.de

Additionally authorized IPv4 addresses

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

212.204.60.0/24

Additional external SPF records

We could find other records authorized in the SPF record

include:nl2go.com
v=spf1 include:_s0.nl2go.com include:_s1.nl2go.com include:_s2.nl2go.com -all
include:_s0.nl2go.com
v=spf1 ip4:176.9.2.16/28 ip4:176.9.2.224/27 ip4:176.9.9.96/27 ip4:213.239.193.16/28 ip4:213.239.211.16/28 ip4:213.239.217.160/27 ip4:213.239.218.64/27 ip4:46.4.133.0/27 ip4:46.4.145.79 ip4:46.4.90.213 ip4:78.46.111.11 ip4:78.46.114.185 ~all
ipv4:
176.9.2.16/28
ipv4:
176.9.2.224/27
ipv4:
176.9.9.96/27
ipv4:
213.239.193.16/28
ipv4:
213.239.211.16/28
ipv4:
213.239.217.160/27
ipv4:
213.239.218.64/27
ipv4:
46.4.133.0/27
ipv4:
46.4.145.79
ipv4:
46.4.90.213
ipv4:
78.46.111.11
ipv4:
78.46.114.185
include:_s1.nl2go.com
v=spf1 ip4:78.46.69.0/27 ip4:78.46.72.176/28 ip4:78.46.88.155 ip4:78.46.94.0/27 ip4:78.47.17.144/29 ip4:78.47.39.96/28 ip4:85.10.192.136 ip4:85.10.205.192/27 ip4:85.10.219.104/29 ip4:88.198.16.192/28 ip4:88.198.244.108/30 ip4:88.198.33.144/28 ~all
ipv4:
78.46.69.0/27
ipv4:
78.46.72.176/28
ipv4:
78.46.88.155
ipv4:
78.46.94.0/27
ipv4:
78.47.17.144/29
ipv4:
78.47.39.96/28
ipv4:
85.10.192.136
ipv4:
85.10.205.192/27
ipv4:
85.10.219.104/29
ipv4:
88.198.16.192/28
ipv4:
88.198.244.108/30
ipv4:
88.198.33.144/28
include:_s2.nl2go.com
v=spf1 ip4:88.198.44.92 ip4:88.198.51.64/28 ip4:88.198.59.96/27 ip4:62.138.121.0/26 ip4:88.198.249.64/28 ip4:88.198.96.0/27 ~all
ipv4:
88.198.44.92
ipv4:
88.198.51.64/28
ipv4:
88.198.59.96/27
ipv4:
62.138.121.0/26
ipv4:
88.198.249.64/28
ipv4:
88.198.96.0/27
include:spf.emailsignatures365.com
v=spf1 ip4:23.96.254.246 ip4:51.116.175.232 ip4:40.86.231.206 ip4:13.79.146.65 ip4:94.245.94.31 ip4:65.52.215.36 ip4:13.81.10.179 ip4:40.126.245.16 ip4:23.101.59.148 ip4:104.42.74.121 ip4:51.116.232.68 ip4:51.140.186.177 ip4:13.75.218.232 -all
ipv4:
23.96.254.246
ipv4:
51.116.175.232
ipv4:
40.86.231.206
ipv4:
13.79.146.65
ipv4:
94.245.94.31
ipv4:
65.52.215.36
ipv4:
13.81.10.179
ipv4:
40.126.245.16
ipv4:
23.101.59.148
ipv4:
104.42.74.121
ipv4:
51.116.232.68
ipv4:
51.140.186.177
ipv4:
13.75.218.232
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::/48 include:spfd.protection.outlook.com -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::/48
include:spfd.protection.outlook.com
v=spf1 ip4:51.4.72.0/24 ip4:51.5.72.0/24 ip4:51.5.80.0/27 ip4:20.47.149.138/32 ip4:51.4.80.0/27 ip6:2a01:4180:4051:0800::/64 ip6:2a01:4180:4050:0800::/64 ip6:2a01:4180:4051:0400::/64 ip6:2a01:4180:4050:0400::/64 -all
ipv4:
51.4.72.0/24
ipv4:
51.5.72.0/24
ipv4:
51.5.80.0/27
ipv4:
20.47.149.138/32
ipv4:
51.4.80.0/27
ipv6:
2a01:4180:4051:0800::/64
ipv6:
2a01:4180:4050:0800::/64
ipv6:
2a01:4180:4051:0400::/64
ipv6:
2a01:4180:4050:0400::/64

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 )

Unknown mechanisms

No unknown mechanisms were found in 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.

How secure are your domains and where are the dangers lurking?

Domain risks are often underestimated

A current study by BITKOM reports on the alarming increase in cyber attacks on German companies, the ICANN warns of attacks on the global domain name system and the Federal Office for Information Security (BSI) sees significant risk potential in dealing with domain name. Unfortunately, these risks come into play every day, although this damage could have been prevented.

What should companies know and what can they do?

Practical and with many examples, the over 20-page eBook deals with the basics of domain risk management, specifies legal obligations and deals with responsibilities and liability issues. Numerous domain risks (e.g. "Domain Hijacking") are clearly described and the risk assessment and possible consequences are discussed.

Checklist: What about my own domain risks?

The Risk Atlas supports domain managers to get a first impression of their own risk potential in the company. The checklist includes 53 questions on 14 risk areas and enables a quick introduction to the topic.

⮩ Secure white paper "Domain Risk Management" for free

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:

www-rdr.bytecamp.net

© 2012 - 2021 nicmanager.com