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

ns1.kundencontroller.de, ns2.kundencontroller.de

Found

Parent zone

de

Delegation from

a.nic.de (194.0.0.53)

NS at the parent

ns1.kundencontroller.de, ns2.kundencontroller.de

NS in the zone

ns1.kundencontroller.de, ns2.kundencontroller.de

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.kundencontroller.de, ns2.kundencontroller.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 2a02:180:ffff::/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 (AS35366 (ISPPRO-AS - ISPpro Internet KG, 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.

serial 2147483647 · primary k1.kundencontroller.de

Found

Primary (MNAME)

k1.kundencontroller.de

Contact (RNAME)

hostmaster.kundencontroller.de

Serial

2147483647

Refresh / retry

10800 s / 3600 s

Expire

604800 s

Negative TTL

3600 s

Serial per nameserver

Checks

• ✓ Serial 2147483647 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.
• i

  Hidden master

  The primary nameserver k1.kundencontroller.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@kundencontroller.de #25

  The SOA RNAME hostmaster.kundencontroller.de means hostmaster@kundencontroller.de.
• ✓ Timestamp serial #26

  The serial 2147483647 is a Unix timestamp (2038-01-19 03:14 UTC).

7 records at the apex

Found

Read from

85.31.185.126:53

Checks

• ✓ TTLs within range #32

  TTLs: A 1d, AAAA 1d, MX 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