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

The SPF record analysis was performed on 02.05.2024 at 10:37:34 clock.

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

Nameserverset:
udns1.cscdns.net
udns2.cscdns.uk
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
64.253.45.78 Next Connex Ltd blacklist 
213.167.71.123 Foreshore Limited blacklist 
184.106.6.191 RACKSPACE blacklist 
72.3.150.219 RMH-14 blacklist 
83.138.131.52 Rackspace Ltd. blacklist 
185.13.246.162 Razorblue Ltd blacklist 
148.139.3.2 SNC blacklist 
148.139.2.2 SNC blacklist 
213.212.88.254 Redcentric Solutions Ltd blacklist 
213.212.125.154 Redcentric Solutions Ltd blacklist 
213.212.110.122 Redcentric Solutions Ltd blacklist 
213.212.88.234 Redcentric Solutions Ltd blacklist 
213.212.110.75 Redcentric Solutions Ltd blacklist 
213.212.88.246 Redcentric Solutions Ltd blacklist 
155.46.141.3 THOMSON-REUTERS blacklist 
155.46.145.4 THOMSON-REUTERS blacklist 
155.46.138.0/24
THOMSON-REUTERS blacklist 
155.46.142.0/24
THOMSON-REUTERS blacklist 
155.46.146.0/24
THOMSON-REUTERS blacklist 
155.46.168.0/24
THOMSON-REUTERS blacklist 
155.46.173.0/24
THOMSON-REUTERS blacklist 
163.231.255.0/24
THOMSON-REUTERS blacklist 
167.68.21.0/24
THOMSON-REUTERS blacklist 
167.68.25.0/24
THOMSON-REUTERS 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 
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 
20.101.192.132 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.101.192.146 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.50.129.173 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.103.134.61 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.103.87.180 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.103.83.233 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
185.108.112.76 Signet B.V. blacklist 
20.76.46.41 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.54.177.205 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
49.12.39.70 Hetzner Online GmbH blacklist 
185.41.28.0/22
Sendinblue SAS blacklist 
94.143.16.0/21
Sendinblue SAS blacklist 
185.24.144.0/22
Sendinblue SAS blacklist 
153.92.224.0/19
Sendinblue SAS blacklist 
213.32.128.0/18
Sendinblue SAS blacklist 
185.107.232.0/22
Sendinblue SAS blacklist 
77.32.128.0/18
Sendinblue SAS blacklist 
77.32.192.0/19
Sendinblue SAS blacklist 
212.146.192.0/18
Sendinblue SAS blacklist 
172.246.0.0/18
Sendinblue SAS blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: simmons-simmons.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

64.253.45.78
213.167.71.123
184.106.6.191
72.3.150.219
83.138.131.52
185.13.246.162
148.139.3.2
148.139.2.2

Additional external SPF records

We could find other records authorized in the SPF record

include:_gbr._spf.highqsolutions.com
v=spf1 ip4:213.212.88.254 ip4:213.212.125.154 ip4:213.212.110.122 ip4:213.212.88.234 ip4:213.212.110.75 ip4:213.212.88.246 ip4:155.46.141.3 ip4:155.46.145.4 include:spf.relay.thomsonreuters.com ~all
ipv4:
213.212.88.254
ipv4:
213.212.125.154
ipv4:
213.212.110.122
ipv4:
213.212.88.234
ipv4:
213.212.110.75
ipv4:
213.212.88.246
ipv4:
155.46.141.3
ipv4:
155.46.145.4
include:spf.relay.thomsonreuters.com
v=spf1 ip4:155.46.138.0/24 ip4:155.46.142.0/24 ip4:155.46.146.0/24 ip4:155.46.168.0/24 ip4:155.46.173.0/24 ip4:163.231.255.0/24 ip4:167.68.21.0/24 ip4:167.68.25.0/24 ~all
ipv4:
155.46.138.0/24
ipv4:
155.46.142.0/24
ipv4:
155.46.146.0/24
ipv4:
155.46.168.0/24
ipv4:
155.46.173.0/24
ipv4:
163.231.255.0/24
ipv4:
167.68.21.0/24
ipv4:
167.68.25.0/24
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: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.mail.services.bastion365.net
v=spf1 ip4:20.101.192.132 ip4:20.101.192.146 ip4:20.50.129.173 ip4:20.103.134.61 ip4:20.103.87.180 ip4:20.103.83.233 ip4:185.108.112.76 ip4:20.76.46.41 ip4:20.54.177.205 ip4:49.12.39.70 -all
ipv4:
20.101.192.132
ipv4:
20.101.192.146
ipv4:
20.50.129.173
ipv4:
20.103.134.61
ipv4:
20.103.87.180
ipv4:
20.103.83.233
ipv4:
185.108.112.76
ipv4:
20.76.46.41
ipv4:
20.54.177.205
ipv4:
49.12.39.70
include:spf.sendinblue.com
v=spf1 ip4:185.41.28.0/22 ip4:94.143.16.0/21 ip4:185.24.144.0/22 ip4:153.92.224.0/19 ip4:213.32.128.0/18 ip4:185.107.232.0/22 ip4:77.32.128.0/18 ip4:77.32.192.0/19 ip4:212.146.192.0/18 ip4:172.246.0.0/18 -all
ipv4:
185.41.28.0/22
ipv4:
94.143.16.0/21
ipv4:
185.24.144.0/22
ipv4:
153.92.224.0/19
ipv4:
213.32.128.0/18
ipv4:
185.107.232.0/22
ipv4:
77.32.128.0/18
ipv4:
77.32.192.0/19
ipv4:
212.146.192.0/18
ipv4:
172.246.0.0/18

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:

51.140.185.151

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