khk.be

Checked 22 October 2026, 06:41 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 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

warn

ns1.belnet.be, ns2.belnet.be, ns3.belnet.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.belnet.be, ns2.belnet.be, ns3.belnet.be
NS in the zone
ns.khk.be, ns1.belnet.be, ns2.belnet.be
NameserverAddressesNetwork (AS)Glue
ns.khk.be (zone only)193.190.124.29AS2611 BELNET - BELNET, BE-
ns1.belnet.be193.190.198.14 2001:6a8:3c80::14AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE193.190.198.14 2001:6a8:3c80::14
ns2.belnet.be193.190.182.40 2001:6a8:3c80:c000::40AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE193.190.182.40 2001:6a8:3c80:c000::40
ns3.belnet.be (parent only)194.58.196.32 2a01:3f1:832::53AS8674 NETNOD-IX - Netnod AB, SE AS8674 NETNOD-IX - Netnod AB, SE194.58.196.32 2a01:3f1:832::53

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.belnet.be, ns2.belnet.be, ns3.belnet.be.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns3.belnet.be; only in the zone: ns.khk.be. ns.khk.be, ns1.belnet.be, ns2.belnet.be, ns3.belnet.be report NS ns.khk.be ns1.belnet.be ns2.belnet.be.
    #7
  • ✓ 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 4 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS2611 (BELNET - BELNET, BE): 5 addresses; AS8674 (NETNOD-IX - Netnod AB, SE): 2 addresses.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns.khk.be.
    #13

Nameservers

info

7 of 7 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.khk.be 193.190.124.29NOERROR, 22 ms, authoritativenoyes / yesrefusedundisclosed
ns1.belnet.be 193.190.198.14NOERROR, 13 ms, authoritativenoyes / yesrefusedFor me to know, for you to guess!
ns1.belnet.be 2001:6a8:3c80::14NOERROR, 17 ms, authoritativenoyes / yesrefusedFor me to know, for you to guess!
ns2.belnet.be 193.190.182.40NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns2.belnet.be 2001:6a8:3c80:c000::40NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns3.belnet.be 194.58.196.32NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns3.belnet.be 2a01:3f1:832::53NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 7 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: ns.khk.be: "undisclosed"; ns1.belnet.be: "For me to know, for you to guess!".
    #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 2024041001 · primary ns.khk.be

Found

Primary (MNAME)
ns.khk.be
Contact (RNAME)
dnsmaster.khk.be
Serial
2024041001
Refresh / retry
10800 s / 1800 s
Expire
1814400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.khk.be (193.190.124.29)2024041001
ns1.belnet.be (193.190.198.14)2024041001
ns1.belnet.be (2001:6a8:3c80::14)2024041001
ns2.belnet.be (193.190.182.40)2024041001
ns2.belnet.be (2001:6a8:3c80:c000::40)2024041001
ns3.belnet.be (194.58.196.32)2024041001
ns3.belnet.be (2a01:3f1:832::53)2024041001

Checks

  • ✓ Serial 2024041001 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 21d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.khk.be is one of the listed nameservers.
  • ✓ Contact dnsmaster@khk.be #25
    The SOA RNAME dnsmaster.khk.be means dnsmaster@khk.be.
  • ✓ Date-based serial #26
    The serial 2024041001 follows the YYYYMMDDnn convention (2024-04-10).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

8 records at the apex

Found

Read from
193.190.124.29:53
TypeValueTTL
SOAns.khk.be. dnsmaster.khk.be. 2024041001 10800 1800 1814400 36003600
NSns1.belnet.be.3600
NSns.khk.be.3600
NSns2.belnet.be.3600
A193.190.124.813600
MX10 relay.thomasmore.be.60
TXT"MS=ms93662791"60
TXT"v=spf1 mx ip4:193.190.67.1/24 ip4:134.58.240.1/23 ip4:193.190.124.0/24 ip4:216.128.14.4 ip4:213.193.222.192 ip4:193.190.63.128/26 ip4:64.233.184.1/24 ip4:87.238.162.138 ip4:193.191.186.128/26 ip6:2a02:2c40:0:c0::25:0/112 -all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32
  • ✓ 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