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

blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org

Found

Parent zone

de

Delegation from

a.nic.de (194.0.0.53)

NS at the parent

blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org

NS in the zone

blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org

Checks

• ✓ 3 nameservers #6

  Delegated to blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org.
• ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 18 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

  #11
• ✓ Nameserver names under 3 TLDs #12

  Nameserver names use the TLDs .com, .net, .org.
• ✓ All reachable over IPv6 #13

  Every nameserver has an IPv6 address.

serial 2016032458 · primary ns1.digikey.com

Found

Primary (MNAME)

ns1.digikey.com

Contact (RNAME)

hostmaster.digikey.com

Serial

2016032458

Refresh / retry

10800 s / 3600 s

Expire

2419200 s

Negative TTL

3600 s

Serial per nameserver

Checks

• ✓ Serial 2016032458 everywhere #22

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

  SOA refresh 3h, retry 1h, expire 28d, negative TTL 1h.
• i

  Hidden master

  The primary nameserver ns1.digikey.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 hostmaster@digikey.com #25

  The SOA RNAME hostmaster.digikey.com means hostmaster@digikey.com.
• ✓ Date-based serial #26

  The serial 2016032458 follows the YYYYMMDDnn convention (2016-03-24).

12 records at the apex

Found

Read from

172.64.40.1:53

Checks

• ✓ TTLs within range #32

  TTLs: A 1h, MX 1h, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
• ✓ 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