euronics.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.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.net

Found

Parent zone

de

Delegation from

a.nic.de (194.0.0.53)

NS at the parent

dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.net

NS in the zone

dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.net

Checks

• ✓ 4 nameservers #6

  Delegated to dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.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 2 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS62597 (NSONE - NSONE Inc, US): 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.

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: dns1.p02.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns2.p02.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns3.p02.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns4.p02.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9".

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

serial 1762348372 · primary dns1.p01.nsone.net

Found

Primary (MNAME)

dns1.p01.nsone.net

Contact (RNAME)

hostmaster.euronics.de

Serial

1762348372

Refresh / retry

43200 s / 7200 s

Expire

1209600 s

Negative TTL

3600 s

Serial per nameserver

Checks

• ✓ Serial 1762348372 everywhere #22

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

  SOA refresh 12h, retry 2h, expire 14d, negative TTL 1h.
• i

  Hidden master

  The primary nameserver dns1.p01.nsone.net 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@euronics.de #25

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

  The serial 1762348372 is a Unix timestamp (2025-11-05 13:12 UTC).

Signed, DS published at parent

Found

Validated by resolver

yes

Denial of existence

NSEC

Signatures valid until

22 October 2026

DS at the parent

DNSKEY in the zone

Checks

• ✓ Signed and validated #27

  The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
• ✓ DS matches a key #28

  The DS record at the parent matches a key in the zone: key tag 48553 (SHA256).
• ✓ Modern algorithms #29

  Key algorithms: ECDSAP256SHA256 (13).
• ✓ Short-lived signatures (online signing) #30

  Signatures are valid for 26h0m0s and created on demand; the current one was made at 2026-10-21 21:19 UTC and expires at 2026-10-22 23:19 UTC.
• i

  NSEC

  The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.

  #31