Solve your problems in no time
Guaranteed measurable improvement for email deliverability and domain security
Solve your problems in no time
With the SPF lookup you analyze the SPF record of a domain for errors, security risks and authorized IP addresses. Optionally, you can specify an IP address to check if it is authorized to send e-mail on behalf of the domain. The SPF lookup analyzes registered TXT records in real time. If you want to specify an SPF record manually, use the SPF Analyzer.
Does a valid SPF record exist?
An SPF record was found for the domain purple.telstra.com.
The SPF record for purple.telstra.com is valid.
The syntax check of the SPF record shows no obvious errors.
Which IP-s are legitimate to send emails?
The SPF record contains a reference to external rules, which means that the validity of the SPF record depends on at least one other domain. A detailed list of the rules used externally can be found in the analysis result.
In total, 77 IP address(es) were authorized by the SPF record to send emails.
The SPF record analysis was performed on 18.11.2024 at 09:51:48 clock.
|
(purple.telstra.com → mail.zendesk.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '103.151.192.0/23'
OK for 'ip4' -> '185.12.80.0/22'
OK for 'ip4' -> '188.172.128.0/20'
OK for 'ip4' -> '192.161.144.0/20'
OK for 'ip4' -> '216.198.0.0/18'
OK for 'all' -> '~'
|
|
(purple.telstra.com → spf.myconnectwise.net → spf.smtp2go.com) The SPF consists of a permissible character set.
The SPF record of spf.smtp2go.com contains valid characters.
|
|
(purple.telstra.com) The DNS lookup limit was not exceeded.
The limit was not exceeded:
1: purple.telstra.com include:spf.protection.outlook.com 2: purple.telstra.com include:mail.zendesk.com 3: purple.telstra.com include:sent-via.netsuite.com 4: purple.telstra.com include:sent-via.netsuite.com include:sp1.mailsenders.netsuite.com 5: purple.telstra.com include:sent-via.netsuite.com include:sp2.mailsenders.netsuite.com 6: purple.telstra.com include:spf.myconnectwise.net 7: purple.telstra.com include:spf.myconnectwise.net include:spf.smtp2go.com |
|
(purple.telstra.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '203.35.135.0/24'
OK for 'ip4' -> '203.35.82.0/24'
OK for 'include' -> 'spf.protection.outlook.com'
OK for 'ip4' -> '203.35.185.240/28'
OK for 'ip4' -> '203.41.142.240/28'
OK for 'include' -> 'mail.zendesk.com'
Correct syntax for 'exists' -> '%{i}._spf.mta.salesforce.com'.
OK for 'ip4' -> '147.253.214.108'
Correct syntax for 'exists' -> '%{i}._spf.sparkpostmail.com'.
OK for 'ip4' -> '205.201.128.0/20'
OK for 'ip4' -> '198.2.128.0/18'
OK for 'ip4' -> '148.105.8.0/21'
OK for 'include' -> 'sent-via.netsuite.com'
OK for 'include' -> 'spf.myconnectwise.net'
OK for 'all' -> '~'
|
|
(purple.telstra.com → spf.protection.outlook.com) The SPF consists of a permissible character set.
The SPF record of spf.protection.outlook.com contains valid characters.
|
|
(purple.telstra.com → spf.protection.outlook.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '40.92.0.0/15'
OK for 'ip4' -> '40.107.0.0/16'
OK for 'ip4' -> '52.100.0.0/15'
OK for 'ip4' -> '52.102.0.0/16'
OK for 'ip4' -> '52.103.0.0/17'
OK for 'ip4' -> '104.47.0.0/17'
OK for 'ip6' -> '2a01:111:f400::/48'
OK for 'ip6' -> '2a01:111:f403::/49'
OK for 'ip6' -> '2a01:111:f403:8000::/51'
OK for 'ip6' -> '2a01:111:f403:c000::/51'
OK for 'ip6' -> '2a01:111:f403:f000::/52'
OK for 'all' -> '-'
|
|
(purple.telstra.com → spf.myconnectwise.net) The SPF consists of a permissible character set.
The SPF record of spf.myconnectwise.net contains valid characters.
|
|
(purple.telstra.com → spf.myconnectwise.net) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '54.175.226.230/32'
OK for 'ip4' -> '54.175.120.115/32'
OK for 'ip4' -> '54.84.157.192/32'
OK for 'ip4' -> '54.173.41.109/32'
OK for 'ip4' -> '54.86.73.129/32'
OK for 'ip4' -> '63.150.4.232/31'
OK for 'ip4' -> '100.42.120.128/27'
OK for 'ip4' -> '100.42.115.0/27'
OK for 'ip4' -> '69.84.129.224/27'
OK for 'ip4' -> '54.66.220.193/32'
OK for 'ip4' -> '54.66.200.109/32'
OK for 'ip4' -> '54.77.78.8/32'
OK for 'ip4' -> '54.77.200.220/32'
OK for 'include' -> 'spf.smtp2go.com'
OK for 'all' -> '~'
|
|
(purple.telstra.com → spf.myconnectwise.net → spf.smtp2go.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '207.58.147.64/28'
OK for 'ip4' -> '216.22.15.224/27'
OK for 'ip4' -> '43.228.184.0/22'
OK for 'ip4' -> '103.47.204.0/22'
OK for 'ip4' -> '103.2.140.0/22'
OK for 'ip4' -> '203.31.36.0/22'
OK for 'ip4' -> '170.10.68.0/22'
OK for 'ip4' -> '158.120.80.0/21'
OK for 'all' -> '~'
|
|
(purple.telstra.com → mail.zendesk.com) The SPF consists of a permissible character set.
The SPF record of mail.zendesk.com contains valid characters.
|
|
(purple.telstra.com → sent-via.netsuite.com) The SPF consists of a permissible character set.
The SPF record of sent-via.netsuite.com contains valid characters.
|
|
(purple.telstra.com → sent-via.netsuite.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '192.29.200.0/25'
OK for 'ip4' -> '129.148.164.0/25'
OK for 'ip4' -> '192.29.103.128/25'
OK for 'ip4' -> '147.154.32.0/25'
OK for 'ip4' -> '130.35.116.0/25'
OK for 'ip4' -> '129.149.22.0/25'
OK for 'ip4' -> '138.1.108.0/25'
OK for 'ip4' -> '192.29.72.0/25'
OK for 'include' -> 'sp1.mailsenders.netsuite.com'
OK for 'ip4' -> '192.29.88.0/25'
OK for 'ip4' -> '192.29.44.0/25'
OK for 'ip4' -> '192.29.151.128/25'
OK for 'ip4' -> '192.29.248.0/25'
OK for 'ip4' -> '192.29.216.0/25'
OK for 'include' -> 'sp2.mailsenders.netsuite.com'
OK for 'all' -> '-'
|
|
(purple.telstra.com → sent-via.netsuite.com → sp2.mailsenders.netsuite.com) The SPF consists of a permissible character set.
The SPF record of sp2.mailsenders.netsuite.com contains valid characters.
|
|
(purple.telstra.com → sent-via.netsuite.com → sp2.mailsenders.netsuite.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '192.174.81.16/28'
OK for 'ip4' -> '192.174.81.32/29'
OK for 'ip4' -> '192.174.82.55/32'
OK for 'ip4' -> '192.174.82.56/31'
OK for 'ip4' -> '192.174.85.168/32'
OK for 'ip4' -> '192.174.85.217/32'
OK for 'ip4' -> '192.174.89.136/32'
OK for 'ip4' -> '192.174.93.164/32'
OK for 'all' -> '~'
|
|
(purple.telstra.com → sent-via.netsuite.com → sp1.mailsenders.netsuite.com) The SPF consists of a permissible character set.
The SPF record of sp1.mailsenders.netsuite.com contains valid characters.
|
|
(purple.telstra.com → sent-via.netsuite.com → sp1.mailsenders.netsuite.com) Mechanisms of SPF-Record are valid
OK for 'v' -> 'spf1'
OK for 'ip4' -> '147.253.209.184/32'
OK for 'ip4' -> '147.253.211.175/32'
OK for 'ip4' -> '147.253.217.248/32'
OK for 'ip4' -> '147.253.218.73/32'
OK for 'ip4' -> '147.253.218.88/32'
OK for 'ip4' -> '147.253.219.153/32'
OK for 'ip4' -> '156.70.3.225/32'
OK for 'ip4' -> '156.70.3.226/31'
OK for 'ip4' -> '156.70.3.228/31'
OK for 'ip4' -> '156.70.4.175/32'
OK for 'ip4' -> '156.70.4.33/32'
OK for 'all' -> '~'
|
|
(purple.telstra.com) The SPF consists of a permissible character set.
The SPF record of purple.telstra.com contains valid characters.
|
SPF record available?
We found an SPF record for the domain.
Additionally authorized IPv4 addresses
Explicit IPv4 addresses in the SPF record have been authorized to send
Additional external SPF records
We could find other records authorized in the SPF record
Authorize IP addresses with markers
When SPF is evaluated, macros can specifically authorize Ip addresses based on the request or connection of the user or client (RFC7208 )
E-Mail handling
How should the checkHost() function of the e-mail server handle the e-mail? (syntax )
Will be forwarded to another SPF record?
There is no reference to any other SPF record
Are the server addresses allowed to send e-mails?
In the SPF entry the mechanism 'a' has not been set.
Additionally authorized A-records?
In addition to the A-Records stored in the DNS, we could not find any other records authorized in the SPF-Record.
Are the registered mail servers allowed to send e-mails?
In the SPF entry the mechanism 'mx' has not been set
Additionally authorized MX records
We could not find any other records authorized in the SPF record besides the MX records stored in the DNS
Additionally authorized IPv6 addresses
No explicit IPv6 addresses in the SPF record have been authorised to send
How is the sender informed?
The exp mechanism acts as a return to the sender if the IP address was not authorized to send and notify them. None was found.
PTR (obsolete mechanism)
The ptr mechanism is deprecated, slow and insecure and should not be used
PTR:
The ptr mechanism is deprecated, slow and insecure and should not be used
Receiver address
analysis.ra-missing
Amount of reports
analysis.rp-missing
Report selection
analysis.rr-missing
Unknown mechanisms
No unknown mechanisms were found in the SPF record.
Server IP Address
We have determined the following IP address for the domain:
No domain specified
Reverse address
We have determined the following name for the server IP address:
13.107.253.45
Get a first impression of the risk potential in your company
