6 / 10
Lookups
2
Issues
18,436
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 mx a ptr ip4:82.97.0.0/18 ip4:185.52.32.0/22 ip4:193.41.72.0/22 include:atsat.com ?all
Copied
Terms
mx
pass
if the sender's IP address is in the A or AAAA record of this domain.
2 IPv4 addresses
or else
a
pass
if the sender's IP address is in the A or AAAA record of this domain.
or else
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ip4:
82.97.0.0 / 18
pass
if the sender's IP is between
82.97.0.0 and 82.97.63.255 (inclusive).
82.97.0.0 and 82.97.63.255 (inclusive).
ATSAT Autonomous System
AS8554
or else
ip4:
185.52.32.0 / 22
pass
if the sender's IP is between
185.52.32.0 and 185.52.35.255 (inclusive).
185.52.32.0 and 185.52.35.255 (inclusive).
ATSAT Autonomous System
AS8554
or else
ip4:
193.41.72.0 / 22
pass
if the sender's IP is between
193.41.72.0 and 193.41.75.255 (inclusive).
193.41.72.0 and 193.41.75.255 (inclusive).
ATSAT Autonomous System
AS8554
or else
include:
atsat.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
?all
Don't state if this IP is allowed to send this email.
Included records
v=spf1 mx a ptr ip4:82.97.0.0/18 ip4:185.52.32.0/22 ip4:193.41.72.0/22 include:atsat.com ?all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
mx ptr ?all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable