2 / 10
Lookups
1
Issue
8
IPv4 addresses
0
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 ptr ip4:178.32.91.83 ip4:178.32.91.87 include:spfsaas.cloud2be.net -all
Copied
Terms
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ip4:
178.32.91.83 / 32
pass
if the sender's IP is between
178.32.91.83 and 178.32.91.83 (inclusive).
178.32.91.83 and 178.32.91.83 (inclusive).
OVH
AS16276
or else
ip4:
178.32.91.87 / 32
pass
if the sender's IP is between
178.32.91.87 and 178.32.91.87 (inclusive).
178.32.91.87 and 178.32.91.87 (inclusive).
OVH
AS16276
or else
include:
spfsaas.cloud2be.net
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 ptr ip4:178.32.91.83 ip4:178.32.91.87 include:spfsaas.cloud2be.net -all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
6 x ip4 -all