How privacy works

Private lookups are not added to public searches, stored reports or change history. This does not remove a report that was already public. Your choice lasts for this browser session.

Who hosts dampf.com?

Answer

www.dampf.com is hosted by STRATO.

Likely🇩🇪 GermanyIPv6

Checked 1 hour ago from Cloudflare ZRH in 907 ms. This is a saved result.

Your next steps

What needs attention

Prioritized observations from this check. Review changes with whoever manages the website.

  1. Review

    SPF protection is not confirmed

    This policy redirects to another SPF record, which this lookup has not evaluated.

    Next step: Validate the complete SPF policy with the mail provider; review the final all mechanism or redirected policy.

  2. Improve

    Review browser security headers

    Strict-Transport-Security, Content-Security-Policy, Clickjacking protection, X-Content-Type-Options, Referrer-Policy, Permissions-Policy did not meet the conservative header checks. This is not a complete security audit.

    Next step: Review these headers with the site developer and test policy changes before enforcing them.

Evidence by layer

The company operating a network and the company selling the hosting can be different.

Hosting company
STRATOInferred

Network operators

STRATO

Network ownership alone does not confirm the retail hosting provider.

How we know

  • 81.169.145.64 belongs to AS6724 (STRATO), reverse DNS w00.rzone.de
  • 2a01:238:20a:202:1064:: belongs to AS6724 (STRATO), reverse DNS w00.rzone.de

Servers

The addresses the name points to and the networks that own them.

www.dampf.com (where the site redirects)

www.dampf.com→dampf.com

  • 81.169.145.64STRATONetwork AS6724🇩🇪 Registered in Germany, block 81.169.144.0/22Reverse DNS w00.rzone.de
  • 2a01:238:20a:202:1064::STRATONetwork AS6724🇩🇪 Registered in Germany, block 2a01:238:20a::/48Reverse DNS w00.rzone.de

dampf.com (the address you entered)

  • 81.169.145.64STRATONetwork AS6724🇩🇪 Registered in Germany, block 81.169.144.0/22Reverse DNS w00.rzone.de
  • 2a01:238:20a:202:1064::STRATONetwork AS6724🇩🇪 Registered in Germany, block 2a01:238:20a::/48Reverse DNS w00.rzone.de

Reachable over IPv6.

Website

What the site answered when we visited its home page.

Status
200 OK
Address
https://www.dampf.com/unternehmen/
Page title
Dampferzeuger in bester Qualität und mit optimalem Service
HTTPS
Yes
HTTP/3
Not advertised
Response time
139 ms from Cloudflare ZRH
Powered by
PHP/8.4.27

Redirects (1)

  1. 302https://dampf.com/
  2. 200https://www.dampf.com/unternehmen/

Security headers

F
  • Strict-Transport-Security
  • Content-Security-Policy
  • Clickjacking protection
  • X-Content-Type-Options
  • Referrer-Policy
  • Permissions-Policy

Built with

CMSWordPress
Page builderElementorDivi
JavaScriptjQueryBootstrap
LanguagePHP 8.4.27
Tag managerGoogle Tag Manager
FontsFont Awesome

DNS

Who answers for the domain name, and its records.

DNS provider
STRATO
Name servers
docks08.rzone.de
shades09.rzone.de
Zone
dampf.com
DNSSEC
Not signed
Certificates
Any certificate authority (no CAA record)
All DNS records (7)
TypeNameValueTTL
Adampf.com81.169.145.64150
AAAAdampf.com2a01:238:20a:202:1064::150
NSdampf.comshades09.rzone.de150
NSdampf.comdocks08.rzone.de150
MXdampf.com5 smtpin.rzone.de150
TXTdampf.comgoogle-site-verification=xoHmZ3XAaMMXZ3oiU41rMuU1eQgwt7fv-Y1DarKAm-U150
TXTdampf.comv=spf1 redirect=_spf.strato.com150

Email

Easy to spoof: SPF or DMARC is missing.

Mailbox provider
STRATO
Mail servers
5 smtpin.rzone.de
Allowed senders
Only servers listed in the SPF record
SPF
Present
DMARC
Spoofed mail is rejected.
MTA-STS
Not enabled
SPF and DMARC records

v=spf1 redirect=_spf.strato.com

v=DMARC1;p=reject;

Domain registration

Registrar
Cronon GmbH
Registered
13 May 1998 (28 years ago)
Paid until
12 May 2027 (in 181 days)
Last changed
13 May 2026
Status
Active
DNSSEC at registry
No
Source
rdap.verisign.com

Connected services

Verification records in DNS show the domain is linked to these accounts.

Google Search Console

Observed changes

A compact record of what changed between public checks. Rechecks happen only when someone requests them.

History starts with saved public observations. No earlier changes are inferred.