SPF Check:
navistar.com

1. Specify domain name

Enter a domain to be checked for the SPF record
2. Specify IP address (optional)
Enter any IP address to check if it is authorized to send e-mails by the SPF record

What is the SPF lookup for?

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.

Loading...

SPF check passed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 0 errors
  •   Email Anti-Spoofing: Good
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain navistar.com.
The SPF record for navistar.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, 61 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 13.05.2025 at 12:42:59 clock.

Lookup for the domain:
navistar.com
IP address to be checked:
no IP address specified
Solve your problems in no time
Guaranteed measurable improvement for email deliverability and domain security
Solve your problems in no time

Evaluation for the domain navistar.com 

Nameserverset:
brknspn3.navistar.com
brknspn2.navistar.com
whqnspn1.navistar.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
13.90.80.167 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
57.151.23.205 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
4.14.167.184/29
LEVEL3 blacklist 
12.37.12.16/29
ATT-INTERNET4 blacklist 
63.243.89.139 AMAZON-02 blacklist 
64.20.169.131 CROWNCASTLE-AS46887 blacklist 
65.74.169.93 QTS-SAC blacklist 
62.13.136.218 GetOnline Limited blacklist 
167.6.247.61 INTERNATIONALDELIVERS blacklist 
167.6.247.79 INTERNATIONALDELIVERS blacklist 
40.92.0.0/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.107.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.100.0.0/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.102.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.103.0.0/17
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.47.0.0/17
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f400::/48
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403::/49
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:8000::/51
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:c000::/51
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:f000::/52
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
167.6.37.80/28
INTERNATIONALDELIVERS blacklist 
104.46.104.121 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
167.6.109.12/28
INTERNATIONALDELIVERS blacklist 
162.247.160.0/21
AMAZON-02 blacklist 
72.21.37.96/27
Rackspace Ltd. blacklist 
35.155.180.221 AMAZON-02 blacklist 
35.162.39.193 AMAZON-02 blacklist 
52.34.215.70 AMAZON-02 blacklist 
52.35.35.11 AMAZON-02 blacklist 
52.40.111.107 AMAZON-02 blacklist 
54.202.190.42 AMAZON-02 blacklist 
54.218.191.98 AMAZON-02 blacklist 
54.218.231.65 AMAZON-02 blacklist 
54.245.150.167 AMAZON-02 blacklist 
34.249.193.113 AMAZON-02 blacklist 
34.252.171.78 AMAZON-02 blacklist 
34.255.32.182 AMAZON-02 blacklist 
52.18.19.18 AMAZON-02 blacklist 
52.209.54.124 AMAZON-02 blacklist 
52.215.34.232 AMAZON-02 blacklist 
52.50.50.63 AMAZON-02 blacklist 
54.171.28.234 AMAZON-02 blacklist 
54.77.8.64 AMAZON-02 blacklist 
166.78.81.73/32
RACKSPACE blacklist 
98.129.166.181/32
RMH-14 blacklist 
162.13.228.166/32
Rackspace Ltd. blacklist 
94.236.35.193/32
Rackspace Ltd. blacklist 
168.245.109.52/32
SENDGRID blacklist 
199.255.192.0/22
AMAZON-02 blacklist 
199.127.232.0/22
AMAZON-02 blacklist 
54.240.0.0/18
AMAZON-02 blacklist 
69.169.224.0/20
AMAZON-02 blacklist 
23.249.208.0/20
AMAZON-02 blacklist 
23.251.224.0/19
AMAZON-02 blacklist 
76.223.176.0/20
AMAZON-02 blacklist 
54.240.64.0/19
AMAZON-AES blacklist 
54.240.96.0/19
AMAZON-02 blacklist 
76.223.128.0/19
AMAZON-02 blacklist 
216.221.160.0/19
AMAZON-02 blacklist 
206.55.144.0/20
AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: navistar.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Additionally authorized IPv4 addresses

Explicit IPv4 addresses in the SPF record have been authorized to send

13.90.80.167
57.151.23.205
4.14.167.184/29
12.37.12.16/29
63.243.89.139
64.20.169.131
65.74.169.93
62.13.136.218
167.6.247.61
167.6.247.79

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all
ipv4:
40.92.0.0/15
ipv4:
40.107.0.0/16
ipv4:
52.100.0.0/15
ipv4:
52.102.0.0/16
ipv4:
52.103.0.0/17
ipv4:
104.47.0.0/17
ipv6:
2a01:111:f400::/48
ipv6:
2a01:111:f403::/49
ipv6:
2a01:111:f403:8000::/51
ipv6:
2a01:111:f403:c000::/51
ipv6:
2a01:111:f403:f000::/52
include:spfa.navistar.com
v=spf1 ip4:167.6.37.80/28 ip4:104.46.104.121 ip4:167.6.109.12/28 include:_spf.salesforce.com include:_netblocks.icims.com include:_spf.mitracloud.com include:amazonses.com -all
ipv4:
167.6.37.80/28
ipv4:
104.46.104.121
ipv4:
167.6.109.12/28
include:_spf.salesforce.com
v=spf1 exists:%{i}._spf.mta.salesforce.com -all
include:_netblocks.icims.com
v=spf1 ip4:162.247.160.0/21 ip4:72.21.37.96/27 ip4:35.155.180.221 ip4:35.162.39.193 ip4:52.34.215.70 ip4:52.35.35.11 ip4:52.40.111.107 ip4:54.202.190.42 ip4:54.218.191.98 ip4:54.218.231.65 ip4:54.245.150.167 ip4:34.249.193.113 ip4:34.252.171.78 ip4:34.255.32.182 ip4:52.18.19.18 ip4:52.209.54.124 ip4:52.215.34.232 ip4:52.50.50.63 ip4:54.171.28.234 ip4:54.77.8.64 -all
ipv4:
162.247.160.0/21
ipv4:
72.21.37.96/27
ipv4:
35.155.180.221
ipv4:
35.162.39.193
ipv4:
52.34.215.70
ipv4:
52.35.35.11
ipv4:
52.40.111.107
ipv4:
54.202.190.42
ipv4:
54.218.191.98
ipv4:
54.218.231.65
ipv4:
54.245.150.167
ipv4:
34.249.193.113
ipv4:
34.252.171.78
ipv4:
34.255.32.182
ipv4:
52.18.19.18
ipv4:
52.209.54.124
ipv4:
52.215.34.232
ipv4:
52.50.50.63
ipv4:
54.171.28.234
ipv4:
54.77.8.64
include:_spf.mitracloud.com
v=spf1 include:_netblocks.mitracloud.com ~all
include:_netblocks.mitracloud.com
v=spf1 ip4:166.78.81.73/32 ip4:98.129.166.181/32 ip4:162.13.228.166/32 ip4:94.236.35.193/32 ip4:168.245.109.52/32 ~all
ipv4:
166.78.81.73/32
ipv4:
98.129.166.181/32
ipv4:
162.13.228.166/32
ipv4:
94.236.35.193/32
ipv4:
168.245.109.52/32
include:amazonses.com
v=spf1 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/19 ip4:54.240.96.0/19 ip4:76.223.128.0/19 ip4:216.221.160.0/19 ip4:206.55.144.0/20 -all
ipv4:
199.255.192.0/22
ipv4:
199.127.232.0/22
ipv4:
54.240.0.0/18
ipv4:
69.169.224.0/20
ipv4:
23.249.208.0/20
ipv4:
23.251.224.0/19
ipv4:
76.223.176.0/20
ipv4:
54.240.64.0/19
ipv4:
54.240.96.0/19
ipv4:
76.223.128.0/19
ipv4:
216.221.160.0/19
ipv4:
206.55.144.0/20

E-Mail handling

How should the checkHost() function of the e-mail server handle the e-mail? (syntax )

-all
Fail (non-compliant e-mails are rejected)

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

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 )

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.

Recently performed SPF lookups

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:

40.90.64.52

Free whitepaper

How secure is your domain?

  • Practical with many examples
  • the basics of domain risk management summarized in 20 pages
  • Checklist with 53 questions on 14 risk areas

Get a first impression of the risk potential in your company

⮩ Download "Domain Risk Management" for free
All offers are aimed at traders, not end consumers and do not include VAT.
© 2025 nicmanager.com.   All rights reserved.
nicmanager