SPF Check:
greenduck.co.uk

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 greenduck.co.uk.
The SPF record for greenduck.co.uk 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, 95 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 22.05.2024 at 05:13:35 clock.

Lookup for the domain:
greenduck.co.uk
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 greenduck.co.uk 

Nameserverset:
angela.ns.cloudflare.com
arturo.ns.cloudflare.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
37.1.99.133 Netservers Limited blacklist 
37.1.98.232 Netservers Limited blacklist 
104.21.75.150 - CLOUDFLARENET blacklist 
172.67.177.229 - CLOUDFLARENET blacklist 
2606:4700:3034:0:0:0:6815:4b96 - CLOUDFLARENET blacklist 
2606:4700:3033:0:0:0:ac43:b1e5 - CLOUDFLARENET blacklist 
37.1.98.232 Netservers Limited blacklist 
37.1.99.133 Netservers Limited blacklist 
54.175.226.230/32
AMAZON-AES blacklist 
54.175.120.115/32
AMAZON-AES blacklist 
54.84.157.192/32
AMAZON-AES blacklist 
54.173.41.109/32
AMAZON-AES blacklist 
54.86.73.129/32
AMAZON-AES blacklist 
63.150.4.232/31
CENTURYLINK-US-LEGACY-QWEST blacklist 
100.42.120.128/27
SWITCH-LTD blacklist 
100.42.115.0/27
- blacklist 
69.84.129.224/27
COLOSPACE blacklist 
54.66.220.193/32
AMAZON-02 blacklist 
54.66.200.109/32
AMAZON-02 blacklist 
54.77.78.8/32
AMAZON-02 blacklist 
54.77.200.220/32
AMAZON-02 blacklist 
207.58.147.64/28
LEASEWEB-USA-WDC blacklist 
216.22.15.224/27
LEASEWEB-USA-WDC blacklist 
43.228.184.0/22
Arelion Sweden AB blacklist 
103.47.204.0/22
Arelion Sweden AB blacklist 
103.2.140.0/22
SERVERCENTRAL blacklist 
203.31.36.0/22
SERVERCENTRAL blacklist 
170.10.68.0/22
Wholesale Services Provider blacklist 
158.120.80.0/21
SERVERCENTRAL 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/14
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 
54.79.63.203 AMAZON-02 blacklist 
52.65.123.89 AMAZON-02 blacklist 
54.206.45.223 AMAZON-02 blacklist 
52.86.161.89 AMAZON-AES blacklist 
52.21.190.16 AMAZON-AES blacklist 
52.31.42.202 AMAZON-02 blacklist 
52.17.58.100 AMAZON-02 blacklist 
52.62.216.13 AMAZON-02 blacklist 
35.170.112.17 AMAZON-AES blacklist 
18.205.0.32 AMAZON-AES blacklist 
18.210.112.189 AMAZON-AES blacklist 
18.235.164.182 AMAZON-AES blacklist 
18.215.201.255 AMAZON-AES blacklist 
18.214.171.80 AMAZON-AES blacklist 
52.205.22.176 AMAZON-AES blacklist 
52.2.115.93 AMAZON-AES blacklist 
34.206.23.58 AMAZON-AES blacklist 
52.22.53.116 AMAZON-AES blacklist 
18.204.147.22 AMAZON-AES blacklist 
13.236.237.174 AMAZON-02 blacklist 
13.54.181.101 AMAZON-02 blacklist 
35.183.213.46 AMAZON-02 blacklist 
23.22.12.8 AMAZON-AES blacklist 
34.239.15.245 AMAZON-AES blacklist 
52.19.234.198 AMAZON-02 blacklist 
23.22.12.8 AMAZON-AES blacklist 
94.229.130.25 Netservers Limited blacklist 
83.138.173.195 Rackspace Ltd. blacklist 
83.138.173.194 Rackspace Ltd. blacklist 
83.138.173.199 Rackspace Ltd. blacklist 
92.52.83.121 Rackspace Ltd. blacklist 
89.234.12.164 Rackspace Ltd. blacklist 
89.234.12.161 Rackspace Ltd. blacklist 
185.123.97.227 - blacklist 
94.229.130.29 Netservers Limited blacklist 
51.140.37.132 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.141.5.228 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
37.1.99.129 Netservers Limited blacklist 
87.115.164.45 British Telecommunications PLC blacklist 
185.132.181.6 Proofpoint, Inc. blacklist 
185.132.181.8 Proofpoint, Inc. blacklist 
185.183.29.38 Proofpoint, Inc. blacklist 
185.132.181.11 Proofpoint, Inc. blacklist 
185.183.29.37 Proofpoint, Inc. blacklist 
185.132.181.7 Proofpoint, Inc. blacklist 
185.183.29.34 Proofpoint, Inc. blacklist 
91.209.104.157 Proofpoint, Inc. blacklist 
185.183.29.36 Proofpoint, Inc. blacklist 
185.183.29.39 Proofpoint, Inc. blacklist 
185.183.29.35 Proofpoint, Inc. blacklist 
185.132.181.13 Proofpoint, Inc. blacklist 
185.132.181.9 Proofpoint, Inc. blacklist 
185.183.29.32 Proofpoint, Inc. blacklist 
185.132.181.12 Proofpoint, Inc. blacklist 
185.132.181.10 Proofpoint, Inc. blacklist 
185.183.29.33 Proofpoint, Inc. blacklist 
91.209.104.158 Proofpoint, Inc. blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: greenduck.co.uk

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

104.21.75.150
172.67.177.229
2606:4700:3034:0:0:0:6815:4b96
2606:4700:3033:0:0:0:ac43:b1e5

Additionally authorized A-records?

In addition to the A-records stored in the DNS, we were able to find further records authorized in the SPF-record

185.132.181.6
185.132.181.8
185.183.29.38
185.132.181.11
185.183.29.37
185.132.181.7
185.183.29.34
91.209.104.157
185.183.29.36
185.183.29.39
185.183.29.35
185.132.181.13
185.132.181.9
185.183.29.32
185.132.181.12
185.132.181.10
185.183.29.33
91.209.104.158

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

cbg-esg-n2.greenduck.net
lon-esg-n1.greenduck.net

Additionally authorized IPv4 addresses

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

37.1.98.232
37.1.99.133
94.229.130.25
83.138.173.195
83.138.173.194
83.138.173.199
92.52.83.121
89.234.12.164
89.234.12.161
185.123.97.227
94.229.130.29
51.140.37.132
51.141.5.228
37.1.99.129
87.115.164.45

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.myconnectwise.net
v=spf1 ip4:54.175.226.230/32 ip4:54.175.120.115/32 ip4:54.84.157.192/32 ip4:54.173.41.109/32 ip4:54.86.73.129/32 ip4:63.150.4.232/31 ip4:100.42.120.128/27 ip4:100.42.115.0/27 ip4:69.84.129.224/27 ip4:54.66.220.193/32 ip4:54.66.200.109/32 ip4:54.77.78.8/32 ip4:54.77.200.220/32 include:spf.smtp2go.com ~all
ipv4:
54.175.226.230/32
ipv4:
54.175.120.115/32
ipv4:
54.84.157.192/32
ipv4:
54.173.41.109/32
ipv4:
54.86.73.129/32
ipv4:
63.150.4.232/31
ipv4:
100.42.120.128/27
ipv4:
100.42.115.0/27
ipv4:
69.84.129.224/27
ipv4:
54.66.220.193/32
ipv4:
54.66.200.109/32
ipv4:
54.77.78.8/32
ipv4:
54.77.200.220/32
include:spf.smtp2go.com
v=spf1 ip4:207.58.147.64/28 ip4:216.22.15.224/27 ip4:43.228.184.0/22 ip4:103.47.204.0/22 ip4:103.2.140.0/22 ip4:203.31.36.0/22 ip4:170.10.68.0/22 ip4:158.120.80.0/21 ~all
ipv4:
207.58.147.64/28
ipv4:
216.22.15.224/27
ipv4:
43.228.184.0/22
ipv4:
103.47.204.0/22
ipv4:
103.2.140.0/22
ipv4:
203.31.36.0/22
ipv4:
170.10.68.0/22
ipv4:
158.120.80.0/21
include:spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/14 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/14
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.deskdirector.com
v=spf1 include:spf-1.deskdirector.com include:spf-2.deskdirector.com -all
include:spf-1.deskdirector.com
v=spf1 ip4:54.79.63.203 ip4:52.65.123.89 ip4:54.206.45.223 ip4:52.86.161.89 ip4:52.21.190.16 ip4:52.31.42.202 ip4:52.17.58.100 ip4:52.62.216.13 ip4:35.170.112.17 ip4:18.205.0.32 ip4:18.210.112.189 ip4:18.235.164.182 ip4:18.215.201.255 -all
ipv4:
54.79.63.203
ipv4:
52.65.123.89
ipv4:
54.206.45.223
ipv4:
52.86.161.89
ipv4:
52.21.190.16
ipv4:
52.31.42.202
ipv4:
52.17.58.100
ipv4:
52.62.216.13
ipv4:
35.170.112.17
ipv4:
18.205.0.32
ipv4:
18.210.112.189
ipv4:
18.235.164.182
ipv4:
18.215.201.255
include:spf-2.deskdirector.com
v=spf1 ip4:18.214.171.80 ip4:52.205.22.176 ip4:52.2.115.93 ip4:34.206.23.58 ip4:52.22.53.116 ip4:18.204.147.22 ip4:13.236.237.174 ip4:13.54.181.101 ip4:35.183.213.46 ip4:23.22.12.8 ip4:34.239.15.245 ip4:52.19.234.198 ip4:23.22.12.8 -all
ipv4:
18.214.171.80
ipv4:
52.205.22.176
ipv4:
52.2.115.93
ipv4:
34.206.23.58
ipv4:
52.22.53.116
ipv4:
18.204.147.22
ipv4:
13.236.237.174
ipv4:
13.54.181.101
ipv4:
35.183.213.46
ipv4:
23.22.12.8
ipv4:
34.239.15.245
ipv4:
52.19.234.198
ipv4:
23.22.12.8

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 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:

172.67.177.229

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   Connected by Team Internet