8 / 10
Lookups
3
Issues
5
IPv4 addresses
0
IPv6 addresses
There are 3 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.
- The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 ptr:ovh.net ip4:194.149.88.225 include:mx.ovh.com include:ovh.net ~all
Copied
Terms
ptr:
ovh.net
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ip4:
194.149.88.225 / 32
pass
if the sender's IP is between
194.149.88.225 and 194.149.88.225 (inclusive).
194.149.88.225 and 194.149.88.225 (inclusive).
IZACOM Sp. z o.o.
AS42986
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
include:
ovh.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
soft fail
the email's SPF check.
Included records
v=spf1 ptr:ovh.net ip4:194.149.88.225 include:mx.ovh.com include:ovh.net ~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
include:mx.ovh.com ?all
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