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

The SPF record analysis was performed on 12.11.2024 at 20:43:59 clock.

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

Nameserverset:
ns0.leaseweb.com
ns1.leaseweb.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
85.17.130.15 LeaseWeb Netherlands B.V. blacklist 
85.17.130.16 LeaseWeb Netherlands B.V. blacklist 
89.238.146.98 M247 Europe SRL blacklist 
2a02:40:12::e M247 Europe SRL blacklist 
83.149.80.102 LeaseWeb Netherlands B.V. blacklist 
62.212.64.73 LeaseWeb Netherlands B.V. blacklist 
2001:1AF8:4100:A064::2525 LeaseWeb Netherlands B.V. blacklist 
213.227.128.225 LeaseWeb Netherlands B.V. blacklist 
2001:1af8:3100:1::2525 LeaseWeb Netherlands B.V. blacklist 
81.171.24.150 LeaseWeb Netherlands B.V. blacklist 
2001:1af8:4700:a129:1006::2525 LeaseWeb Netherlands B.V. blacklist 
212.32.242.82 LeaseWeb Netherlands B.V. blacklist 
2001:1af8:4700:a400:1007::2525 LeaseWeb Netherlands B.V. blacklist 
46.165.252.94 Leaseweb Deutschland GmbH blacklist 
2a00:c98:2200:af05:3::2525 Leaseweb Deutschland GmbH blacklist 
62.212.65.124 LeaseWeb Netherlands B.V. blacklist 
85.17.130.16 LeaseWeb Netherlands B.V. blacklist 
87.255.57.194 LeaseWeb Network B.V. blacklist 
212.95.49.3 Leaseweb Deutschland GmbH blacklist 
85.17.130.180 LeaseWeb Netherlands B.V. 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 
104.40.229.156 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.169.0.179 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
191.237.4.149 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.209.35.28 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.210.80.79 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.70.157.244 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.140.37.132 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.141.5.228 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.233.37.155 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.242.32.10 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.233.10.24 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.74.156.16 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.52.124.58 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.113.192.118 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
3.93.157.0/24
AMAZON-AES blacklist 
3.210.190.0/24
AMAZON-AES blacklist 
18.208.124.128/25
AMAZON-AES blacklist 
54.174.52.0/24
AMAZON-AES blacklist 
54.174.57.0/24
AMAZON-AES blacklist 
54.174.59.0/24
AMAZON-AES blacklist 
54.174.60.0/23
AMAZON-AES blacklist 
54.174.63.0/24
AMAZON-AES blacklist 
108.179.144.0/20
AMAZON-02 blacklist 
139.180.17.0/24
AMAZON-AES blacklist 
141.193.184.32/27
AMAZON-AES blacklist 
141.193.184.64/26
AMAZON-AES blacklist 
141.193.184.128/25
AMAZON-AES blacklist 
141.193.185.32/27
AMAZON-02 blacklist 
141.193.185.64/26
AMAZON-02 blacklist 
141.193.185.128/25
AMAZON-02 blacklist 
143.244.80.0/20
AMAZON-AES blacklist 
158.247.16.0/20
AMAZON-AES blacklist 
216.139.64.0/19
- blacklist 
155.56.208.100/30
SAP SE blacklist 
157.133.97.216/30
SAP SE blacklist 
169.145.66.70/31
- blacklist 
169.145.66.72/31
- blacklist 
130.214.105.240/28
SAP SE blacklist 
130.214.163.240/28
SAP SE blacklist 
130.214.134.192/28
SAP SE blacklist 
130.214.240.208/28
SAP SE blacklist 
185.250.239.148 Mailjet SAS blacklist 
185.250.239.168 Mailjet SAS blacklist 
185.250.239.190 Mailjet SAS blacklist 
198.244.59.30 MAILGUN blacklist 
198.244.59.33 MAILGUN blacklist 
198.244.59.35 MAILGUN blacklist 
198.61.254.21 RACKSPACE blacklist 
209.61.151.236 RMH-14 blacklist 
209.61.151.249 RMH-14 blacklist 
209.61.151.251 RMH-14 blacklist 
69.72.40.93 MAILGUN blacklist 
69.72.40.94/31
MAILGUN blacklist 
69.72.40.96/30
MAILGUN blacklist 
69.72.47.205 MAILGUN blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: leaseweb.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

85.17.130.15
85.17.130.16
89.238.146.98

Additionally authorized IPv6 addresses

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

2a02:40:12::e

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.mxout.ocom.com
v=spf1 ip4:83.149.80.102 ip4:62.212.64.73 ip6:2001:1AF8:4100:A064::2525 ip4:213.227.128.225 ip6:2001:1af8:3100:1::2525 ip4:81.171.24.150 ip6:2001:1af8:4700:a129:1006::2525 ip4:212.32.242.82 ip6:2001:1af8:4700:a400:1007::2525 ip4:46.165.252.94 ip6:2a00:c98:2200:af05:3::2525 ip4:62.212.65.124 ip4:85.17.130.16 ip4:87.255.57.194 ip4:212.95.49.3 ip4:85.17.130.180 -all
ipv4:
83.149.80.102
ipv4:
62.212.64.73
ipv4:
213.227.128.225
ipv4:
81.171.24.150
ipv4:
212.32.242.82
ipv4:
46.165.252.94
ipv4:
62.212.65.124
ipv4:
85.17.130.16
ipv4:
87.255.57.194
ipv4:
212.95.49.3
ipv4:
85.17.130.180
ipv6:
2001:1AF8:4100:A064::2525
ipv6:
2001:1af8:3100:1::2525
ipv6:
2001:1af8:4700:a129:1006::2525
ipv6:
2001:1af8:4700:a400:1007::2525
ipv6:
2a00:c98:2200:af05:3::2525
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.exclaimer.net
v=spf1 ip4:104.40.229.156 ip4:52.169.0.179 ip4:191.237.4.149 ip4:104.209.35.28 ip4:104.210.80.79 ip4:13.70.157.244 ip4:51.140.37.132 ip4:51.141.5.228 ip4:52.233.37.155 ip4:52.242.32.10 ip4:20.233.10.24 ip4:20.74.156.16 ip4:20.52.124.58 ip4:20.113.192.118 ~all
ipv4:
104.40.229.156
ipv4:
52.169.0.179
ipv4:
191.237.4.149
ipv4:
104.209.35.28
ipv4:
104.210.80.79
ipv4:
13.70.157.244
ipv4:
51.140.37.132
ipv4:
51.141.5.228
ipv4:
52.233.37.155
ipv4:
52.242.32.10
ipv4:
20.233.10.24
ipv4:
20.74.156.16
ipv4:
20.52.124.58
ipv4:
20.113.192.118
include:27248975.spf04.hubspotemail.net
v=spf1 ip4:3.93.157.0/24 ip4:3.210.190.0/24 ip4:18.208.124.128/25 ip4:54.174.52.0/24 ip4:54.174.57.0/24 ip4:54.174.59.0/24 ip4:54.174.60.0/23 ip4:54.174.63.0/24 ip4:108.179.144.0/20 ip4:139.180.17.0/24 ip4:141.193.184.32/27 ip4:141.193.184.64/26 ip4:141.193.184.128/25 ip4:141.193.185.32/27 ip4:141.193.185.64/26 ip4:141.193.185.128/25 ip4:143.244.80.0/20 ip4:158.247.16.0/20 ip4:216.139.64.0/19 -all
ipv4:
3.93.157.0/24
ipv4:
3.210.190.0/24
ipv4:
18.208.124.128/25
ipv4:
54.174.52.0/24
ipv4:
54.174.57.0/24
ipv4:
54.174.59.0/24
ipv4:
54.174.60.0/23
ipv4:
54.174.63.0/24
ipv4:
108.179.144.0/20
ipv4:
139.180.17.0/24
ipv4:
141.193.184.32/27
ipv4:
141.193.184.64/26
ipv4:
141.193.184.128/25
ipv4:
141.193.185.32/27
ipv4:
141.193.185.64/26
ipv4:
141.193.185.128/25
ipv4:
143.244.80.0/20
ipv4:
158.247.16.0/20
ipv4:
216.139.64.0/19
include:_spf.cmail.ondemand.com
v=spf1 ip4:155.56.208.100/30 ip4:157.133.97.216/30 ip4:169.145.66.70/31 ip4:169.145.66.72/31 ip4:130.214.105.240/28 ip4:130.214.163.240/28 ip4:130.214.134.192/28 ip4:130.214.240.208/28 ~all
ipv4:
155.56.208.100/30
ipv4:
157.133.97.216/30
ipv4:
169.145.66.70/31
ipv4:
169.145.66.72/31
ipv4:
130.214.105.240/28
ipv4:
130.214.163.240/28
ipv4:
130.214.134.192/28
ipv4:
130.214.240.208/28
include:mg-spf.greenhouse.io
v=spf1 ip4:185.250.239.148 ip4:185.250.239.168 ip4:185.250.239.190 ip4:198.244.59.30 ip4:198.244.59.33 ip4:198.244.59.35 ip4:198.61.254.21 ip4:209.61.151.236 ip4:209.61.151.249 ip4:209.61.151.251 ip4:69.72.40.93 ip4:69.72.40.94/31 ip4:69.72.40.96/30 ip4:69.72.47.205 ~all
ipv4:
185.250.239.148
ipv4:
185.250.239.168
ipv4:
185.250.239.190
ipv4:
198.244.59.30
ipv4:
198.244.59.33
ipv4:
198.244.59.35
ipv4:
198.61.254.21
ipv4:
209.61.151.236
ipv4:
209.61.151.249
ipv4:
209.61.151.251
ipv4:
69.72.40.93
ipv4:
69.72.40.94/31
ipv4:
69.72.40.96/30
ipv4:
69.72.47.205

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

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:

https-41-63-96-2.hhn.llnw.net

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