1 / 10
Lookups
1
Issue
4
IPv4 addresses
0
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 ip4:188.165.33.73 ip4:91.121.37.151 ip4:92.222.155.67 ip4:51.91.176.140 ptr:daghebergement.fr ?all
Copied
Terms
ip4:
188.165.33.73 / 32
pass
if the sender's IP is between
188.165.33.73 and 188.165.33.73 (inclusive).
188.165.33.73 and 188.165.33.73 (inclusive).
OVH
AS16276
or else
ip4:
91.121.37.151 / 32
pass
if the sender's IP is between
91.121.37.151 and 91.121.37.151 (inclusive).
91.121.37.151 and 91.121.37.151 (inclusive).
OVH
AS16276
or else
ip4:
92.222.155.67 / 32
pass
if the sender's IP is between
92.222.155.67 and 92.222.155.67 (inclusive).
92.222.155.67 and 92.222.155.67 (inclusive).
OVH
AS16276
or else
ip4:
51.91.176.140 / 32
pass
if the sender's IP is between
51.91.176.140 and 51.91.176.140 (inclusive).
51.91.176.140 and 51.91.176.140 (inclusive).
OVH
AS16276
or else
ptr:
daghebergement.fr
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
?all
Don't state if this IP is allowed to send this email.
Included records
v=spf1 ip4:188.165.33.73 ip4:91.121.37.151 ip4:92.222.155.67 ip4:51.91.176.140 ptr:daghebergement.fr ?all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable