hamburg.de

.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

ns2.mcs.de, ns3.mcs.de

Found

Parent zone

de

Delegation from

a.nic.de (194.0.0.53)

NS at the parent

ns2.mcs.de, ns3.mcs.de

NS in the zone

ns2.mcs.de, ns3.mcs.de

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns2.mcs.de, ns3.mcs.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 different networks #10

  The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
• ✓ 2 autonomous systems #11

  The nameservers are spread over: AS197540 (netcup-AS - netcup GmbH, DE): 2 addresses; AS215992 (MCS-AS - MCS GmbH, DE): 2 addresses.
• 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
• ✓ All reachable over IPv6 #13

  Every nameserver has an IPv6 address.

serial 2026102012 · primary ns1.mcs.de

Found

Primary (MNAME)

ns1.mcs.de

Contact (RNAME)

hostmaster.mcs.de

Serial

2026102012

Refresh / retry

14400 s / 3600 s

Expire

604800 s

Negative TTL

600 s

Serial per nameserver

Checks

• ✓ Serial 2026102012 everywhere #22

  All nameservers serve the same version of the zone.
• ✓ Timers within recommendations #23

  SOA refresh 4h, retry 1h, expire 7d, negative TTL 10m.
• i

  Hidden master

  The primary nameserver ns1.mcs.de is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.

  #24
• ✓ Contact hostmaster@mcs.de #25

  The SOA RNAME hostmaster.mcs.de means hostmaster@mcs.de.
• ✓ Date-based serial #26

  The serial 2026102012 follows the YYYYMMDDnn convention (2026-10-20).

Signed, DS published at parent

Found

Validated by resolver

yes

Denial of existence

NSEC

Signatures valid until

29 October 2026

DS at the parent

DNSKEY in the zone

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 12989 (SHA256).
• ✓ Modern algorithms #29

  Key algorithms: ECDSAP256SHA256 (13).
• ✓ Signatures valid until 2026-10-29 #30

  The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
• i

  NSEC

  The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.

  #31