9 / 10
Lookups
2
Issues
458,763
IPv4 addresses
2.19 ⋅ 10
24
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 ptr a include:clearcable.ca a:mail.clearcable.net -all
Copied
Terms
mx
pass
if the sender's IP address is in the A or AAAA record of this domain.
4 IPv4 addresses
4 IPv6 addresses
or else
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
a
pass
if the sender's IP address is in the A or AAAA record of this domain.
1 IPv4 address
1 IPv6 address
or else
include:
clearcable.ca
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
pass
if the sender's IP address is in the A or AAAA record of this domain.
1 IPv4 address
1 IPv6 address
or else
-all
fail
the email's SPF check.
Included records
v=spf1 mx ptr a include:clearcable.ca a:mail.clearcable.net -all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
mx include:spf.protection.outlook.com a:mail.clearcable.ca ptr -all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
6 x ip4 5 x ip6 -all
IP ranges
2a01:111:f403:8000::
/ 51
Microsoft
AS8075
2a01:111:f403:8000::
2a01:111:f403:9fff:ffff:ffff:ffff:ffff
2a01:111:f403:c000::
/ 51
Microsoft
AS8075
2a01:111:f403:c000::
2a01:111:f403:dfff:ffff:ffff:ffff:ffff
2a01:111:f403:f000::
/ 52
Microsoft
AS8075
2a01:111:f403:f000::
2a01:111:f403:ffff:ffff:ffff:ffff:ffff