6 / 10
Lookups
1
Issue
92,173
IPv4 addresses
0
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 a mx ptr a:smtp.stella-telecom.fr a:smtp.celeste.fr ip4:62.193.36.196 ip4:62.193.36.198 include:amazonses.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.
2 IPv4 addresses
or else
ptr:
.
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
pass
if the sender's IP address is in the A or AAAA record of this domain.
7 IPv4 addresses
or else
pass
if the sender's IP address is in the A or AAAA record of this domain.
1 IPv4 address
or else
ip4:
62.193.36.196 / 32
pass
if the sender's IP is between
62.193.36.196 and 62.193.36.196 (inclusive).
62.193.36.196 and 62.193.36.196 (inclusive).
Celeste
AS34177
or else
ip4:
62.193.36.198 / 32
pass
if the sender's IP is between
62.193.36.198 and 62.193.36.198 (inclusive).
62.193.36.198 and 62.193.36.198 (inclusive).
Celeste
AS34177
or else
include:
amazonses.com
Evaluate this SPF record and
pass
if it
passes.
This include does nothing if the included record returns fail, soft fail, or neutral.
Amazon SES
Email automation
or else
~all
soft fail
the email's SPF check.
Included records
v=spf1 a mx ptr a:smtp.stella-telecom.fr a:smtp.celeste.fr ip4:62.193.36.196 ip4:62.193.36.198 include:amazonses.com ~all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
12 x ip4 -all
