hz.de

Checked 21 October 2026, 22:51 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 0 failed 5 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

warn

ns1.local-host.de, ns2.local-host.de, ns3.local-host.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.local-host.de, ns2.local-host.de, ns3.local-host.de
NS in the zone
ns1.local-host.de, ns2.local-host.de, ns3.local-host.de
NameserverAddressesNetwork (AS)Glue
ns1.local-host.de94.16.117.181AS197540 netcup-AS - netcup GmbH, DE94.16.117.181
ns2.local-host.de168.119.103.121AS24940 HETZNER-AS - Hetzner Online GmbH, DE168.119.103.121
ns3.local-host.de152.53.3.247AS197540 netcup-AS - netcup GmbH, DE152.53.3.247

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.local-host.de, ns2.local-host.de, ns3.local-host.de.
  • ✓ 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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS197540 (netcup-AS - netcup GmbH, DE): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address.
  • i
    All nameserver names under .de
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.local-host.de 94.16.117.181NOERROR, 1 ms, authoritativenoyes / yesrefused-
ns2.local-host.de 168.119.103.121NOERROR, 6 ms, authoritativenoyes / yesrefused-
ns3.local-host.de 152.53.3.247NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

pass

serial 2026101914 · primary ns1.local-host.de

Found

Primary (MNAME)
ns1.local-host.de
Contact (RNAME)
hostmaster.local-host.de
Serial
2026101914
Refresh / retry
43200 s / 7200 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.local-host.de (94.16.117.181)2026101914
ns2.local-host.de (168.119.103.121)2026101914
ns3.local-host.de (152.53.3.247)2026101914

Checks

  • ✓ Serial 2026101914 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 28d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.local-host.de is one of the listed nameservers.
  • ✓ Contact hostmaster@local-host.de #25
    The SOA RNAME hostmaster.local-host.de means hostmaster@local-host.de.
  • ✓ Date-based serial #26
    The serial 2026101914 follows the YYYYMMDDnn convention (2026-10-19).

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
94.16.117.181:53
TypeValueTTL
SOAns1.local-host.de. hostmaster.local-host.de. 2026101914 43200 7200 2419200 36003600
NSns1.local-host.de.10800
NSns2.local-host.de.10800
NSns3.local-host.de.10800
A3.124.189.64180
MX0 hz-de.mail.protection.outlook.com.3600
TXT"743bd83054f7bd62273e1548f760f9"21600
TXT"brevo-code:8abd1931441752adc8ab7d5708cb986f"3600
TXT"google-site-verification=XCNtFSRNsu4pDjYhT_P67Cr452JRDYCsAEeG4ZeWiPs"3600
TXT"v=spf1 mx ip4:46.245.182.42 ip4:194.195.3.64 ip4:80.149.146.212 include:spf.nl2go.com include:amazonses.com include:spf.protection.outlook.com include:_spf_eucentral1.prod.hydra.sophos.com -all"3600
TXT"atlassian-domain-verification=qtZnpHM33ADdD/KQV69OtudQl2NizLbmySdy2cXRPKMGnGHE95nINp7mdcPrRKnn"86400
TXT"sophos-domain-verification=ef7208152a5bca62f1d65b53c0dff0c359fd884b "600
TXT"MS=ms57843926"3600
TXT"facebook-domain-verification=di2rgjd3q9dx0hzc432eep8wtvsaiw"3600
TXT"sophos-domain-verification=833f3d24b27d9d0df7110e358943d183f28871ced2e7a71a4a28a677d802a629"3600
TXT"iqO9G91yb1ivnY3yxUF8j+tdxaMXtU75p0Wu4ancr92aBY/DNDljNIoaEmsQW5w7WB+EaoxzMxrCliLtARC12A=="3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (3m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 3h; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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