SPF Check:
matthiasgassner.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 matthiasgassner.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 matthiasgassner.de.
The SPF record for matthiasgassner.de is valid.
The syntax check of the SPF record shows no obvious errors.

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

The SPF record analysis was performed on 14.11.2024 at 16:17:14 clock.

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

Nameserverset:
second-dns.netcup.net
root-dns.netcup.net
third-dns.netcup.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
202.61.232.217 netcup GmbH blacklist 
2a03:4000:61:564d:0:0:18:9384 netcup GmbH blacklist 
202.61.232.219 netcup GmbH blacklist 
2a03:4000:0:3ea:8871:55ff:fe3d:bdaa netcup GmbH blacklist 
202.61.232.219 netcup GmbH blacklist 
46.38.225.138 netcup GmbH blacklist 
2a03:4000:0:1:0:0:0:e18a netcup GmbH blacklist 
202.61.232.217 netcup GmbH blacklist 
2a03:4000:61:564d:0:0:18:9384 netcup GmbH blacklist 
188.68.53.67 netcup GmbH blacklist 
202.61.232.217 netcup GmbH blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: matthiasgassner.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

202.61.232.217
2a03:4000:61:564d:0:0:18:9384

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

46.38.225.138
2a03:4000:0:1:0:0:0:e18a
202.61.232.217
2a03:4000:61:564d:0:0:18:9384

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

mxe8db.netcup.net
mxe8db.netcup.net
mail.matthiasgassner.de

Additionally authorized IPv4 addresses

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

188.68.53.67
202.61.232.217

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

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:

ae8d9.netcup.net

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