6 / 10
Lookups
2
Issues
9
IPv4 addresses
0
IPv6 addresses
There are 2 issues with this SPF record
- The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
- The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 a mx ptr ip4:51.38.35.1/32 ip4:13.37.201.222/32 ip4:35.181.25.130/32 include:mx.ovh.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.
3 IPv4 addresses
or else
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ip4:
51.38.35.1 / 32
pass
if the sender's IP is between
51.38.35.1 and 51.38.35.1 (inclusive).
51.38.35.1 and 51.38.35.1 (inclusive).
OVH
AS16276
or else
ip4:
13.37.201.222 / 32
pass
if the sender's IP is between
13.37.201.222 and 13.37.201.222 (inclusive).
13.37.201.222 and 13.37.201.222 (inclusive).
Amazon.com
AS16509
or else
ip4:
35.181.25.130 / 32
pass
if the sender's IP is between
35.181.25.130 and 35.181.25.130 (inclusive).
35.181.25.130 and 35.181.25.130 (inclusive).
Amazon.com
AS16509
or else
include:
mx.ovh.com
Evaluate this SPF record and
pass
if it
passes.
This include does nothing if the included record returns fail, soft fail, or neutral.
OVHcloud
Inbox software
or else
-all
fail
the email's SPF check.
Included records
v=spf1 a mx ptr ip4:51.38.35.1 ip4:13.37.201.222 ip4:35.181.25.130 include:mx.ovh.com -all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
ptr:mail-out.ovh.net ptr:mail.ovh.net 2 x ip4 ?all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable