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

ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be

Found

Parent zone

be

Delegation from

a.nsset.be (194.0.6.1)

NS at the parent

ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be

NS in the zone

ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be

Checks

• ✓ 3 nameservers #6

  Delegated to ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be.
• ✓ 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 (AS6848 (TELENET-AS - Telenet BV, BE): 6 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 .be

  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.

6 of 6 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 6 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: ns1.cloud.telenet.be: "<HIDDEN>"; ns2.cloud.telenet.be: "<HIDDEN>"; ns3.cloud.telenet.be: "<HIDDEN>".

  #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 1790867285 · primary lpt.vdk.be

Found

Primary (MNAME)

lpt.vdk.be

Contact (RNAME)

postmaster.vdk.be

Serial

1790867285

Refresh / retry

86400 s / 7200 s

Expire

3600000 s

Negative TTL

900 s

Serial per nameserver

Checks

• ✓ Serial 1790867285 everywhere #22

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

  SOA refresh 1d, retry 2h, expire 1000h, negative TTL 15m.
• i

  Hidden master

  The primary nameserver lpt.vdk.be 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 postmaster@vdk.be #25

  The SOA RNAME postmaster.vdk.be means postmaster@vdk.be.
• ✓ Timestamp serial #26

  The serial 1790867285 is a Unix timestamp (2026-10-01 15:08 UTC).