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

n01.public.auth.dns.services.k-net.io, n02.public.auth.dns.services.k-net.io, n03.public.auth.dns.services.k-net.io, n04.public.auth.dns.services.k-net.io

Found

Parent zone

de

Delegation from

a.nic.de (194.0.0.53)

NS at the parent

n01.public.auth.dns.services.k-net.io, n02.public.auth.dns.services.k-net.io, n03.public.auth.dns.services.k-net.io, n04.public.auth.dns.services.k-net.io

NS in the zone

n01.public.auth.dns.services.k-net.io, n02.public.auth.dns.services.k-net.io, n03.public.auth.dns.services.k-net.io, n04.public.auth.dns.services.k-net.io

Checks

• ✓ 4 nameservers #6

  Delegated to n01.public.auth.dns.services.k-net.io, n02.public.auth.dns.services.k-net.io, n03.public.auth.dns.services.k-net.io, n04.public.auth.dns.services.k-net.io.
• ✓ 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 4 IPv4 /24s and 2 IPv6 /48s.
• ✓ 2 autonomous systems #11

  The nameservers are spread over: AS15418 (IONOS-ANYCAST - Fasthosts Internet Limited, GB): 4 addresses; AS8560 (IONOS-AS - IONOS SE, DE): 4 addresses.
• i

  All nameserver names under .io

  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.

8 of 8 addresses answer authoritatively

Found

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.
• i

  Identifying string disclosed

  These nameservers answer version queries with a string that is not a version number: n01.public.auth.dns.services.k-net.io: "Served by PowerDNS - https://www.powerdns.com/"; n02.public.auth.dns.services.k-net.io: "Served by PowerDNS - https://www.powerdns.com/"; n03.public.auth.dns.services.k-net.io: "Served by PowerDNS - https://www.powerdns.com/"; n04.public.auth.dns.services.k-net.io: "Served by PowerDNS - https://www.powerdns.com/".

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