5 / 10
Lookups
3
Issues
771
IPv4 addresses
0
IPv6 addresses
There are 3 issues with this SPF record
- The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
- DNS returned SERVFAIL while resolving A/AAAA records for www, so this SPF term could not be expanded into IP addresses.
- DNS returned SERVFAIL while resolving A/AAAA records for mail, so this SPF term could not be expanded into IP addresses.
v=spf1 a mx ptr a:www a:mail ip4:64.192.56.0/24 ip4:209.221.63.0/24 ip4:68.208.146.0/24 -all
Copied
Terms
a
pass
if the sender's IP address is in the A or AAAA record of this domain.
1 IPv4 address
or else
mx
pass
if the sender's IP address is in the A or AAAA record of this domain.
2 IPv4 addresses
or else
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
or else
or else
ip4:
64.192.56.0 / 24
pass
if the sender's IP is between
64.192.56.0 and 64.192.56.255 (inclusive).
64.192.56.0 and 64.192.56.255 (inclusive).
Epproach Communications
AS7856
or else
ip4:
209.221.63.0 / 24
pass
if the sender's IP is between
209.221.63.0 and 209.221.63.255 (inclusive).
209.221.63.0 and 209.221.63.255 (inclusive).
The Seimitsu
AS62844
or else
ip4:
68.208.146.0 / 24
pass
if the sender's IP is between
68.208.146.0 and 68.208.146.255 (inclusive).
68.208.146.0 and 68.208.146.255 (inclusive).
AT&T Enterprises
AS6389
or else
-all
fail
the email's SPF check.
Included records
v=spf1 a mx ptr a:www a:mail ip4:64.192.56.0/24 ip4:209.221.63.0/24 ip4:68.208.146.0/24 -all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable