SPF Check:
baussenwein.net

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

The SPF record analysis was performed on 29.03.2024 at 13:28:59 clock.

Lookup for the domain:
baussenwein.net
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 baussenwein.net 

Nameserverset:
root-dns.netcup.net
second-dns.netcup.net
third-dns.netcup.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
91.204.46.93 netcup GmbH blacklist 
2a03:4000:0:3e8:4e5:57ff:fe39:1e09 netcup GmbH blacklist 
91.204.46.93 netcup GmbH blacklist 
91.204.46.91 netcup GmbH blacklist 
2a03:4000:30:9758:0:0:13:9252 netcup GmbH blacklist 
46.38.249.0/25
netcup GmbH blacklist 
188.68.47.0/24
netcup GmbH blacklist 
94.16.123.254 netcup GmbH blacklist 
194.59.204.53 netcup GmbH blacklist 
185.244.192.112 netcup GmbH blacklist 
185.244.192.111 netcup GmbH blacklist 
185.244.194.184 netcup GmbH blacklist 
188.68.63.160/28
netcup GmbH blacklist 
46.38.247.112/28
netcup GmbH blacklist 
188.68.61.96/27
netcup GmbH blacklist 
188.68.63.96/27
netcup GmbH blacklist 
194.59.204.23 netcup GmbH blacklist 
194.59.206.189 netcup GmbH blacklist 
194.59.207.99 netcup GmbH blacklist 
185.244.195.67 netcup GmbH blacklist 
94.16.17.240/28
ANEXIA Internetdienstleistungs GmbH blacklist 
2a03:4000:0:200::/56
netcup GmbH blacklist 
2a03:4000:27:578:e81d:28ff:fe2a:e4b9 netcup GmbH blacklist 
2a03:4000:34:4d4:e449:7ff:fee3:c48d netcup GmbH blacklist 
2a03:4000:21:611:1479:86ff:fe4e:c332 netcup GmbH blacklist 
2a03:4001:0:200::160 netcup GmbH blacklist 
2a03:4001:0:200::164 netcup GmbH blacklist 
2a03:4001:0:200::168 netcup GmbH blacklist 
2a03:4001:0:200::172 netcup GmbH blacklist 
2a03:4001:0:109:94ab:73ff:fe56:b085 netcup GmbH blacklist 
2a03:4001:0:108:a80e:45ff:fe08:52bc netcup GmbH blacklist 
2a03:4000:3c::/48
netcup GmbH blacklist 
2a00:11c0:82:1117::/64
ANEXIA Internetdienstleistungs GmbH blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: baussenwein.net

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

91.204.46.91
2a03:4000:30:9758:0:0:13:9252

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

mx2e5d.netcup.net
mx2e5d.netcup.net
mail.baussenwein.net

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf.webhosting.systems
v=spf1 include:_spf_v4.webhosting.systems include:_spf_v6.webhosting.systems ~all
include:_spf_v4.webhosting.systems
v=spf1 ip4:46.38.249.0/25 ip4:188.68.47.0/24 ip4:94.16.123.254 ip4:194.59.204.53 ip4:185.244.192.112 ip4:185.244.192.111 ip4:185.244.194.184 ip4:188.68.63.160/28 ip4:46.38.247.112/28 ip4:188.68.61.96/27 ip4:188.68.63.96/27 ip4:194.59.204.23 ip4:194.59.206.189 ip4:194.59.207.99 ip4:185.244.195.67 ip4:94.16.17.240/28 ~all
ipv4:
46.38.249.0/25
ipv4:
188.68.47.0/24
ipv4:
94.16.123.254
ipv4:
194.59.204.53
ipv4:
185.244.192.112
ipv4:
185.244.192.111
ipv4:
185.244.194.184
ipv4:
188.68.63.160/28
ipv4:
46.38.247.112/28
ipv4:
188.68.61.96/27
ipv4:
188.68.63.96/27
ipv4:
194.59.204.23
ipv4:
194.59.206.189
ipv4:
194.59.207.99
ipv4:
185.244.195.67
ipv4:
94.16.17.240/28
include:_spf_v6.webhosting.systems
v=spf1 ip6:2a03:4000:0:200::/56 ip6:2a03:4000:27:578:e81d:28ff:fe2a:e4b9 ip6:2a03:4000:34:4d4:e449:7ff:fee3:c48d ip6:2a03:4000:21:611:1479:86ff:fe4e:c332 ip6:2a03:4001:0:200::160 ip6:2a03:4001:0:200::164 ip6:2a03:4001:0:200::168 ip6:2a03:4001:0:200::172 ip6:2a03:4001:0:109:94ab:73ff:fe56:b085 ip6:2a03:4001:0:108:a80e:45ff:fe08:52bc ip6:2a03:4000:3c::/48 ip6:2a00:11c0:82:1117::/64 ~all
ipv6:
2a03:4000:0:200::/56
ipv6:
2a03:4000:27:578:e81d:28ff:fe2a:e4b9
ipv6:
2a03:4000:34:4d4:e449:7ff:fee3:c48d
ipv6:
2a03:4000:21:611:1479:86ff:fe4e:c332
ipv6:
2a03:4001:0:200::160
ipv6:
2a03:4001:0:200::164
ipv6:
2a03:4001:0:200::168
ipv6:
2a03:4001:0:200::172
ipv6:
2a03:4001:0:109:94ab:73ff:fe56:b085
ipv6:
2a03:4001:0:108:a80e:45ff:fe08:52bc
ipv6:
2a03:4000:3c::/48
ipv6:
2a00:11c0:82:1117::/64

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

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

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:

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