5 / 10
Lookups
1
Issue
98,307
IPv4 addresses
2.83 ⋅ 10
22
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 a mx ptr ip6:2a01:4f9:3a:2d4c::3 ip4:135.181.215.99 include:aspmx.googlemail.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.
1 IPv4 address
or else
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ip6:
2a01:4f9:3a:2d4c::3 / 128
pass
if the sender's IP is between
2a01:4f9:3a:2d4c::3 and 2a01:4f9:3a:2d4c::3 (inclusive).
2a01:4f9:3a:2d4c::3 and 2a01:4f9:3a:2d4c::3 (inclusive).
Hetzner Online
AS24940
or else
ip4:
135.181.215.99 / 32
pass
if the sender's IP is between
135.181.215.99 and 135.181.215.99 (inclusive).
135.181.215.99 and 135.181.215.99 (inclusive).
Hetzner Online
AS24940
or else
include:
aspmx.googlemail.com
Evaluate this SPF record and
pass
if it
passes.
This include does nothing if the included record returns fail, soft fail, or neutral.
or else
-all
fail
the email's SPF check.
Included records
v=spf1 a mx ptr ip6:2a01:4f9:3a:2d4c::3 ip4:135.181.215.99 include:aspmx.googlemail.com -all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable