5 / 10
Lookups
1
Issue
46
IPv4 addresses
1.84 ⋅ 10
19
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:85.10.133.127 ip6:2a01:7c8:d006:325:5054:ff:fe57:9bb1 include:_spf.transip.email ~all
Copied
Terms
a
pass
if the sender's IP address is in the A or AAAA record of this domain.
1 IPv4 address
1 IPv6 address
or else
mx
pass
if the sender's IP address is in the A or AAAA record of this domain.
or else
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ip4:
85.10.133.127 / 32
pass
if the sender's IP is between
85.10.133.127 and 85.10.133.127 (inclusive).
85.10.133.127 and 85.10.133.127 (inclusive).
Signet
AS20857
or else
ip6:
2a01:7c8:d006:325:5054:ff:fe57:9bb1 / 128
pass
if the sender's IP is between
2a01:7c8:d006:325:5054:ff:fe57:9bb1 and 2a01:7c8:d006:325:5054:ff:fe57:9bb1 (inclusive).
2a01:7c8:d006:325:5054:ff:fe57:9bb1 and 2a01:7c8:d006:325:5054:ff:fe57:9bb1 (inclusive).
Signet
AS20857
or else
include:
_spf.transip.email
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
soft fail
the email's SPF check.
Included records
v=spf1 a mx ptr ip4:85.10.133.127 ip6:2a01:7c8:d006:325:5054:ff:fe57:9bb1 include:_spf.transip.email ~all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
include:_mailcluster.transip.email 1 x ip4 ~all
12 x ip4 4 x ip6 ~all