3 / 10
Lookups
1
Issue
1,026
IPv4 addresses
0
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 a mx ptr ip4:64.192.56.0/24 ip4:64.192.54.0/24 ip4:209.221.62.0/24 ip4:209.221.63.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.
1 IPv4 address
or else
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
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:
64.192.54.0 / 24
pass
if the sender's IP is between
64.192.54.0 and 64.192.54.255 (inclusive).
64.192.54.0 and 64.192.54.255 (inclusive).
The Seimitsu
AS62844
or else
ip4:
209.221.62.0 / 24
pass
if the sender's IP is between
209.221.62.0 and 209.221.62.255 (inclusive).
209.221.62.0 and 209.221.62.255 (inclusive).
The Seimitsu
AS62844
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
~all
soft fail
the email's SPF check.
Included records
v=spf1 a mx ptr ip4:64.192.56.0/24 ip4:64.192.54.0/24 ip4:209.221.62.0/24 ip4:209.221.63.0/24 ~all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable