4 / 10
Lookups
1
Issue
98,310
IPv4 addresses
2.97 ⋅ 10
28
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:176.107.219.19 ip4:176.107.219.26 ip4:176.107.219.14 include:_spf.google.com ~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
ip4:
176.107.219.19 / 32
pass
if the sender's IP is between
176.107.219.19 and 176.107.219.19 (inclusive).
176.107.219.19 and 176.107.219.19 (inclusive).
LLC Yarteleservice
AS57781
or else
ip4:
176.107.219.26 / 32
pass
if the sender's IP is between
176.107.219.26 and 176.107.219.26 (inclusive).
176.107.219.26 and 176.107.219.26 (inclusive).
LLC Yarteleservice
AS57781
or else
ip4:
176.107.219.14 / 32
pass
if the sender's IP is between
176.107.219.14 and 176.107.219.14 (inclusive).
176.107.219.14 and 176.107.219.14 (inclusive).
LLC Yarteleservice
AS57781
or else
include:
_spf.google.com
Evaluate this SPF record and
pass
if it
passes.
This include does nothing if the included record returns fail, soft fail, or neutral.
Gmail
Inbox software
or else
~all
soft fail
the email's SPF check.
Included records
v=spf1 a mx ptr ip4:176.107.219.19 ip4:176.107.219.26 ip4:176.107.219.14 include:_spf.google.com ~all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
2 x ip4 6 x ip6 ~all