10 / 10
Lookups
1
Issue
203,124
IPv4 addresses
5.94 ⋅ 10
28
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 a:smtp-gw1.silae.fr ptr:out1.raccourci.fr ip4:178.33.169.0/24 ip4:5.226.2.176/28 include:spf.raccourci.fr include:calendar-server.bounces.google.com include:_spf.google.com -all
Copied
Terms
or else
ptr:
out1.raccourci.fr
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ip4:
178.33.169.0 / 24
pass
if the sender's IP is between
178.33.169.0 and 178.33.169.255 (inclusive).
178.33.169.0 and 178.33.169.255 (inclusive).
OVH
AS16276
or else
ip4:
5.226.2.176 / 28
pass
if the sender's IP is between
5.226.2.176 and 5.226.2.191 (inclusive).
5.226.2.176 and 5.226.2.191 (inclusive).
Free Pro
AS30781
or else
include:
spf.raccourci.fr
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
include:
calendar-server.bounces.google.com
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
include:
_spf.google.com
Evaluate this SPF record and
pass
if it
passes.
This include does nothing if the included record returns fail, soft fail, or neutral.
Gmail
Inbox software
or else
-all
fail
the email's SPF check.
Included records
v=spf1 a:smtp-gw1.silae.fr ptr:out1.raccourci.fr ip4:178.33.169.0/24 ip4:5.226.2.176/28 include:spf.raccourci.fr include:calendar-server.bounces.google.com include:_spf.google.com -all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
a:out1.raccourci.fr a:out1.graffeuille.com.raccourci.fr a:out1.mairie-aigrefeuille.fr.raccourci.fr 3 x ip4 include:spf.mailjet.com -all
5 x ip4 ~all
2 x ip4 6 x ip6 ~all