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.
Does a valid SPF record exist?
An SPF record was found for the domain natek.email.
The SPF record for natek.email is not valid.
The syntax check resulted in a total of 60 errors.
of the email -Spoofing protection for this domain is not or not sufficiently provided.
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, 190 IP address(es) were authorized by the SPF record to send emails.
181 of these are not taken into account by the Mail Transfer Agent evaluation and are not authorized to send emails on behalf of the domain.
The SPF record analysis was performed on 01.07.2025 at 21:12:31 clock.
Have secure SPF record created by expert
from 749€
| IP | Provider / ASN | DNSBL-Check | ||
|---|---|---|---|---|
| 94.23.164.216 | OVH SAS | blacklist | ||
| 84.19.173.138 | Keyweb AG | blacklist | ||
| 84.19.173.138 | Keyweb AG | blacklist | ||
| 212.123.34.110 | EPAG Domainservices GmbH | blacklist | ||
| 212.123.36.25 | EPAG Domainservices GmbH | blacklist | ||
| 94.23.164.216 | OVH SAS | blacklist | ||
| 88.198.47.105 | Hetzner Online GmbH | blacklist | ||
| 84.19.180.12 | Keyweb AG | blacklist | ||
| 88.198.47.105 | Hetzner Online GmbH | blacklist | ||
| 84.19.180.12 | Keyweb AG | blacklist | ||
| 144.76.86.250 | Hetzner Online GmbH | blacklist | ||
| 94.23.164.216 | OVH SAS | blacklist | ||
| 94.23.164.183 | OVH SAS | blacklist | ||
| 54.37.212.106 | OVH SAS | blacklist | ||
| 84.19.173.138 | Keyweb AG | blacklist | ||
| 66.102.0.0/21
|
blacklist | |||
| 66.249.80.0/20
|
blacklist | |||
| 72.14.192.0/18
|
blacklist | |||
| 74.125.0.0/16
|
blacklist | |||
| 108.177.8.0/21
|
blacklist | |||
| 173.194.0.0/16
|
blacklist | |||
| 209.85.128.0/17
|
blacklist | |||
| 216.58.192.0/19
|
blacklist | |||
| 216.239.32.0/19
|
blacklist | |||
| 2001:4860:4000::/36
|
blacklist | |||
| 2404:6800:4000::/36
|
blacklist | |||
| 2607:f8b0:4000::/36
|
blacklist | |||
| 2800:3f0:4000::/36
|
blacklist | |||
| 2a00:1450:4000::/36
|
blacklist | |||
| 2c0f:fb50:4000::/36
|
blacklist | |||
| 172.217.0.0/19
|
blacklist | |||
| 172.217.32.0/20
|
blacklist | |||
| 172.217.128.0/19
|
blacklist | |||
| 172.217.160.0/20
|
blacklist | |||
| 172.217.192.0/19
|
blacklist | |||
| 172.253.56.0/21
|
blacklist | |||
| 172.253.112.0/20
|
blacklist | |||
| 108.177.96.0/19
|
blacklist | |||
| 66.102.0.0/21
|
blacklist | |||
| 66.249.80.0/20
|
blacklist | |||
| 72.14.192.0/18
|
blacklist | |||
| 74.125.0.0/16
|
blacklist | |||
| 108.177.8.0/21
|
blacklist | |||
| 173.194.0.0/16
|
blacklist | |||
| 209.85.128.0/17
|
blacklist | |||
| 216.58.192.0/19
|
blacklist | |||
| 216.239.32.0/19
|
blacklist | |||
| 2001:4860:4000::/36
|
blacklist | |||
| 2404:6800:4000::/36
|
blacklist | |||
| 2607:f8b0:4000::/36
|
blacklist | |||
| 2800:3f0:4000::/36
|
blacklist | |||
| 2a00:1450:4000::/36
|
blacklist | |||
| 2c0f:fb50:4000::/36
|
blacklist | |||
| 172.217.0.0/19
|
blacklist | |||
| 172.217.32.0/20
|
blacklist | |||
| 172.217.128.0/19
|
blacklist | |||
| 172.217.160.0/20
|
blacklist | |||
| 172.217.192.0/19
|
blacklist | |||
| 172.253.56.0/21
|
blacklist | |||
| 172.253.112.0/20
|
blacklist | |||
| 108.177.96.0/19
|
blacklist | |||
| 66.102.0.0/21
|
blacklist | |||
| 66.249.80.0/20
|
blacklist | |||
| 72.14.192.0/18
|
blacklist | |||
| 74.125.0.0/16
|
blacklist | |||
| 108.177.8.0/21
|
blacklist | |||
| 173.194.0.0/16
|
blacklist | |||
| 209.85.128.0/17
|
blacklist | |||
| 216.58.192.0/19
|
blacklist | |||
| 216.239.32.0/19
|
blacklist | |||
| 2001:4860:4000::/36
|
blacklist | |||
| 2404:6800:4000::/36
|
blacklist | |||
| 2607:f8b0:4000::/36
|
blacklist | |||
| 2800:3f0:4000::/36
|
blacklist | |||
| 2a00:1450:4000::/36
|
blacklist | |||
| 2c0f:fb50:4000::/36
|
blacklist | |||
| 172.217.0.0/19
|
blacklist | |||
| 172.217.32.0/20
|
blacklist | |||
| 172.217.128.0/19
|
blacklist | |||
| 172.217.160.0/20
|
blacklist | |||
| 172.217.192.0/19
|
blacklist | |||
| 172.253.56.0/21
|
blacklist | |||
| 172.253.112.0/20
|
blacklist | |||
| 108.177.96.0/19
|
blacklist | |||
| 87.118.88.220 | Keyweb AG | blacklist | ||
| 84.19.180.12 | Keyweb AG | blacklist | ||
| 88.198.47.105 | Hetzner Online GmbH | blacklist | ||
| 84.19.180.12 | Keyweb AG | blacklist | ||
| 144.76.86.250 | Hetzner Online GmbH | blacklist | ||
| 94.23.164.216 | OVH SAS | blacklist | ||
| 94.23.164.183 | OVH SAS | blacklist | ||
| 54.37.212.106 | OVH SAS | blacklist | ||
| 84.19.173.138 | Keyweb AG | blacklist | ||
| 66.102.0.0/21
|
blacklist | |||
| 66.249.80.0/20
|
blacklist | |||
| 72.14.192.0/18
|
blacklist | |||
| 74.125.0.0/16
|
blacklist | |||
| 108.177.8.0/21
|
blacklist | |||
| 173.194.0.0/16
|
blacklist | |||
| 209.85.128.0/17
|
blacklist | |||
| 216.58.192.0/19
|
blacklist | |||
| 216.239.32.0/19
|
blacklist | |||
| 2001:4860:4000::/36
|
blacklist | |||
| 2404:6800:4000::/36
|
blacklist | |||
| 2607:f8b0:4000::/36
|
blacklist | |||
| 2800:3f0:4000::/36
|
blacklist | |||
| 2a00:1450:4000::/36
|
blacklist | |||
| 2c0f:fb50:4000::/36
|
blacklist | |||
| 172.217.0.0/19
|
blacklist | |||
| 172.217.32.0/20
|
blacklist | |||
| 172.217.128.0/19
|
blacklist | |||
| 172.217.160.0/20
|
blacklist | |||
| 172.217.192.0/19
|
blacklist | |||
| 172.253.56.0/21
|
blacklist | |||
| 172.253.112.0/20
|
blacklist | |||
| 108.177.96.0/19
|
blacklist | |||
| 66.102.0.0/21
|
blacklist | |||
| 66.249.80.0/20
|
blacklist | |||
| 72.14.192.0/18
|
blacklist | |||
| 74.125.0.0/16
|
blacklist | |||
| 108.177.8.0/21
|
blacklist | |||
| 173.194.0.0/16
|
blacklist | |||
| 209.85.128.0/17
|
blacklist | |||
| 216.58.192.0/19
|
blacklist | |||
| 216.239.32.0/19
|
blacklist | |||
| 2001:4860:4000::/36
|
blacklist | |||
| 2404:6800:4000::/36
|
blacklist | |||
| 2607:f8b0:4000::/36
|
blacklist | |||
| 2800:3f0:4000::/36
|
blacklist | |||
| 2a00:1450:4000::/36
|
blacklist | |||
| 2c0f:fb50:4000::/36
|
blacklist | |||
| 172.217.0.0/19
|
blacklist | |||
| 172.217.32.0/20
|
blacklist | |||
| 172.217.128.0/19
|
blacklist | |||
| 172.217.160.0/20
|
blacklist | |||
| 172.217.192.0/19
|
blacklist | |||
| 172.253.56.0/21
|
blacklist | |||
| 172.253.112.0/20
|
blacklist | |||
| 108.177.96.0/19
|
blacklist | |||
| 66.102.0.0/21
|
blacklist | |||
| 66.249.80.0/20
|
blacklist | |||
| 72.14.192.0/18
|
blacklist | |||
| 74.125.0.0/16
|
blacklist | |||
| 108.177.8.0/21
|
blacklist | |||
| 173.194.0.0/16
|
blacklist | |||
| 209.85.128.0/17
|
blacklist | |||
| 216.58.192.0/19
|
blacklist | |||
| 216.239.32.0/19
|
blacklist | |||
| 2001:4860:4000::/36
|
blacklist | |||
| 2404:6800:4000::/36
|
blacklist | |||
| 2607:f8b0:4000::/36
|
blacklist | |||
| 2800:3f0:4000::/36
|
blacklist | |||
| 2a00:1450:4000::/36
|
blacklist | |||
| 2c0f:fb50:4000::/36
|
blacklist | |||
| 172.217.0.0/19
|
blacklist | |||
| 172.217.32.0/20
|
blacklist | |||
| 172.217.128.0/19
|
blacklist | |||
| 172.217.160.0/20
|
blacklist | |||
| 172.217.192.0/19
|
blacklist | |||
| 172.253.56.0/21
|
blacklist | |||
| 172.253.112.0/20
|
blacklist | |||
| 108.177.96.0/19
|
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
|
- | 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
|
- | 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 |
|
(natek.email) The SPF record of the domain exceeds the DNS lookup limit (49/10)!
At natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de include:frgra07.bieber.com.de - A the limit is exceeded (RFC7208):
1: natek.email - A 2: natek.email - MX 3: natek.email - A 4: natek.email include:mailgw.serverpool24.de 5: natek.email include:mailgw.serverpool24.de - MX 6: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de 7: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de - MX 8: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de 9: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de - MX 10: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de include:frgra07.bieber.com.de 11: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de include:frgra07.bieber.com.de - A 12: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de include:frgra07.bieber.com.de - MX 13: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de include:_spf.google.com 14: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de include:_spf.google.com include:_netblocks.google.com 15: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de include:_spf.google.com include:_netblocks2.google.com 16: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:defsn02.serverpool24.de include:_spf.google.com include:_netblocks3.google.com 17: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:_spf.google.com 18: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:_spf.google.com include:_netblocks.google.com 19: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:_spf.google.com include:_netblocks2.google.com 20: natek.email include:mailgw.serverpool24.de include:deerf05.serverpool24.de include:_spf.google.com include:_netblocks3.google.com 21: natek.email include:mailgw.serverpool24.de include:sys01.natek-server.de 22: natek.email include:mailgw.serverpool24.de include:sys01.natek-server.de include:_spf.google.com 23: natek.email include:mailgw.serverpool24.de include:sys01.natek-server.de include:_spf.google.com include:_netblocks.google.com 24: natek.email include:mailgw.serverpool24.de include:sys01.natek-server.de include:_spf.google.com include:_netblocks2.google.com 25: natek.email include:mailgw.serverpool24.de include:sys01.natek-server.de include:_spf.google.com include:_netblocks3.google.com 26: natek.email include:mailgw.serverpool24.de include:sys01.natek-server.de - A 27: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de 28: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de - MX 29: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de 30: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de - MX 31: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de include:frgra07.bieber.com.de 32: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de include:frgra07.bieber.com.de - A 33: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de include:frgra07.bieber.com.de - MX 34: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de include:_spf.google.com 35: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de include:_spf.google.com include:_netblocks.google.com 36: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de include:_spf.google.com include:_netblocks2.google.com 37: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:defsn02.serverpool24.de include:_spf.google.com include:_netblocks3.google.com 38: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:_spf.google.com 39: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:_spf.google.com include:_netblocks.google.com 40: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:_spf.google.com include:_netblocks2.google.com 41: natek.email include:mailgw.serverpool24.de include:deerf06.serverpool24.de include:_spf.google.com include:_netblocks3.google.com 42: natek.email include:mailgw.serverpool24.de include:_spf.google.com 43: natek.email include:mailgw.serverpool24.de include:_spf.google.com include:_netblocks.google.com 44: natek.email include:mailgw.serverpool24.de include:_spf.google.com include:_netblocks2.google.com 45: natek.email include:mailgw.serverpool24.de include:_spf.google.com include:_netblocks3.google.com 46: natek.email include:spf.nl2go.com 47: natek.email include:spf.nl2go.com include:spf1.nl2go.com 48: natek.email include:spf.nl2go.com include:spf2.nl2go.com 49: natek.email include:spf.nl2go.com include:spf3.nl2go.com |
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → _spf.google.com) Invalid mechanisms in SPF-Record!
'include:_netblocks.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 21)!
'include:_netblocks2.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 22)!
'include:_netblocks3.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 23)!
OK for 'v' -> 'spf1'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → _spf.google.com) Invalid mechanisms in SPF-Record!
'include:_netblocks.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 40)!
'include:_netblocks2.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 41)!
'include:_netblocks3.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 42)!
OK for 'v' -> 'spf1'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → frgra07.bieber.com.de) Invalid mechanisms in SPF-Record!
'a:spf1' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 36)!
'mx' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 37)!
Endlosschleife bei 'include:mailgw.serverpool24.de':
Trace: natek.email-> include:mailgw.serverpool24.de-> include:deerf06.serverpool24.de-> include:defsn02.serverpool24.de-> include:frgra07.bieber.com.de-> include:mailgw.serverpool24.de
'mx' cannot be resolved (IPv4)
OK for 'v' -> 'spf1'
OK for 'a'
OK for 'ip4' -> '94.23.164.183'
OK for 'ip4' -> '54.37.212.106'
OK for 'ip4' -> '84.19.173.138'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → _spf.google.com) Invalid mechanisms in SPF-Record!
'include:_netblocks.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 44)!
'include:_netblocks2.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 45)!
'include:_netblocks3.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 46)!
OK for 'v' -> 'spf1'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de) Invalid mechanisms in SPF-Record!
'mx' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 34)!
'mx' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 34)!
'include:frgra07.bieber.com.de' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 35)!
'include:_spf.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 39)!
OK for 'v' -> 'spf1'
OK for 'mx'
OK for 'ip4' -> '144.76.86.250'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de) Invalid mechanisms in SPF-Record!
'mx' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 31)!
'mx' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 31)!
Endlosschleife bei 'include:deerf06.serverpool24.de':
Trace: natek.email-> include:mailgw.serverpool24.de-> include:deerf06.serverpool24.de-> include:deerf06.serverpool24.de
'include:defsn02.serverpool24.de' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 33)!
'include:_spf.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 43)!
OK for 'v' -> 'spf1'
OK for 'mx'
OK for 'ip4' -> '88.198.47.105'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de) Invalid mechanisms in SPF-Record!
'include:_spf.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 20)!
Endlosschleife bei 'include:deerf05.serverpool24.de':
Trace: natek.email-> include:mailgw.serverpool24.de-> include:deerf05.serverpool24.de-> include:deerf05.serverpool24.de
OK for 'v' -> 'spf1'
OK for 'mx'
OK for 'ip4' -> '88.198.47.105'
OK for 'include' -> 'defsn02.serverpool24.de'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de) Invalid mechanisms in SPF-Record!
'mx' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 11)!
'mx' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 11)!
'include:frgra07.bieber.com.de' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 12)!
'include:_spf.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 16)!
OK for 'v' -> 'spf1'
OK for 'mx'
OK for 'ip4' -> '144.76.86.250'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → frgra07.bieber.com.de) Invalid mechanisms in SPF-Record!
'a:spf1' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 13)!
'mx' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 14)!
Endlosschleife bei 'include:mailgw.serverpool24.de':
Trace: natek.email-> include:mailgw.serverpool24.de-> include:deerf05.serverpool24.de-> include:defsn02.serverpool24.de-> include:frgra07.bieber.com.de-> include:mailgw.serverpool24.de
'mx' cannot be resolved (IPv4)
OK for 'v' -> 'spf1'
OK for 'a'
OK for 'ip4' -> '94.23.164.183'
OK for 'ip4' -> '54.37.212.106'
OK for 'ip4' -> '84.19.173.138'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → _spf.google.com) Invalid mechanisms in SPF-Record!
'include:_netblocks.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 17)!
'include:_netblocks2.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 18)!
'include:_netblocks3.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 19)!
OK for 'v' -> 'spf1'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de) Invalid mechanisms in SPF-Record!
|
|
(natek.email → mailgw.serverpool24.de) Invalid mechanisms in SPF-Record!
'include:sys01.natek-server.de' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 24)!
Endlosschleife bei 'include:mailgw.serverpool24.de':
Trace: natek.email-> include:mailgw.serverpool24.de-> include:mailgw.serverpool24.de
'include:deerf06.serverpool24.de' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 30)!
'include:_spf.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 47)!
'mx' cannot be resolved (IPv4)
OK for 'v' -> 'spf1'
OK for 'ip4' -> '88.198.47.105'
OK for 'include' -> 'deerf05.serverpool24.de'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de → _spf.google.com) Invalid mechanisms in SPF-Record!
'include:_netblocks.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 26)!
'include:_netblocks2.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 27)!
'include:_netblocks3.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 28)!
OK for 'v' -> 'spf1'
OK for 'all' -> '~'
|
|
(natek.email → spf.nl2go.com) Invalid mechanisms in SPF-Record!
'include:spf1.nl2go.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 52)!
'include:spf2.nl2go.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 53)!
'include:spf3.nl2go.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 54)!
OK for 'v' -> 'spf1'
OK for 'ip4' -> '88.198.181.208/28'
OK for 'ip4' -> '88.198.96.0/27'
OK for 'ip4' -> '178.63.169.208/28'
OK for 'ip4' -> '88.198.249.64/28'
OK for 'ip4' -> '46.4.145.64/28'
OK for 'ip4' -> '178.63.165.160/28'
OK for 'all' -> '~'
|
|
(natek.email) Invalid mechanisms in SPF-Record!
'include:spf.nl2go.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 51)!
'a:mail4.epag.de' cannot be resolved (IPv6)
OK for 'v' -> 'spf1'
OK for 'a'
OK for 'mx'
OK for 'ip4' -> '84.19.173.138'
OK for 'ip4' -> '212.123.34.110'
OK for 'ip4' -> '212.123.36.25'
OK for 'ip4' -> '94.23.164.216'
OK for 'include' -> 'mailgw.serverpool24.de'
OK for 'all' -> '~'
|
|
(natek.email) Domains are resolved several times in the SPF Record!
The domain defsn02.serverpool24.de was 2 times resolved in the SPF record!
The domain frgra07.bieber.com.de was 2 times resolved in the SPF record!
The domain _spf.google.com was 6 times resolved in the SPF record!
The domain _netblocks.google.com was 6 times resolved in the SPF record!
The domain _netblocks2.google.com was 6 times resolved in the SPF record!
The domain _netblocks3.google.com was 6 times resolved in the SPF record!
|
|
(natek.email → mailgw.serverpool24.de → _spf.google.com) Invalid mechanisms in SPF-Record!
'include:_netblocks.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 48)!
'include:_netblocks2.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 49)!
'include:_netblocks3.google.com' exceeds the maximum DNS lookup limit of 10 (RFC7208)(Aktuell: 50)!
OK for 'v' -> 'spf1'
OK for 'all' -> '~'
|
|
(natek.email → spf.nl2go.com → spf1.nl2go.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '78.46.88.157'
OK for 'ip4' -> '62.138.82.64/26'
OK for 'ip4' -> '62.138.86.8/29'
OK for 'ip4' -> '62.138.91.0/29'
OK for 'ip4' -> '62.138.120.184/29'
OK for 'ip4' -> '62.138.121.0/26'
OK for 'ip4' -> '46.4.133.24'
OK for 'ip4' -> '176.9.2.230'
OK for 'all' -> '~'
|
|
(natek.email) The SPF consists of a permissible character set.
The SPF record of natek.email contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → _spf.google.com) The SPF consists of a permissible character set.
The SPF record of _spf.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → frgra07.bieber.com.de) The SPF consists of a permissible character set.
The SPF record of frgra07.bieber.com.de contains valid characters.
|
|
(natek.email → spf.nl2go.com) The SPF consists of a permissible character set.
The SPF record of spf.nl2go.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de) The SPF consists of a permissible character set.
The SPF record of defsn02.serverpool24.de contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de) The SPF consists of a permissible character set.
The SPF record of deerf06.serverpool24.de contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de → _spf.google.com → _netblocks.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '66.102.0.0/21'
OK for 'ip4' -> '66.249.80.0/20'
OK for 'ip4' -> '72.14.192.0/18'
OK for 'ip4' -> '74.125.0.0/16'
OK for 'ip4' -> '108.177.8.0/21'
OK for 'ip4' -> '173.194.0.0/16'
OK for 'ip4' -> '209.85.128.0/17'
OK for 'ip4' -> '216.58.192.0/19'
OK for 'ip4' -> '216.239.32.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de → _spf.google.com → _netblocks.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de → _spf.google.com → _netblocks2.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip6' -> '2001:4860:4000::/36'
OK for 'ip6' -> '2404:6800:4000::/36'
OK for 'ip6' -> '2607:f8b0:4000::/36'
OK for 'ip6' -> '2800:3f0:4000::/36'
OK for 'ip6' -> '2a00:1450:4000::/36'
OK for 'ip6' -> '2c0f:fb50:4000::/36'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de) The SPF consists of a permissible character set.
The SPF record of mailgw.serverpool24.de contains valid characters.
|
|
(natek.email → spf.nl2go.com → spf3.nl2go.com) The SPF consists of a permissible character set.
The SPF record of spf3.nl2go.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de → _spf.google.com → _netblocks2.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks2.google.com contains valid characters.
|
|
(natek.email → spf.nl2go.com → spf3.nl2go.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '185.182.80.48/29'
OK for 'ip4' -> '185.182.80.144/29'
OK for 'ip4' -> '185.182.80.248/29'
OK for 'ip4' -> '185.182.83.240/29'
OK for 'ip4' -> '78.47.39.96/28'
OK for 'ip4' -> '78.46.88.146'
OK for 'ip4' -> '78.46.88.156'
OK for 'ip4' -> '213.239.217.189'
OK for 'ip4' -> '78.46.114.185'
OK for 'ip4' -> '176.9.2.231'
OK for 'ip4' -> '46.4.133.23'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de → _spf.google.com → _netblocks3.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '172.217.0.0/19'
OK for 'ip4' -> '172.217.32.0/20'
OK for 'ip4' -> '172.217.128.0/19'
OK for 'ip4' -> '172.217.160.0/20'
OK for 'ip4' -> '172.217.192.0/19'
OK for 'ip4' -> '172.253.56.0/21'
OK for 'ip4' -> '172.253.112.0/20'
OK for 'ip4' -> '108.177.96.0/19'
OK for 'all' -> '~'
|
|
(natek.email → spf.nl2go.com → spf2.nl2go.com) The SPF consists of a permissible character set.
The SPF record of spf2.nl2go.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de → _spf.google.com → _netblocks3.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks3.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks3.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '172.217.0.0/19'
OK for 'ip4' -> '172.217.32.0/20'
OK for 'ip4' -> '172.217.128.0/19'
OK for 'ip4' -> '172.217.160.0/20'
OK for 'ip4' -> '172.217.192.0/19'
OK for 'ip4' -> '172.253.56.0/21'
OK for 'ip4' -> '172.253.112.0/20'
OK for 'ip4' -> '108.177.96.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de → _spf.google.com) The SPF consists of a permissible character set.
The SPF record of _spf.google.com contains valid characters.
|
|
(natek.email → spf.nl2go.com → spf2.nl2go.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '46.4.133.19'
OK for 'ip4' -> '62.138.90.192/26'
OK for 'ip4' -> '91.228.144.0/24'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → sys01.natek-server.de) The SPF consists of a permissible character set.
The SPF record of sys01.natek-server.de contains valid characters.
|
|
(natek.email → spf.nl2go.com → spf1.nl2go.com) The SPF consists of a permissible character set.
The SPF record of spf1.nl2go.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks3.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks3.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → _spf.google.com → _netblocks.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '66.102.0.0/21'
OK for 'ip4' -> '66.249.80.0/20'
OK for 'ip4' -> '72.14.192.0/18'
OK for 'ip4' -> '74.125.0.0/16'
OK for 'ip4' -> '108.177.8.0/21'
OK for 'ip4' -> '173.194.0.0/16'
OK for 'ip4' -> '209.85.128.0/17'
OK for 'ip4' -> '216.58.192.0/19'
OK for 'ip4' -> '216.239.32.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks2.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks2.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks2.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip6' -> '2001:4860:4000::/36'
OK for 'ip6' -> '2404:6800:4000::/36'
OK for 'ip6' -> '2607:f8b0:4000::/36'
OK for 'ip6' -> '2800:3f0:4000::/36'
OK for 'ip6' -> '2a00:1450:4000::/36'
OK for 'ip6' -> '2c0f:fb50:4000::/36'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → _spf.google.com → _netblocks2.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip6' -> '2001:4860:4000::/36'
OK for 'ip6' -> '2404:6800:4000::/36'
OK for 'ip6' -> '2607:f8b0:4000::/36'
OK for 'ip6' -> '2800:3f0:4000::/36'
OK for 'ip6' -> '2a00:1450:4000::/36'
OK for 'ip6' -> '2c0f:fb50:4000::/36'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → _spf.google.com → _netblocks2.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks2.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → _spf.google.com → _netblocks3.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '172.217.0.0/19'
OK for 'ip4' -> '172.217.32.0/20'
OK for 'ip4' -> '172.217.128.0/19'
OK for 'ip4' -> '172.217.160.0/20'
OK for 'ip4' -> '172.217.192.0/19'
OK for 'ip4' -> '172.253.56.0/21'
OK for 'ip4' -> '172.253.112.0/20'
OK for 'ip4' -> '108.177.96.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → _spf.google.com → _netblocks3.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks3.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → _spf.google.com) The SPF consists of a permissible character set.
The SPF record of _spf.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → _spf.google.com → _netblocks.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '66.102.0.0/21'
OK for 'ip4' -> '66.249.80.0/20'
OK for 'ip4' -> '72.14.192.0/18'
OK for 'ip4' -> '74.125.0.0/16'
OK for 'ip4' -> '108.177.8.0/21'
OK for 'ip4' -> '173.194.0.0/16'
OK for 'ip4' -> '209.85.128.0/17'
OK for 'ip4' -> '216.58.192.0/19'
OK for 'ip4' -> '216.239.32.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → _spf.google.com → _netblocks.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → _spf.google.com → _netblocks2.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip6' -> '2001:4860:4000::/36'
OK for 'ip6' -> '2404:6800:4000::/36'
OK for 'ip6' -> '2607:f8b0:4000::/36'
OK for 'ip6' -> '2800:3f0:4000::/36'
OK for 'ip6' -> '2a00:1450:4000::/36'
OK for 'ip6' -> '2c0f:fb50:4000::/36'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → _spf.google.com → _netblocks2.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks2.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → _spf.google.com → _netblocks3.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '172.217.0.0/19'
OK for 'ip4' -> '172.217.32.0/20'
OK for 'ip4' -> '172.217.128.0/19'
OK for 'ip4' -> '172.217.160.0/20'
OK for 'ip4' -> '172.217.192.0/19'
OK for 'ip4' -> '172.253.56.0/21'
OK for 'ip4' -> '172.253.112.0/20'
OK for 'ip4' -> '108.177.96.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → _spf.google.com → _netblocks3.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks3.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → _spf.google.com) The SPF consists of a permissible character set.
The SPF record of _spf.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '66.102.0.0/21'
OK for 'ip4' -> '66.249.80.0/20'
OK for 'ip4' -> '72.14.192.0/18'
OK for 'ip4' -> '74.125.0.0/16'
OK for 'ip4' -> '108.177.8.0/21'
OK for 'ip4' -> '173.194.0.0/16'
OK for 'ip4' -> '209.85.128.0/17'
OK for 'ip4' -> '216.58.192.0/19'
OK for 'ip4' -> '216.239.32.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks2.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks2.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks2.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip6' -> '2001:4860:4000::/36'
OK for 'ip6' -> '2404:6800:4000::/36'
OK for 'ip6' -> '2607:f8b0:4000::/36'
OK for 'ip6' -> '2800:3f0:4000::/36'
OK for 'ip6' -> '2a00:1450:4000::/36'
OK for 'ip6' -> '2c0f:fb50:4000::/36'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → _spf.google.com → _netblocks2.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip6' -> '2001:4860:4000::/36'
OK for 'ip6' -> '2404:6800:4000::/36'
OK for 'ip6' -> '2607:f8b0:4000::/36'
OK for 'ip6' -> '2800:3f0:4000::/36'
OK for 'ip6' -> '2a00:1450:4000::/36'
OK for 'ip6' -> '2c0f:fb50:4000::/36'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → _spf.google.com → _netblocks.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → _spf.google.com) The SPF consists of a permissible character set.
The SPF record of _spf.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → _spf.google.com → _netblocks3.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks3.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → _spf.google.com → _netblocks3.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '172.217.0.0/19'
OK for 'ip4' -> '172.217.32.0/20'
OK for 'ip4' -> '172.217.128.0/19'
OK for 'ip4' -> '172.217.160.0/20'
OK for 'ip4' -> '172.217.192.0/19'
OK for 'ip4' -> '172.253.56.0/21'
OK for 'ip4' -> '172.253.112.0/20'
OK for 'ip4' -> '108.177.96.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → _spf.google.com → _netblocks2.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks2.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → _spf.google.com → _netblocks.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks3.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '172.217.0.0/19'
OK for 'ip4' -> '172.217.32.0/20'
OK for 'ip4' -> '172.217.128.0/19'
OK for 'ip4' -> '172.217.160.0/20'
OK for 'ip4' -> '172.217.192.0/19'
OK for 'ip4' -> '172.253.56.0/21'
OK for 'ip4' -> '172.253.112.0/20'
OK for 'ip4' -> '108.177.96.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → _spf.google.com → _netblocks.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '66.102.0.0/21'
OK for 'ip4' -> '66.249.80.0/20'
OK for 'ip4' -> '72.14.192.0/18'
OK for 'ip4' -> '74.125.0.0/16'
OK for 'ip4' -> '108.177.8.0/21'
OK for 'ip4' -> '173.194.0.0/16'
OK for 'ip4' -> '209.85.128.0/17'
OK for 'ip4' -> '216.58.192.0/19'
OK for 'ip4' -> '216.239.32.0/19'
OK for 'all' -> '~'
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de) The SPF consists of a permissible character set.
The SPF record of deerf05.serverpool24.de contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de) The SPF consists of a permissible character set.
The SPF record of defsn02.serverpool24.de contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → frgra07.bieber.com.de) The SPF consists of a permissible character set.
The SPF record of frgra07.bieber.com.de contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → _spf.google.com) The SPF consists of a permissible character set.
The SPF record of _spf.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf05.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks3.google.com) The SPF consists of a permissible character set.
The SPF record of _netblocks3.google.com contains valid characters.
|
|
(natek.email → mailgw.serverpool24.de → deerf06.serverpool24.de → defsn02.serverpool24.de → _spf.google.com → _netblocks.google.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '66.102.0.0/21'
OK for 'ip4' -> '66.249.80.0/20'
OK for 'ip4' -> '72.14.192.0/18'
OK for 'ip4' -> '74.125.0.0/16'
OK for 'ip4' -> '108.177.8.0/21'
OK for 'ip4' -> '173.194.0.0/16'
OK for 'ip4' -> '209.85.128.0/17'
OK for 'ip4' -> '216.58.192.0/19'
OK for 'ip4' -> '216.239.32.0/19'
OK for 'all' -> '~'
|
SPF record available?
We found an SPF record for the domain.
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
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
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
Additionally authorized IPv4 addresses
Explicit IPv4 addresses in the SPF record have been authorized to send
Additional external SPF records
We could find other records authorized in the SPF record
E-Mail handling
How should the checkHost() function of the e-mail server handle the e-mail? (syntax )
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 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
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:
frgra07.bieber.com.de
Get a first impression of the risk potential in your company
