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

The SPF record analysis was performed on 18.11.2024 at 21:23:08 clock.

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

Nameserverset:
ns2.he.net
ns1.he.net
ns3.he.net
ns4.he.net
ns5.he.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
217.26.61.232 Hostpoint AG blacklist 
52.101.185.12 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.187.1 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.185.13 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.185.14 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
148.139.1.2 SNC blacklist 
212.80.96.0/21
Softec AG blacklist 
2a01:7480:1:100::/64
Softec AG blacklist 
155.56.208.100/30
SAP SE blacklist 
157.133.97.216/30
SAP SE blacklist 
169.145.66.70/31
- blacklist 
148.139.29.85 SNC blacklist 
149.96.6.110 SNC blacklist 
148.139.28.85 SNC blacklist 
149.96.5.110 SNC blacklist 
104.40.229.156 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.169.0.179 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
169.145.66.72/31
- blacklist 
40.127.253.48/28
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
18.169.108.4 AMAZON-02 blacklist 
155.56.208.99/28
SAP SE blacklist 
35.214.212.238 GOOGLE blacklist 
130.214.156.249 SAP SE blacklist 
130.214.156.205 SAP SE blacklist 
35.214.213.218 GOOGLE blacklist 
40.107.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.50.220.144/28
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
46.235.17.249 Koesio Corporate IT SAS blacklist 
46.235.17.250 Koesio Corporate IT SAS blacklist 
46.235.17.251 Koesio Corporate IT SAS blacklist 
46.235.17.252 Koesio Corporate IT SAS blacklist 
198.21.6.129 SENDGRID blacklist 
20.79.220.33 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.79.222.204 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.94.95.171 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
137.116.240.241 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
130.214.193.78/27
SAP SE blacklist 
3.66.14.43 AMAZON-02 blacklist 
52.58.241.178 AMAZON-02 blacklist 
37.98.232.2 - blacklist 
148.139.0.31 SNC blacklist 
148.139.1.31 SNC blacklist 
148.139.2.2 SNC blacklist 
148.139.3.2 SNC blacklist 
148.139.0.2 SNC blacklist 
199.91.139.22 SNC blacklist 
199.91.139.23 SNC blacklist 
199.91.139.24 SNC 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 
3.71.24.100 AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: chainiq.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Are the server addresses allowed to send e-mails?

The mechanism 'a' was set in the SPF record. The following IP addresses are allowed to send

217.26.61.232

Are the registered mail servers allowed to send e-mails?

The mechanism 'mx' was set in the SPF entry. The following hosts are allowed to send

chainiq-com.mail.protection.outlook.com
chainiq-com.mail.protection.outlook.com
chainiq-com.mail.protection.outlook.com
chainiq-com.mail.protection.outlook.com

Additionally authorized MX records

In addition to the MX records stored in the DNS, we were able to find other records authorized in the SPF record

service-now.com

Additionally authorized IPv4 addresses

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

148.139.1.2
212.80.96.0/21
155.56.208.100/30
157.133.97.216/30
169.145.66.70/31

Additionally authorized IPv6 addresses

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

2a01:7480:1:100::/64

Additional external SPF records

We could find other records authorized in the SPF record

include:spf2.chainiq.com
v=spf1 ip4:104.40.229.156 ip4:52.169.0.179 ip4:169.145.66.72/31 ip4:40.127.253.48/28 ip4:18.169.108.4 ip4:155.56.208.99/28 ip4:35.214.212.238 ip4:130.214.156.249 ip4:130.214.156.205 ip4:35.214.213.218 ip4:40.107.0.0/16 ~all
ipv4:
104.40.229.156
ipv4:
52.169.0.179
ipv4:
169.145.66.72/31
ipv4:
40.127.253.48/28
ipv4:
18.169.108.4
ipv4:
155.56.208.99/28
ipv4:
35.214.212.238
ipv4:
130.214.156.249
ipv4:
130.214.156.205
ipv4:
35.214.213.218
ipv4:
40.107.0.0/16
include:spf.chainiq.com
v=spf1 ip4:20.50.220.144/28 ip4:46.235.17.249 ip4:46.235.17.250 ip4:46.235.17.251 ip4:46.235.17.252 ip4:198.21.6.129 ip4:20.79.220.33 ip4:20.79.222.204 ip4:13.94.95.171 ip4:137.116.240.241 ip4:130.214.193.78/27 ip4:3.66.14.43 ip4:52.58.241.178 -all
ipv4:
20.50.220.144/28
ipv4:
46.235.17.249
ipv4:
46.235.17.250
ipv4:
46.235.17.251
ipv4:
46.235.17.252
ipv4:
198.21.6.129
ipv4:
20.79.220.33
ipv4:
20.79.222.204
ipv4:
13.94.95.171
ipv4:
137.116.240.241
ipv4:
130.214.193.78/27
ipv4:
3.66.14.43
ipv4:
52.58.241.178
include:spf3.chainiq.com
v=spf1 ip4:37.98.232.2 ip4:148.139.0.31 ip4:148.139.1.31 ip4:148.139.2.2 ip4:148.139.3.2 ip4:148.139.0.2 ip4:199.91.139.22 ip4:199.91.139.23 ip4:199.91.139.24 include:spf.protection.outlook.com include:_spf.salesforce.com ip4:3.71.24.100 -all
ipv4:
37.98.232.2
ipv4:
148.139.0.31
ipv4:
148.139.1.31
ipv4:
148.139.2.2
ipv4:
148.139.3.2
ipv4:
148.139.0.2
ipv4:
199.91.139.22
ipv4:
199.91.139.23
ipv4:
199.91.139.24
ipv4:
3.71.24.100
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

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

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.

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:

sl2354.web.hostpoint.ch

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