6 / 10
Lookups
1
Issue
4
IPv4 addresses
0
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 mx ip4:46.46.137.27 ip4:46.46.137.28 ptr:mail.ru ptr:google.com ptr:retn.net ptr:retn.ru ptr:retnnet.ru ~all
Copied
Terms
mx
pass
if the sender's IP address is in the A or AAAA record of this domain.
2 IPv4 addresses
or else
ip4:
46.46.137.27 / 32
pass
if the sender's IP is between
46.46.137.27 and 46.46.137.27 (inclusive).
46.46.137.27 and 46.46.137.27 (inclusive).
JSC RetnNet
AS29470
or else
ip4:
46.46.137.28 / 32
pass
if the sender's IP is between
46.46.137.28 and 46.46.137.28 (inclusive).
46.46.137.28 and 46.46.137.28 (inclusive).
JSC "RetnNet"
AS29470
or else
ptr:
mail.ru
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ptr:
google.com
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ptr:
retn.net
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ptr:
retn.ru
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ptr:
retnnet.ru
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
~all
soft fail
the email's SPF check.
Included records
v=spf1 mx ip4:46.46.137.27 ip4:46.46.137.28 ptr:mail.ru ptr:google.com ptr:retn.net ptr:retn.ru ptr:retnnet.ru ~all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable