SPF Check:
mii.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 mii.com.
The SPF record for mii.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, 75 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 22.12.2024 at 20:05:35 clock.

Lookup for the domain:
mii.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 mii.com 

Nameserverset:
dns4.p01.nsone.net
dns1.p01.nsone.net
dns2.p01.nsone.net
dns3.p01.nsone.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
208.86.201.94 PROOFPOINT-ASN-US-EAST blacklist 
148.163.156.241 PROOFPOINT-ASN-US-WEST 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 
198.245.81.0/24
SALESFORCE blacklist 
136.147.176.0/24
SALESFORCE blacklist 
13.111.0.0/16
SALESFORCE blacklist 
136.147.182.0/24
SALESFORCE blacklist 
136.147.135.0/24
SALESFORCE blacklist 
199.122.123.0/24
SALESFORCE 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 
159.112.242.217 MAILGUN blacklist 
167.89.0.0/17
SENDGRID blacklist 
208.117.48.0/20
SENDGRID blacklist 
50.31.32.0/19
SENDGRID blacklist 
198.37.144.0/20
SENDGRID blacklist 
198.21.0.0/21
SENDGRID blacklist 
192.254.112.0/20
SENDGRID blacklist 
168.245.0.0/17
SENDGRID blacklist 
149.72.0.0/16
AMAZON-AES blacklist 
159.183.0.0/16
SENDGRID blacklist 
223.165.113.0/24
SENDGRID blacklist 
223.165.115.0/24
SENDGRID blacklist 
223.165.118.0/23
SENDGRID blacklist 
223.165.120.0/23
SENDGRID blacklist 
192.245.140.5 MII-DOMAIN blacklist 
198.147.156.3 MII-DOMAIN blacklist 
80.6.91.150 Virgin Media blacklist 
107.20.210.250 AMAZON-AES blacklist 
52.1.14.157 AMAZON-AES blacklist 
67.23.194.116 WILINE blacklist 
128.242.118.200 NTT-LTD-2914 blacklist 
121.240.21.82 TATA Communications formerly VSNL is Leading ISP blacklist 
139.130.130.250 Telstra Limited blacklist 
138.217.133.206 Telstra Limited blacklist 
132.145.68.85 ORACLE-BMC-31898 blacklist 
50.31.48.205 SENDGRID blacklist 
208.117.55.133 SENDGRID blacklist 
149.72.113.166 SENDGRID blacklist 
159.183.107.55 SENDGRID blacklist 
3.217.186.95 AMAZON-AES blacklist 
13.110.74.0/24
SALESFORCE blacklist 
13.110.78.0/24
SALESFORCE blacklist 
209.85.220.69 GOOGLE blacklist 
80.12.242.0/24
Orange blacklist 
209.85.128.0/24
GOOGLE blacklist 
209.85.166.0/24
GOOGLE blacklist 
209.85.220.97 GOOGLE blacklist 
192.249.118.159 INMOTION blacklist 
44.192.35.0/24
AMAZON-AES blacklist 
54.173.83.138 AMAZON-AES blacklist 
107.23.16.222 AMAZON-AES blacklist 
64.78.239.116 ASN-FLEXENTIAL blacklist 
123.25.128.188 VNPT Corp blacklist 
52.142.171.106 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: mii.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

192.245.140.5
198.147.156.3
80.6.91.150
107.20.210.250
52.1.14.157
67.23.194.116
128.242.118.200
121.240.21.82
139.130.130.250
138.217.133.206
132.145.68.85
50.31.48.205
208.117.55.133
149.72.113.166
159.183.107.55
3.217.186.95
13.110.74.0/24
13.110.78.0/24
209.85.220.69
80.12.242.0/24
209.85.128.0/24
209.85.166.0/24
209.85.220.97
192.249.118.159
44.192.35.0/24
54.173.83.138
107.23.16.222
64.78.239.116
123.25.128.188
52.142.171.106

Additional external SPF records

We could find other records authorized in the SPF record

include:spf-00276401.pphosted.com
v=spf1 ip4:208.86.201.94 ip4:148.163.156.241
ipv4:
208.86.201.94
ipv4:
148.163.156.241
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:_spf.salesforce.com
v=spf1 exists:%{i}._spf.mta.salesforce.com -all
include:aspmx.pardot.com
v=spf1 include:et._spf.pardot.com -all
include:et._spf.pardot.com
v=spf1 ip4:198.245.81.0/24 ip4:136.147.176.0/24 ip4:13.111.0.0/16 ip4:136.147.182.0/24 ip4:136.147.135.0/24 ip4:199.122.123.0/24 -all
ipv4:
198.245.81.0/24
ipv4:
136.147.176.0/24
ipv4:
13.111.0.0/16
ipv4:
136.147.182.0/24
ipv4:
136.147.135.0/24
ipv4:
199.122.123.0/24
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
include:mail.clinchtalent.com
v=spf1 ip4:159.112.242.217 ~all
ipv4:
159.112.242.217
include:sendgrid.net
v=spf1 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 include:ab.sendgrid.net ~all
ipv4:
167.89.0.0/17
ipv4:
208.117.48.0/20
ipv4:
50.31.32.0/19
ipv4:
198.37.144.0/20
ipv4:
198.21.0.0/21
ipv4:
192.254.112.0/20
ipv4:
168.245.0.0/17
ipv4:
149.72.0.0/16
ipv4:
159.183.0.0/16
include:ab.sendgrid.net
v=spf1 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ~all
ipv4:
223.165.113.0/24
ipv4:
223.165.115.0/24
ipv4:
223.165.118.0/23
ipv4:
223.165.120.0/23

E-Mail handling

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

~all
SoftFail (non-compliant e-mails are accepted but marked)

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:

192.0.66.208

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.
© 2024 nicmanager.com.   All rights reserved.
nicmanager