stiebel-eltron.de

Checked 22 October 2026, 00:31 UTC · via 8.8.8.8
✗Problems found
21 passed 3 warnings 1 failed 4 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
ICANN policies apply
no

Checks

  • i
    .de is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .de is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

info

dns.wn-dns.de, ns1.waaf.net, ns2.waaf.net, ns3.waaf.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns.wn-dns.de, ns1.waaf.net, ns2.waaf.net, ns3.waaf.net
NS in the zone
dns.wn-dns.de, ns1.waaf.net, ns2.waaf.net, ns3.waaf.net
NameserverAddressesNetwork (AS)Glue
dns.wn-dns.de46.101.245.225 2a03:b0c0:3:d0::28:b001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US46.101.245.225 2a03:b0c0:3:d0::28:b001
ns1.waaf.net35.156.243.225AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns2.waaf.net54.36.113.70 2001:41d0:701:1000::b99AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns3.waaf.net188.166.73.66AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to dns.wn-dns.de, ns1.waaf.net, ns2.waaf.net, ns3.waaf.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 3 addresses; AS16276 (OVH - OVH SAS, FR): 2 addresses; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.waaf.net, ns3.waaf.net.
    #13

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns.wn-dns.de 46.101.245.225NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
dns.wn-dns.de 2a03:b0c0:3:d0::28:b001NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns1.waaf.net 35.156.243.225NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns2.waaf.net 54.36.113.70NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns2.waaf.net 2001:41d0:701:1000::b99NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns3.waaf.net 188.166.73.66NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3

Checks

  • ✓ All respond #14
    All 6 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns.wn-dns.de: "PowerDNS Authoritative Server 4.7.3"; ns1.waaf.net: "PowerDNS Authoritative Server 4.7.3"; ns2.waaf.net: "PowerDNS Authoritative Server 4.7.3"; ns3.waaf.net: "PowerDNS Authoritative Server 4.7.3". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

fail

serial 2026092801 · primary ns1.waaf.net

Found

Primary (MNAME)
ns1.waaf.net
Contact (RNAME)
hostmaster\@ns1.waaf.net
Serial
2026092801
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns.wn-dns.de (46.101.245.225)2026092801
dns.wn-dns.de (2a03:b0c0:3:d0::28:b001)2026092801
ns1.waaf.net (35.156.243.225)2026092801
ns2.waaf.net (54.36.113.70)2026092801
ns2.waaf.net (2001:41d0:701:1000::b99)2026092801
ns3.waaf.net (188.166.73.66)2026092801

Checks

  • ✓ Serial 2026092801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.waaf.net is one of the listed nameservers.
  • ✗
    Invalid contact address
    The SOA RNAME "hostmaster\\@ns1.waaf.net" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • ✓ Date-based serial #26
    The serial 2026092801 follows the YYYYMMDDnn convention (2026-09-28).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

16 records at the apex

Found

Read from
46.101.245.225:53
TypeValueTTL
SOAns1.waaf.net. hostmaster\@ns1.waaf.net. 2026092801 10800 3600 604800 36003600
NSns2.waaf.net.3600
NSdns.wn-dns.de.3600
NSns3.waaf.net.3600
NSns1.waaf.net.3600
A217.13.71.160
AAAA2a00:1030:1008:44::d90d:470160
MX10 stiebeleltron-de01i.mail.protection.outlook.com.3600
TXT"+4roW2cJqYDKYrebj8weAzdB8EauY/t1xZpUCupdfbF5Vd+PzGjV7hl/dDtXaoMxL3ZKTXIb7vvcGooxodUBrQ=="3600
TXT"_8qjiu3z7bj1x6xw5k0haiexgfiy6tta"3600
TXT"google-site-verification=uiPzhQFgXQKMklfl284pem-A0CLUo8om_aif41Bzrkw"3600
TXT"_ir9lpqm47bdzcnkdji75ask8vh2ayon"3600
TXT"Sendinblue-code:273e64583503db9a1b04622d240ef2f1"3600
TXT"miro-verification=8b520578a216deb4e2f54cafadbbff735a9f692b"3600
TXT"MS=ms98375628"3600
TXT"v=spf1 mx include:spf.stiebel-eltron.com include:spf.protection.outlook.com ~all"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35