mhh.de

Checked 21 October 2026, 23:22 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 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

nsext1.mh-hannover.de, nsext2.mh-hannover.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
nsext1.mh-hannover.de, nsext2.mh-hannover.de
NS in the zone
nsext1.mh-hannover.de, nsext2.mh-hannover.de
NameserverAddressesNetwork (AS)Glue
nsext1.mh-hannover.de193.174.104.33AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE193.174.104.33
nsext2.mh-hannover.de193.174.104.34AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE193.174.104.34

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: nsext1.mh-hannover.de, nsext2.mh-hannover.de.
    #6
  • ✓ 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 one network
    all IPv4 addresses are in 193.174.104.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS680 (DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
nsext1.mh-hannover.de 193.174.104.33NOERROR, 9 ms, authoritativenoyes / yesrefused9.20.21
nsext2.mh-hannover.de 193.174.104.34NOERROR, 9 ms, authoritativenoyes / yesrefused9.20.21

Checks

  • ✓ All respond #14
    All 2 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: nsext1.mh-hannover.de: "9.20.21"; nsext2.mh-hannover.de: "9.20.21". 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 2026100503 · primary nsext1.mh-hannover.de

Found

Primary (MNAME)
nsext1.mh-hannover.de
Contact (RNAME)
inetmaster.mh-hannover.de
Serial
2026100503
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
nsext1.mh-hannover.de (193.174.104.33)2026100503
nsext2.mh-hannover.de (193.174.104.34)2026100503

Checks

  • ✓ Serial 2026100503 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 nsext1.mh-hannover.de is one of the listed nameservers.
  • ✓ Contact inetmaster@mh-hannover.de #25
    The SOA RNAME inetmaster.mh-hannover.de means inetmaster@mh-hannover.de.
  • ✓ Date-based serial #26
    The serial 2026100503 follows the YYYYMMDDnn convention (2026-10-05).

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

pass

8 records at the apex

Found

Read from
193.174.104.33:53
TypeValueTTL
SOAnsext1.mh-hannover.de. inetmaster.mh-hannover.de. 2026100503 10800 3600 604800 360010800
NSnsext1.mh-hannover.de.10800
NSnsext2.mh-hannover.de.10800
A193.174.105.7010800
MX10 mx01.ionos.de.10800
MX10 mx00.ionos.de.10800
CAA0 issue "harica.gr"10800
CAA0 issue "pki.dfn.de"10800

Checks

  • ✓ TTLs within range #32
    TTLs: A 3h, MX 3h, NS 3h. The NS TTL at the parent is 1d and in the zone 3h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: harica.gr, pki.dfn.de.