SPF Check:
eimermacher.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: 2 Error
  •   Email Spoofing Protection: Poor
Summary of the SPF check

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

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, 38 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 28.11.2024 at 17:51:03 clock.

Lookup for the domain:
eimermacher.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 eimermacher.de 

Nameserverset:
dns.dns4.de
dns.dns1.de
dns.dns2.de
dns.dns3.de
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
18.185.115.147 AMAZON-02 blacklist 
18.185.115.146 AMAZON-02 blacklist 
18.185.115.145 AMAZON-02 blacklist 
156.67.184.114 Deutsche Glasfaser Wholesale GmbH blacklist 
156.67.184.114 Deutsche Glasfaser Wholesale GmbH blacklist 
217.91.63.141 Deutsche Telekom AG blacklist 
217.5.224.122 Deutsche Telekom AG blacklist 
18.208.22.64/26
AMAZON-AES blacklist 
18.208.22.128/25
AMAZON-AES blacklist 
18.185.115.128/26
AMAZON-02 blacklist 
18.185.115.0/25
AMAZON-02 blacklist 
13.238.202.0/25
AMAZON-02 blacklist 
13.238.202.128/26
AMAZON-02 blacklist 
18.176.203.128/25
AMAZON-02 blacklist 
13.213.174.128/25
AMAZON-02 blacklist 
18.177.156.0/25
AMAZON-02 blacklist 
13.213.220.0/25
AMAZON-02 blacklist 
107.22.223.18 AMAZON-AES blacklist 
52.70.252.86 AMAZON-AES blacklist 
35.156.245.132 AMAZON-02 blacklist 
18.156.0.20 AMAZON-02 blacklist 
3.72.196.143 AMAZON-02 blacklist 
54.146.4.63 AMAZON-AES blacklist 
54.174.82.86 AMAZON-AES blacklist 
18.188.9.192/26
AMAZON-02 blacklist 
18.188.239.128/26
AMAZON-02 blacklist 
34.253.238.128/26
AMAZON-02 blacklist 
34.253.238.192/26
AMAZON-02 blacklist 
15.168.56.0/25
AMAZON-02 blacklist 
15.168.49.64/26
AMAZON-02 blacklist 
15.168.56.128/26
AMAZON-02 blacklist 
18.97.0.160/27
AMAZON-AES blacklist 
18.96.32.128/27
AMAZON-02 blacklist 
178.77.121.128/26
PlusServer GmbH blacklist 
158.69.163.48/29
OVH SAS blacklist 
46.4.238.128/29
Hetzner Online GmbH blacklist 
194.42.96.0/23
AMAZON-02 blacklist 
2607:5300:203:fe1::/112
OVH SAS blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: eimermacher.de

SPF record available?

We found an SPF record for the domain.

v=spf1

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

eimermacher.in.tmes.trendmicro.eu
eimermacher.in.tmes.trendmicro.eu
eimermacher.in.tmes.trendmicro.eu
outlook.eimermacher.de

Additionally authorized MX records

In addition to the MX records stored in the DNS, we were able to find other records authorized in the SPF record

Additionally authorized IPv4 addresses

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

156.67.184.114
217.91.63.141
217.5.224.122

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.tmes.trendmicro.com
v=spf1 ip4:18.208.22.64/26 ip4:18.208.22.128/25 ip4:18.185.115.128/26 ip4:18.185.115.0/25 ip4:13.238.202.0/25 ip4:13.238.202.128/26 ip4:18.176.203.128/25 ip4:13.213.174.128/25 ip4:18.177.156.0/25 ip4:13.213.220.0/25 include:spfb.tmes.trendmicro.com ~all
ipv4:
18.208.22.64/26
ipv4:
18.208.22.128/25
ipv4:
18.185.115.128/26
ipv4:
18.185.115.0/25
ipv4:
13.238.202.0/25
ipv4:
13.238.202.128/26
ipv4:
18.176.203.128/25
ipv4:
13.213.174.128/25
ipv4:
18.177.156.0/25
ipv4:
13.213.220.0/25
include:spfb.tmes.trendmicro.com
v=spf1 ip4:107.22.223.18 ip4:52.70.252.86 ip4:35.156.245.132 ip4:18.156.0.20 ip4:3.72.196.143 ip4:54.146.4.63 ip4:54.174.82.86 include:spfc.tmes.trendmicro.com ~all
ipv4:
107.22.223.18
ipv4:
52.70.252.86
ipv4:
35.156.245.132
ipv4:
18.156.0.20
ipv4:
3.72.196.143
ipv4:
54.146.4.63
ipv4:
54.174.82.86
include:spfc.tmes.trendmicro.com
v=spf1 ip4:18.188.9.192/26 ip4:18.188.239.128/26 ip4:34.253.238.128/26 ip4:34.253.238.192/26 ip4:15.168.56.0/25 ip4:15.168.49.64/26 ip4:15.168.56.128/26 ip4:18.97.0.160/27 ip4:18.96.32.128/27 ~all
ipv4:
18.188.9.192/26
ipv4:
18.188.239.128/26
ipv4:
34.253.238.128/26
ipv4:
34.253.238.192/26
ipv4:
15.168.56.0/25
ipv4:
15.168.49.64/26
ipv4:
15.168.56.128/26
ipv4:
18.97.0.160/27
ipv4:
18.96.32.128/27
include:spf.crsend.com
v=spf1 ip4:178.77.121.128/26 ip4:158.69.163.48/29 ip4:46.4.238.128/29 ip4:194.42.96.0/23 ip6:2607:5300:203:fe1::/112 ~all
ipv4:
178.77.121.128/26
ipv4:
158.69.163.48/29
ipv4:
46.4.238.128/29
ipv4:
194.42.96.0/23
ipv6:
2607:5300:203:fe1::/112

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.

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:

eimermacher.de

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