SPF Check:
henkesasswolf.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 passed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 0 errors
  •   Email Anti-Spoofing: Good
Warning: Compliance breach for email deliverability & security

The domain henkesasswolf.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 henkesasswolf.de.
The SPF record for henkesasswolf.de 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, 43 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 15.06.2024 at 18:22:00 clock.

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

Nameserverset:
ns3.stratoserver.net
ns4.stratoserver.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
138.201.205.25 Hetzner Online GmbH blacklist 
62.225.74.194 Deutsche Telekom AG blacklist 
212.184.104.140 Deutsche Telekom AG blacklist 
62.153.215.148 Deutsche Telekom AG blacklist 
62.153.215.148 Deutsche Telekom AG blacklist 
212.184.104.137 Deutsche Telekom AG blacklist 
212.184.104.138 Deutsche Telekom AG blacklist 
212.184.104.139 Deutsche Telekom AG blacklist 
212.184.104.140 Deutsche Telekom AG blacklist 
212.184.104.141 Deutsche Telekom AG blacklist 
212.184.104.142 Deutsche Telekom AG blacklist 
62.225.74.193 Deutsche Telekom AG blacklist 
62.225.74.194 Deutsche Telekom AG blacklist 
62.225.74.195 Deutsche Telekom AG blacklist 
62.225.74.196 Deutsche Telekom AG blacklist 
62.225.74.197 Deutsche Telekom AG blacklist 
62.225.74.198 Deutsche Telekom AG blacklist 
66.189.121.201 CHARTER-20115 blacklist 
66.189.121.202 CHARTER-20115 blacklist 
66.189.121.203 CHARTER-20115 blacklist 
66.189.121.204 CHARTER-20115 blacklist 
66.189.121.205 CHARTER-20115 blacklist 
66.189.121.206 CHARTER-20115 blacklist 
46.243.95.179 dogado GmbH blacklist 
46.243.95.180 dogado GmbH blacklist 
128.127.70.0/26
dogado GmbH blacklist 
89.22.108.0/24
dogado GmbH blacklist 
192.162.87.0/24
dogado GmbH blacklist 
109.237.142.0/24
dogado GmbH blacklist 
2a02:a60:0:5::/64
dogado GmbH blacklist 
46.243.88.174 dogado GmbH blacklist 
46.243.88.175 dogado GmbH blacklist 
46.243.88.176 dogado GmbH blacklist 
46.243.88.177 dogado GmbH blacklist 
37.218.248.47 dogado GmbH blacklist 
185.80.95.31 dogado GmbH blacklist 
37.218.249.47 dogado GmbH blacklist 
37.218.251.62 dogado GmbH blacklist 
185.80.93.227 dogado GmbH blacklist 
185.80.93.204 dogado GmbH blacklist 
194.175.186.25 UUNET blacklist 
194.175.186.26 UUNET blacklist 
194.15.61.25 Deutsche Telekom AG blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: henkesasswolf.de

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

138.201.205.25

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

mail.henkesasswolf.de
ssp.henkesasswolf.de
mail3.henkesasswolf.de

Additionally authorized IPv4 addresses

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

62.153.215.148
212.184.104.137
212.184.104.138
212.184.104.139
212.184.104.140
212.184.104.141
212.184.104.142
62.225.74.193
62.225.74.194
62.225.74.195
62.225.74.196
62.225.74.197
62.225.74.198
66.189.121.201
66.189.121.202
66.189.121.203
66.189.121.204
66.189.121.205
66.189.121.206

Additional external SPF records

We could find other records authorized in the SPF record

include:secure-mailgate.com
v=spf1 ip4:46.243.95.179 ip4:46.243.95.180 ip4:128.127.70.0/26 ip4:89.22.108.0/24 ip4:192.162.87.0/24 ip4:109.237.142.0/24 ip6:2a02:a60:0:5::/64 ip4:46.243.88.174 ip4:46.243.88.175 ip4:46.243.88.176 ip4:46.243.88.177 a:mailcloud.dogado.de -all
ipv4:
46.243.95.179
ipv4:
46.243.95.180
ipv4:
128.127.70.0/26
ipv4:
89.22.108.0/24
ipv4:
192.162.87.0/24
ipv4:
109.237.142.0/24
ipv4:
46.243.88.174
ipv4:
46.243.88.175
ipv4:
46.243.88.176
ipv4:
46.243.88.177
ipv6:
2a02:a60:0:5::/64
include:_spf.senders.dc.aeb.com
v=spf1 ip4:194.175.186.25 ip4:194.175.186.26 ip4:194.15.61.25 -all
ipv4:
194.175.186.25
ipv4:
194.175.186.26
ipv4:
194.15.61.25

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

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