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

The SPF record analysis was performed on 02.05.2024 at 07:37:27 clock.

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

Nameserverset:
ns3-03.azure-dns.org
ns4-03.azure-dns.info
ns1-03.azure-dns.com
ns2-03.azure-dns.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
198.37.153.11 SENDGRID blacklist 
167.89.7.59 SENDGRID blacklist 
142.0.177.224 SRS-6-Z-7381 blacklist 
142.0.177.225 SRS-6-Z-7381 blacklist 
142.0.181.72 SOCKETLABS blacklist 
142.0.181.73 SOCKETLABS blacklist 
142.0.180.192 SOCKETLABS blacklist 
142.0.180.193 SOCKETLABS blacklist 
142.0.180.194 SOCKETLABS blacklist 
142.0.177.227 SRS-6-Z-7381 blacklist 
142.0.181.75 SOCKETLABS blacklist 
204.62.53.4 BULLHORN-INC-BOSTON blacklist 
52.129.17.4 BULLHORN-INC-BOSTON blacklist 
52.129.16.10 BULLHORN-INC-BOSTON blacklist 
40.127.192.217 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.113.71.161 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
195.130.217.0/24
Mimecast Services Limited blacklist 
91.220.42.0/24
Mimecast Services Limited blacklist 
146.101.78.0/24
TELSTRAEUROPELTD-BACKBONE Telstra Europe Ltd blacklist 
207.82.80.0/24
Mimecast Services Limited blacklist 
213.167.81.0/25
Mimecast Services Limited blacklist 
193.7.207.0/25
Mimecast Services Limited blacklist 
213.167.75.0/25
Mimecast Services Limited blacklist 
185.58.85.0/24
Mimecast Services Limited blacklist 
185.58.86.0/24
Mimecast Services Limited blacklist 
193.7.206.0/25
Mimecast Services Limited blacklist 
147.28.36.0/24
AMAZON-02 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 
164.138.221.186 SuperHosting.BG Ltd. 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 
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 
46.236.31.126 Pulsant (Scotland) Ltd blacklist 
46.249.214.124 Pulsant (Scotland) Ltd blacklist 
46.249.214.140 Pulsant (Scotland) Ltd blacklist 
46.249.208.219 Pulsant (Scotland) Ltd blacklist 
46.236.39.181 Pulsant (Scotland) Ltd blacklist 
46.236.35.2 Pulsant (Scotland) Ltd blacklist 
167.89.96.153 SENDGRID blacklist 
40.115.126.94 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: investigo.co.uk

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

167.89.96.153
40.115.126.94

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.bullhornmail.com
v=spf1 ip4:198.37.153.11 ip4:167.89.7.59 ip4:142.0.177.224 ip4:142.0.177.225 ip4:142.0.181.72 ip4:142.0.181.73 ip4:142.0.180.192 ip4:142.0.180.193 ip4:142.0.180.194 ip4:142.0.177.227 ip4:142.0.181.75 ip4:204.62.53.4 ip4:52.129.17.4 ip4:52.129.16.10 ~all
ipv4:
198.37.153.11
ipv4:
167.89.7.59
ipv4:
142.0.177.224
ipv4:
142.0.177.225
ipv4:
142.0.181.72
ipv4:
142.0.181.73
ipv4:
142.0.180.192
ipv4:
142.0.180.193
ipv4:
142.0.180.194
ipv4:
142.0.177.227
ipv4:
142.0.181.75
ipv4:
204.62.53.4
ipv4:
52.129.17.4
ipv4:
52.129.16.10
include:_spf.timesheetz.net
v=spf1 ip4:40.127.192.217 ip4:40.113.71.161 ~all
ipv4:
40.127.192.217
ipv4:
40.113.71.161
include:eu._netblocks.mimecast.com
v=spf1 ip4:195.130.217.0/24 ip4:91.220.42.0/24 ip4:146.101.78.0/24 ip4:207.82.80.0/24 ip4:213.167.81.0/25 ip4:193.7.207.0/25 ip4:213.167.75.0/25 ip4:185.58.85.0/24 ip4:185.58.86.0/24 ip4:193.7.206.0/25 ip4:147.28.36.0/24 ~all
ipv4:
195.130.217.0/24
ipv4:
91.220.42.0/24
ipv4:
146.101.78.0/24
ipv4:
207.82.80.0/24
ipv4:
213.167.81.0/25
ipv4:
193.7.207.0/25
ipv4:
213.167.75.0/25
ipv4:
185.58.85.0/24
ipv4:
185.58.86.0/24
ipv4:
193.7.206.0/25
ipv4:
147.28.36.0/24
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
include:mail.kanbanize.com
v=spf1 ip4:164.138.221.186
ipv4:
164.138.221.186
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
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.rsmemployerservices.co.uk
v=spf1 ip4:46.236.31.126 ip4:46.249.214.124 ip4:46.249.214.140 ip4:46.249.208.219 ip4:46.236.39.181 ip4:46.236.35.2 -all
ipv4:
46.236.31.126
ipv4:
46.249.214.124
ipv4:
46.249.214.140
ipv4:
46.249.208.219
ipv4:
46.236.39.181
ipv4:
46.236.35.2

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:

ec2-34-241-64-5.eu-west-1.compute.amazonaws.com

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