3 / 10
Lookups
1
Issue
2
IPv4 addresses
0
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 ip4:46.160.151.18 ip4:89.251.66.33 ptr:ksu1.ugmk-telecom.ru a mx -all
Copied
Terms
ip4:
46.160.151.18 / 32
pass
if the sender's IP is between
46.160.151.18 and 46.160.151.18 (inclusive).
46.160.151.18 and 46.160.151.18 (inclusive).
UGMK-Telecom
AS41560
or else
ip4:
89.251.66.33 / 32
pass
if the sender's IP is between
89.251.66.33 and 89.251.66.33 (inclusive).
89.251.66.33 and 89.251.66.33 (inclusive).
UGMK-Telecom
AS41560
or else
ptr:
ksu1.ugmk-telecom.ru
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
a
pass
if the sender's IP address is in the A or AAAA record of this domain.
or else
mx
pass
if the sender's IP address is in the A or AAAA record of this domain.
or else
-all
fail
the email's SPF check.
Included records
v=spf1 ip4:46.160.151.18 ip4:89.251.66.33 ptr:ksu1.ugmk-telecom.ru a mx -all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable