hannover-stadt.de

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

ns.htp-tel.de, ns01.hannover-stadt.de, ns02.hannover-stadt.de, ns1.htp-tel.de, ns2.htp-tel.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.htp-tel.de, ns01.hannover-stadt.de, ns02.hannover-stadt.de, ns1.htp-tel.de, ns2.htp-tel.de
NS in the zone
ns.htp-tel.de, ns01.hannover-stadt.de, ns02.hannover-stadt.de, ns1.htp-tel.de, ns2.htp-tel.de
NameserverAddressesNetwork (AS)Glue
ns.htp-tel.de81.14.244.10 2a02:560:2:140::10AS13045 HTP-AS - htp GmbH, DE AS13045 HTP-AS - htp GmbH, DE81.14.244.10 2a02:560:2:140::10
ns01.hannover-stadt.de212.59.55.202AS13045 HTP-AS - htp GmbH, DE212.59.55.202
ns02.hannover-stadt.de212.59.55.203AS13045 HTP-AS - htp GmbH, DE212.59.55.203
ns1.htp-tel.de81.14.243.10 2a02:560:2:100::10AS13045 HTP-AS - htp GmbH, DE AS13045 HTP-AS - htp GmbH, DE81.14.243.10 2a02:560:2:100::10
ns2.htp-tel.de212.59.54.188 2a02:560:2:180::10AS13045 HTP-AS - htp GmbH, DE AS13045 HTP-AS - htp GmbH, DE212.59.54.188 2a02:560:2:180::10

Checks

  • ✓ 5 nameservers #6
    Delegated to ns.htp-tel.de, ns01.hannover-stadt.de, ns02.hannover-stadt.de, ns1.htp-tel.de, ns2.htp-tel.de.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns01.hannover-stadt.de, ns02.hannover-stadt.de.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 2a02:560:2::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13045 (HTP-AS - htp GmbH, DE): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns01.hannover-stadt.de, ns02.hannover-stadt.de.
    #13

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.htp-tel.de 81.14.244.10NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns.htp-tel.de 2a02:560:2:140::10NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns01.hannover-stadt.de 212.59.55.202NOERROR, 10 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu
ns02.hannover-stadt.de 212.59.55.203NOERROR, 10 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.04.8-Ubuntu
ns1.htp-tel.de 81.14.243.10NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns1.htp-tel.de 2a02:560:2:100::10NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.htp-tel.de 212.59.54.188NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.htp-tel.de 2a02:560:2:180::10NOERROR, 10 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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: ns01.hannover-stadt.de: "9.18.39-0ubuntu0.22.04.7-Ubuntu"; ns02.hannover-stadt.de: "9.18.39-0ubuntu0.24.04.8-Ubuntu". 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

pass

serial 2010112610 · primary ns01.hannover-stadt.de

Found

Primary (MNAME)
ns01.hannover-stadt.de
Contact (RNAME)
hostmaster.hannover-stadt.de
Serial
2010112610
Refresh / retry
10800 s / 1800 s
Expire
2592000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns.htp-tel.de (81.14.244.10)2010112610
ns.htp-tel.de (2a02:560:2:140::10)2010112610
ns01.hannover-stadt.de (212.59.55.202)2010112610
ns02.hannover-stadt.de (212.59.55.203)2010112610
ns1.htp-tel.de (81.14.243.10)2010112610
ns1.htp-tel.de (2a02:560:2:100::10)2010112610
ns2.htp-tel.de (212.59.54.188)2010112610
ns2.htp-tel.de (2a02:560:2:180::10)2010112610

Checks

  • ✓ Serial 2010112610 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 30d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.hannover-stadt.de is one of the listed nameservers.
  • ✓ Contact hostmaster@hannover-stadt.de #25
    The SOA RNAME hostmaster.hannover-stadt.de means hostmaster@hannover-stadt.de.
  • ✓ Date-based serial #26
    The serial 2010112610 follows the YYYYMMDDnn convention (2010-11-26).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
8 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
1612RSASHA256 (8)SHA256 67BDE463C3FE1E58…yes

DNSKEY in the zone

Key tagRoleAlgorithm
32985ZSK (256)RSASHA256 (8)
1612KSK (257)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 1612 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-08 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-08 04:15 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

18 records at the apex

Found

Read from
81.14.244.10:53
TypeValueTTL
SOAns01.hannover-stadt.de. hostmaster.hannover-stadt.de. 2010112610 10800 1800 2592000 8640086400
NSns.htp-tel.de.86400
NSns1.htp-tel.de.86400
NSns01.hannover-stadt.de.86400
NSns2.htp-tel.de.86400
NSns02.hannover-stadt.de.86400
A212.59.55.086400
MX100 dmzmailgw04.hannover-stadt.de.60
MX100 dmzmailgw03.hannover-stadt.de.60
TXT"MS=ms29313936"86400
TXT"autodesk-domain-verification=8ZV43C2eQt8LIAXCaukr"86400
TXT"MS=0A4F0FFDD599DDEBCFEF769A64475FB0B5E7ED5C"86400
TXT"adobe-idp-site-verification=c5eba24dcc86a2b95db51cc8c18462304ebd7fedee129e5048fc271b37ea5c28"86400
TXT"apple-domain-verification=lLoKLqdIxsGPRyc6"86400
TXT"v=spf1 mx ip4:192.109.36.75 ip4:192.109.36.76 ip4:192.109.36.85 ip4:192.109.36.86 ip4:212.59.55.87 include:spf.mxg.cloud include:ekom21.de -all"86400
TXT"c9r83m8n3b1knlhrb5vwcvdxkq3rrqfn"86400
TXT"google-site-verification=1Qp1HU9VqyD74v8_ak4d6qSsy_CwBGyD5V427ZiJ-UE"86400
TXT"cisco-ci-domain-verification=2cca390de45cc48b1325b11bdec6c6fc34df35ab1a7e1d04efbb575a5826c07f"86400

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change.
    #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