3 / 10
Lookups
1
Issue
1,027
IPv4 addresses
0
IPv6 addresses
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable.
v=spf1 mx a ptr ip4:95.175.122.0/24 ip4:62.106.45.0/24 ip4:62.106.3.0/24 ip4:62.106.47.0/24 ?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.
1 IPv4 address
or else
PTR checks should no longer be used. See
RFC 7208, section 5.5
.
or else
ip4:
95.175.122.0 / 24
pass
if the sender's IP is between
95.175.122.0 and 95.175.122.255 (inclusive).
95.175.122.0 and 95.175.122.255 (inclusive).
Verne Vantaa Oy
AS49282
or else
ip4:
62.106.45.0 / 24
pass
if the sender's IP is between
62.106.45.0 and 62.106.45.255 (inclusive).
62.106.45.0 and 62.106.45.255 (inclusive).
ElmoNet Oy
AS8829
or else
ip4:
62.106.3.0 / 24
pass
if the sender's IP is between
62.106.3.0 and 62.106.3.255 (inclusive).
62.106.3.0 and 62.106.3.255 (inclusive).
ElmoNet Oy
AS8829
or else
ip4:
62.106.47.0 / 24
pass
if the sender's IP is between
62.106.47.0 and 62.106.47.255 (inclusive).
62.106.47.0 and 62.106.47.255 (inclusive).
ElmoNet Oy
AS8829
or else
?all
Don't state if this IP is allowed to send this email.
Included records
v=spf1 mx a ptr ip4:95.175.122.0/24 ip4:62.106.45.0/24 ip4:62.106.3.0/24 ip4:62.106.47.0/24 ?all
The 'ptr' mechanism shouldn't be used because it's slow, resource intensive, and not very reliable