db-thueringen.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

dns-extern-01.uni-jena.de, dns-extern-02.uni-jena.de

Found

Parent zone

de

Delegation from

a.nic.de (194.0.0.53)

NS at the parent

dns-extern-01.uni-jena.de, dns-extern-02.uni-jena.de

NS in the zone

dns-extern-01.uni-jena.de, dns-extern-02.uni-jena.de

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns-extern-01.uni-jena.de, dns-extern-02.uni-jena.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.
• i

  One address family in one network

  all IPv6 addresses are in 2001:638:1558::/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 (AS680 (DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE): 4 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
• ✓ All reachable over IPv6 #13

  Every nameserver has an IPv6 address.

4 of 4 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 4 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: dns-extern-01.uni-jena.de: "none"; dns-extern-02.uni-jena.de: "none".

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

7 records at the apex

Found

Read from

141.35.104.106:53

Checks

• ✓ TTLs within range #32

  TTLs: A 1d, AAAA 1d, NS 1d.
• ✓ No CNAME at the apex #33

  The zone apex has no CNAME record.
• i

  Wildcard record

  A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

  #34
• 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