lokeren.be

Checked 22 October 2026, 06:50 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 6 info

Registration

info

.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

Delegation

info

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
NameserverAddressesNetwork (AS)Glue
ns1.cloud.telenet.be85.255.200.200 2a01:498:8301:1c0::200AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-
ns2.cloud.telenet.be195.130.154.74 2a01:498:8101:4c0::200AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-
ns3.cloud.telenet.be185.35.52.200 2a01:498:8501:4090::6:1AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, 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.

Nameservers

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.cloud.telenet.be 85.255.200.200NOERROR, 19 ms, authoritativenoyes / yesrefused<HIDDEN>
ns1.cloud.telenet.be 2a01:498:8301:1c0::200NOERROR, 16 ms, authoritativenoyes / yesrefused<HIDDEN>
ns2.cloud.telenet.be 195.130.154.74NOERROR, 25 ms, authoritativenoyes / yesrefused<HIDDEN>
ns2.cloud.telenet.be 2a01:498:8101:4c0::200NOERROR, 15 ms, authoritativenoyes / yesrefused<HIDDEN>
ns3.cloud.telenet.be 185.35.52.200NOERROR, 19 ms, authoritativenoyes / yesrefused<HIDDEN>
ns3.cloud.telenet.be 2a01:498:8501:4090::6:1NOERROR, 13 ms, authoritativenoyes / yesrefused<HIDDEN>

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.

SOA

pass

serial 1787829067 · primary ns1.cloud.telenet.be

Found

Primary (MNAME)
ns1.cloud.telenet.be
Contact (RNAME)
postmaster.lokeren.be
Serial
1787829067
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.cloud.telenet.be (85.255.200.200)1787829067
ns1.cloud.telenet.be (2a01:498:8301:1c0::200)1787829067
ns2.cloud.telenet.be (195.130.154.74)1787829067
ns2.cloud.telenet.be (2a01:498:8101:4c0::200)1787829067
ns3.cloud.telenet.be (185.35.52.200)1787829067
ns3.cloud.telenet.be (2a01:498:8501:4090::6:1)1787829067

Checks

  • ✓ Serial 1787829067 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.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.cloud.telenet.be is one of the listed nameservers.
  • ✓ Contact postmaster@lokeren.be #25
    The SOA RNAME postmaster.lokeren.be means postmaster@lokeren.be.
  • ✓ Timestamp serial #26
    The serial 1787829067 is a Unix timestamp (2026-08-27 11:11 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
10 iterations, 16-byte salt
Signatures valid until
27 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
42444ECDSAP256SHA256 (13)SHA256 12E42867F2DBC056…yes

DNSKEY in the zone

Key tagRoleAlgorithm
33138KSK (257)ECDSAP256SHA256 (13)
42444KSK (257)ECDSAP256SHA256 (13)
40048ZSK (256)ECDSAP256SHA256 (13)
42765KSK (257)ECDSAP256SHA256 (13)

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 42444 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • !
    Signatures expire soon
    The earliest signature expires at 2026-10-27 12:02 UTC (in 125h0m0s). Check that automatic re-signing works.
    #30
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 10 iterations and a 16-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

info

12 records at the apex

Found

Read from
85.255.200.200:53
TypeValueTTL
SOAns1.cloud.telenet.be. postmaster.lokeren.be. 1787829067 86400 7200 3600000 900900
NSns1.cloud.telenet.be.900
NSns3.cloud.telenet.be.900
NSns2.cloud.telenet.be.900
A185.111.197.215900
MX0 lokeren-be.k-v1.mx.microsoft.900
TXT"v=spf1 include:_spf.lokeren.be -all"900
TXT"6BP5AxyZefqsh1jL9btBJAOCtTjz3Kqv/YsMCG4yIy3c2gWldCG627ko0jzNH/osB+gE3ygi0FxZIo6bli8wVQ=="900
TXT"P0OCO9WRhX3AYouLB4sI4HIZJMtSB5UaR1extsZU0yeM7gwYtTv9o2aNyaQulzZf7+YVA5K5MNQI5Z8YAAistg=="900
TXT"MS=ms37511656"900
TXT"typ68crsq2vd7vxnq1cmppwgtghp95qh"900
TXT"_n4j7ut9raouh4a99ex4d9sfrz8mgzh5"900

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, MX 15m, NS 15m. The NS TTL at the parent is 1d and in the zone 15m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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