michelin.be

.be country-code

Found

TLD

.be (country-code)

ICANN policies apply

no

Checks

• i

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

  .be is delegated in the root zone and DNSSEC-signed.
• i

  Registration data not available

  No registration data via RDAP: the registry of .be offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.

  #3

udns1.cscdns.net, udns2.cscdns.uk

Found

Parent zone

be

Delegation from

a.nsset.be (194.0.6.1)

NS at the parent

udns1.cscdns.net, udns2.cscdns.uk

NS in the zone

udns1.cscdns.net, udns2.cscdns.uk

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: udns1.cscdns.net, udns2.cscdns.uk.

  #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.
• ✓ 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 (AS12008 (VERCARA - Vercara, LLC, US): 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
• ✓ Nameserver names under 2 TLDs #12

  Nameserver names use the TLDs .net, .uk.
• ✓ 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: udns1.cscdns.net: "UltraDNS Nameserver"; udns2.cscdns.uk: "UltraDNS Nameserver".

  #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 2005083224 · primary pdns1.cscdns.net

Found

Primary (MNAME)

pdns1.cscdns.net

Contact (RNAME)

hostmaster.cscdns.net

Serial

2005083224

Refresh / retry

86400 s / 7200 s

Expire

2592000 s

Negative TTL

600 s

Serial per nameserver

Checks

• ✓ Serial 2005083224 everywhere #22

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

  SOA refresh 1d, retry 2h, expire 30d, negative TTL 10m.
• i

  Hidden master

  The primary nameserver pdns1.cscdns.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@cscdns.net #25

  The SOA RNAME hostmaster.cscdns.net means hostmaster@cscdns.net.
• ✓ Timestamp serial #26

  The serial 2005083224 is a Unix timestamp (2033-07-15 23:33 UTC).

Signed, DS published at parent

Found

Validated by resolver

yes

Denial of existence

NSEC

Signatures valid until

3 November 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 48723 (SHA256).
• ✓ Modern algorithms #29

  Key algorithms: ECDSAP256SHA256 (13).
• ✓ Signatures valid until 2026-11-03 #30

  The earliest DNSKEY/SOA signature expires at 2026-11-03 13:51 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