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

The SPF record analysis was performed on 04.05.2025 at 20:53:20 clock.

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

Nameserverset:
udns2.cscdns.uk
udns1.cscdns.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
81.167.55.11 Lyse Tele blacklist 
52.52.50.165 AMAZON-02 blacklist 
52.52.50.160 AMAZON-02 blacklist 
178.21.131.158 Webhuset AS blacklist 
81.93.169.182 Orange Business Digital Norway As blacklist 
81.93.169.183 Orange Business Digital Norway As 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 
62.209.53.0/24
Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
81.19.233.13 Sentia Denmark A/S blacklist 
62.50.78.150 GTT Communications Inc. blacklist 
116.213.108.60 - blacklist 
195.245.230.34 GOOGLE-CLOUD-PLATFORM blacklist 
82.118.73.116 CENTURYLINK-LEGACY-SAVVIS blacklist 
213.17.133.0/26
Netia SA blacklist 
35.158.18.46 AMAZON-02 blacklist 
91.227.208.0/24
AMAZON-02 blacklist 
198.2.128.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.132.0/22
THEROCKETSCIENCEGROUP blacklist 
198.2.136.0/23
THEROCKETSCIENCEGROUP blacklist 
198.2.145.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.186.0/23
THEROCKETSCIENCEGROUP blacklist 
205.201.131.128/25
THEROCKETSCIENCEGROUP blacklist 
205.201.134.128/25
THEROCKETSCIENCEGROUP blacklist 
205.201.136.0/23
THEROCKETSCIENCEGROUP blacklist 
205.201.139.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.177.0/24
THEROCKETSCIENCEGROUP blacklist 
198.2.178.0/23
THEROCKETSCIENCEGROUP blacklist 
198.2.180.0/24
THEROCKETSCIENCEGROUP blacklist 
213.251.39.226/28
GTT Communications Inc. blacklist 
213.131.182.34 Digital Space Group Limited blacklist 
213.241.1.58 Netia SA blacklist 
52.59.111.152 AMAZON-02 blacklist 
168.245.74.215 SENDGRID blacklist 
54.223.134.154 Beijing Guanghuan Xinwang Digital blacklist 
141.193.32.0/23
AMAZON-02 blacklist 
159.135.140.80/29
Rackspace Ltd. blacklist 
159.135.132.128/25
Rackspace Ltd. blacklist 
161.38.204.0/22
AMAZON-02 blacklist 
87.253.232.0/21
Mailjet SAS blacklist 
185.189.236.0/22
Mailjet SAS blacklist 
185.211.120.0/22
Mailjet SAS blacklist 
185.250.236.0/22
Mailjet SAS blacklist 
143.55.236.0/22
Mailjet SAS blacklist 
198.244.60.0/22
Mailjet SAS blacklist 
204.220.160.0/21
Mailjet SAS blacklist 
35.157.50.198 AMAZON-02 blacklist 
35.156.10.207 AMAZON-02 blacklist 
109.239.225.26 GlobalConnect AB blacklist 
2a00:1b60:0:4::26 GlobalConnect AB blacklist 
20.40.137.116/30
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.40.137.120/29
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.21.109.197 AMAZON-AES blacklist 
23.21.109.212 AMAZON-AES blacklist 
147.160.167.14 AMAZON-AES blacklist 
147.160.167.15 AMAZON-AES blacklist 
52.49.235.189 AMAZON-02 blacklist 
52.49.201.246 AMAZON-02 blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: jotun.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

81.167.55.11
52.52.50.165
52.52.50.160
178.21.131.158
81.93.169.182
81.93.169.183
62.209.53.0/24
81.19.233.13
62.50.78.150
116.213.108.60
195.245.230.34
82.118.73.116
213.17.133.0/26
35.158.18.46
91.227.208.0/24

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:spf.mandrillapp.com
v=spf1 ip4:198.2.128.0/24 ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.145.0/24 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.177.0/24 ip4:198.2.178.0/23 ip4:198.2.180.0/24 ~all
ipv4:
198.2.128.0/24
ipv4:
198.2.132.0/22
ipv4:
198.2.136.0/23
ipv4:
198.2.145.0/24
ipv4:
198.2.186.0/23
ipv4:
205.201.131.128/25
ipv4:
205.201.134.128/25
ipv4:
205.201.136.0/23
ipv4:
205.201.139.0/24
ipv4:
198.2.177.0/24
ipv4:
198.2.178.0/23
ipv4:
198.2.180.0/24
include:_spf.jotun.com
v=spf1 ip4:213.251.39.226/28 ip4:213.131.182.34 ip4:213.241.1.58 ip4:52.59.111.152 ip4:168.245.74.215 ip4:54.223.134.154 include:eu.mailgun.org ip4:35.157.50.198 ip4:35.156.10.207 ip4:109.239.225.26 ip6:2a00:1b60:0:4::26 ip4:20.40.137.116/30 ip4:20.40.137.120/29 include:_spf.psm.knowbe4.com -all
ipv4:
213.251.39.226/28
ipv4:
213.131.182.34
ipv4:
213.241.1.58
ipv4:
52.59.111.152
ipv4:
168.245.74.215
ipv4:
54.223.134.154
ipv4:
35.157.50.198
ipv4:
35.156.10.207
ipv4:
109.239.225.26
ipv4:
20.40.137.116/30
ipv4:
20.40.137.120/29
ipv6:
2a00:1b60:0:4::26
include:eu.mailgun.org
v=spf1 include:_spf.eu.mailgun.org ~all
include:_spf.eu.mailgun.org
v=spf1 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.60.0/22 ip4:204.220.160.0/21 ~all
ipv4:
141.193.32.0/23
ipv4:
159.135.140.80/29
ipv4:
159.135.132.128/25
ipv4:
161.38.204.0/22
ipv4:
87.253.232.0/21
ipv4:
185.189.236.0/22
ipv4:
185.211.120.0/22
ipv4:
185.250.236.0/22
ipv4:
143.55.236.0/22
ipv4:
198.244.60.0/22
ipv4:
204.220.160.0/21
include:_spf.psm.knowbe4.com
v=spf1 ip4:23.21.109.197 ip4:23.21.109.212 ip4:147.160.167.14 ip4:147.160.167.15 ip4:52.49.235.189 ip4:52.49.201.246 -all
ipv4:
23.21.109.197
ipv4:
23.21.109.212
ipv4:
147.160.167.14
ipv4:
147.160.167.15
ipv4:
52.49.235.189
ipv4:
52.49.201.246

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:

204.74.99.103

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