SPF Check:
thomasthomas.de

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 failed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 1 Error
  •   Email Spoofing Protection: Poor
Warning: Compliance breach for email deliverability & security

The domain thomasthomas.de does not fulfil the requirements for optimal deliverability to Google, Yahoo and other email service providers.

Mandatory IT baseline protection measures for email security are not fulfilled. There are risks of email misuse.

Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain thomasthomas.de.
The SPF record for thomasthomas.de is not valid.
The syntax check resulted in a total of 1 errors.
of the email -Spoofing protection for this domain is not or not sufficiently provided.

Which IP-s are legitimate to send emails?
In total, 15 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 22.11.2024 at 00:02:58 clock.

Lookup for the domain:
thomasthomas.de
IP address to be checked:
no IP address specified

Have secure SPF record created by expert
from 749€

Order SPF record
  • 1. You send an email to our analysis system
  • 2. We will send you the finished SPF record
  • 3. You implement the SPF record
  • 4. We check the setup final
Have secure SPF record created by expert
from 749€

Evaluation for the domain thomasthomas.de 

Nameserverset:
ns1031.ui-dns.org
ns1031.ui-dns.com
ns1031.ui-dns.biz
ns1031.ui-dns.de
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
217.160.0.100 IONOS SE blacklist 
212.227.17.10 IONOS SE blacklist 
212.227.126.134 IONOS SE blacklist 
212.227.126.133 IONOS SE blacklist 
212.227.126.187 IONOS SE blacklist 
212.227.17.13 IONOS SE blacklist 
217.72.192.75 IONOS SE blacklist 
212.227.17.24 IONOS SE blacklist 
212.227.126.135 IONOS SE blacklist 
212.227.126.130 IONOS SE blacklist 
217.72.192.74 IONOS SE blacklist 
217.72.192.73 IONOS SE blacklist 
212.227.126.131 IONOS SE blacklist 
217.72.192.67 IONOS SE blacklist 
212.227.15.41 IONOS SE blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: thomasthomas.de

SPF record available?

We found an SPF record for the domain.

v=spf1

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

217.160.0.100

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

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 MX records

We could not find any other records authorized in the SPF record besides the MX records stored in the DNS

Additionally authorized IPv4 addresses

No explicit IPv4 addresses in the SPF record have been authorised to send

Additionally authorized IPv6 addresses

No explicit IPv6 addresses in the SPF record have been authorised to send

Additional external SPF records

We could not find any other records authorized in SPF-Record

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:

217-160-0-100.elastic-ssl.ui-r.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