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

Your overall domain security

SPF is only one of 11 security factors. Your domain still has critical gaps.

Email authentication
SPF DKIM ? DMARC ?
Email transport
TLS ? MTA-STS ? TLSRPT ? DANE ?
Reputation
DNSBL ? BIMI ?
Certificate control
DNSSEC ? CAA ?
Warning: Compliance breach for email deliverability & security

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

The SPF record analysis was performed on 17.04.2026 at 11:56:52 clock.

Lookup for the domain:
immowien.de
IP address to be checked:
no IP address specified
Find out now: The BSI's Email Security Year 2025
This way, you'll be well prepared and can now strengthen your email security in a targeted manner.
Find out now: The BSI's Email Security Year 2025

Evaluation for the domain immowien.de 

Nameserverset:
ns5.kasserver.com
ns6.kasserver.com
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
85.13.162.49 Neue Medien Muennich GmbH blacklist 
148.251.12.246 Hetzner Online GmbH blacklist 
85.214.159.148 Strato GmbH blacklist 
202.61.203.42 netcup GmbH blacklist 
148.251.12.246 Hetzner Online GmbH blacklist 
85.214.92.64 Strato GmbH blacklist 
85.214.243.184 Strato GmbH blacklist 
85.214.198.168 Strato GmbH blacklist 
85.214.112.184 Strato GmbH blacklist 
85.215.90.1 Strato GmbH blacklist 
88.99.208.77 Hetzner Online GmbH blacklist 
2a03:4000:5a:a8:98a9:96ff:fed6:5d7b netcup GmbH blacklist 
2a01:238:4299:1e00:991e:dfa2:f0c4:f838 Strato GmbH blacklist 
2a01:238:43d2:6600:279a:6a62:a8a9:e0ce Strato GmbH blacklist 
2a01:238:420c:900:cece:90b6:94a7:1cd0 Strato GmbH blacklist 
2a01:0238:438f:1400:99dc:f331:6e21:6ffd Strato GmbH blacklist 
40.92.0.0/15
Microsoft Corporation blacklist 
40.107.0.0/16
Microsoft Corporation blacklist 
52.100.0.0/15
Microsoft Corporation blacklist 
52.102.0.0/16
Microsoft Corporation blacklist 
52.103.0.0/17
Microsoft Corporation blacklist 
104.47.0.0/17
Microsoft Corporation blacklist 
2a01:111:f400::/48
Microsoft Corporation blacklist 
2a01:111:f403::/49
Microsoft Corporation blacklist 
2a01:111:f403:8000::/51
Microsoft Corporation blacklist 
2a01:111:f403:c000::/51
Microsoft Corporation blacklist 
2a01:111:f403:f000::/52
Microsoft Corporation blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: immowien.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

85.13.162.49

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

mailin.witera.de

Additional external SPF records

We could find other records authorized in the SPF record

include:spfall.tcinet.de
v=spf1 include:spfv4.tcinet.de include:spfv6.tcinet.de -all
include:spfv4.tcinet.de
v=spf1 ip4:85.214.159.148 ip4:202.61.203.42 ip4:148.251.12.246 ip4:85.214.92.64 ip4:85.214.243.184 ip4:85.214.198.168 ip4:85.214.112.184 ip4:85.215.90.1 ip4:88.99.208.77 -all
ipv4:
85.214.159.148
ipv4:
202.61.203.42
ipv4:
148.251.12.246
ipv4:
85.214.92.64
ipv4:
85.214.243.184
ipv4:
85.214.198.168
ipv4:
85.214.112.184
ipv4:
85.215.90.1
ipv4:
88.99.208.77
include:spfv6.tcinet.de
v=spf1 ip6:2a03:4000:5a:a8:98a9:96ff:fed6:5d7b ip6:2a01:238:4299:1e00:991e:dfa2:f0c4:f838 ip6:2a01:238:43d2:6600:279a:6a62:a8a9:e0ce ip6:2a01:238:420c:900:cece:90b6:94a7:1cd0 ip6:2a01:0238:438f:1400:99dc:f331:6e21:6ffd -all
ipv6:
2a03:4000:5a:a8:98a9:96ff:fed6:5d7b
ipv6:
2a01:238:4299:1e00:991e:dfa2:f0c4:f838
ipv6:
2a01:238:43d2:6600:279a:6a62:a8a9:e0ce
ipv6:
2a01:238:420c:900:cece:90b6:94a7:1cd0
ipv6:
2a01:0238:438f:1400:99dc:f331:6e21:6ffd
include:spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all
ipv4:
40.92.0.0/15
ipv4:
40.107.0.0/16
ipv4:
52.100.0.0/15
ipv4:
52.102.0.0/16
ipv4:
52.103.0.0/17
ipv4:
104.47.0.0/17
ipv6:
2a01:111:f400::/48
ipv6:
2a01:111:f403::/49
ipv6:
2a01:111:f403:8000::/51
ipv6:
2a01:111:f403:c000::/51
ipv6:
2a01:111:f403:f000::/52

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

dd19820.kasserver.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.
© 2026 nicmanager.com.   All rights reserved.
nicmanager