netztransparenz.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

dns1.metaways.net, dns2.metaways.net, dns3.metaways.net, dns4.metaways.net

Found

Parent zone

de

Delegation from

a.nic.de (194.0.0.53)

NS at the parent

dns1.metaways.net, dns2.metaways.net, dns3.metaways.net, dns4.metaways.net

NS in the zone

dns1.metaways.net, dns2.metaways.net, dns3.metaways.net, dns4.metaways.net

Checks

• ✓ 4 nameservers #6

  Delegated to dns1.metaways.net, dns2.metaways.net, dns3.metaways.net, dns4.metaways.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 2 IPv4 /24s and 4 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS44225 (Metaways - Metaways Infosystems 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 .net

  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 2026022602 · primary ns1.50hertz.com

Found

Primary (MNAME)

ns1.50hertz.com

Contact (RNAME)

noc.50hertz.com

Serial

2026022602

Refresh / retry

14400 s / 3600 s

Expire

3024000 s

Negative TTL

900 s

Serial per nameserver

Checks

• ✓ Serial 2026022602 everywhere #22

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

  SOA refresh 4h, retry 1h, expire 35d, negative TTL 15m.
• i

  Hidden master

  The primary nameserver ns1.50hertz.com 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 noc@50hertz.com #25

  The SOA RNAME noc.50hertz.com means noc@50hertz.com.
• ✓ Date-based serial #26

  The serial 2026022602 follows the YYYYMMDDnn convention (2026-02-26).

17 records at the apex

Found

Read from

109.232.170.117:53

Checks

• ✓ TTLs within range #32

  TTLs: A 1d, MX 5m, NS 1d.
• ✓ 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