6 / 10
Lookups
2
Issues
98,308
IPv4 addresses
4.95 ⋅ 10
27
IPv6 addresses
There are 2 issues with this SPF record
- 'all' should be the last mechanism (any other mechanism will be ignored).
- The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 include:_spf.google.com ~all a mx ptr mx:18d05.mspz3.gob.ec ip4:186.42.97.130 ptr:18d05.mspz3.gob.ec ~all
Copied
Terms
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
soft fail
the email's SPF check.
or else
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.
1 IPv4 address
or else
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.
1 IPv4 address
or else
ip4:
186.42.97.130 / 32
pass
if the sender's IP is between
186.42.97.130 and 186.42.97.130 (inclusive).
186.42.97.130 and 186.42.97.130 (inclusive).
CORPORACION NACIONAL DE TELECOMUNICACIONES - CNT EP
AS28006
or else
ptr:
18d05.mspz3.gob.ec
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
~all
soft fail
the email's SPF check.
Included records
v=spf1 include:_spf.google.com ~all a mx ptr mx:18d05.mspz3.gob.ec ip4:186.42.97.130 ptr:18d05.mspz3.gob.ec ~all
'all' should be the last mechanism (any other mechanism will be ignored)
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable
2 x ip4 6 x ip6 ~all