km.be

Checked 22 October 2026, 06:41 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 warnings 0 failed 5 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.vandenbroele.be, ns2.vandenbroele.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.vandenbroele.be, ns2.vandenbroele.be
NS in the zone
ns1.vandenbroele.be, ns2.vandenbroele.be
NameserverAddressesNetwork (AS)Glue
ns1.vandenbroele.be212.123.19.131AS6848 TELENET-AS - Telenet BV, BE212.123.19.131
ns2.vandenbroele.be93.94.109.159AS44806 KINAMO-BACKBONE - Kinamo N.V., BE93.94.109.159

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.vandenbroele.be, ns2.vandenbroele.be.
    #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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS44806 (KINAMO-BACKBONE - Kinamo N.V., BE): 1 address; AS6848 (TELENET-AS - Telenet BV, BE): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.vandenbroele.be 212.123.19.131NOERROR, 26 ms, authoritativenoyes / yesrefused-
ns2.vandenbroele.be 93.94.109.159NOERROR, 13 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

warn

serial 2024112002 · primary ns1.vandenbroele.be

Found

Primary (MNAME)
ns1.vandenbroele.be
Contact (RNAME)
dnsmaster.vandenbroele.be
Serial
2024112002
Refresh / retry
7200 s / 7200 s
Expire
1209600 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns1.vandenbroele.be (212.123.19.131)2024112002
ns2.vandenbroele.be (93.94.109.159)2024112002

Checks

  • ✓ Serial 2024112002 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 2h should be shorter than refresh 2h. Current values: refresh 2h, retry 2h, expire 14d, negative TTL 2h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.vandenbroele.be is one of the listed nameservers.
  • ✓ Contact dnsmaster@vandenbroele.be #25
    The SOA RNAME dnsmaster.vandenbroele.be means dnsmaster@vandenbroele.be.
  • ✓ Date-based serial #26
    The serial 2024112002 follows the YYYYMMDDnn convention (2024-11-20).

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

11 records at the apex

Found

Read from
212.123.19.131:53
TypeValueTTL
SOAns1.vandenbroele.be. dnsmaster.vandenbroele.be. 2024112002 7200 7200 1209600 72007200
NSns1.vandenbroele.be.7200
NSns2.vandenbroele.be.7200
A194.32.155.19120
AAAA2a02:5b41:4:440::d120
MX10 d310698.a.ess.de.barracudanetworks.com.7200
MX20 d310698.b.ess.de.barracudanetworks.com.7200
TXT"apple-domain-verification=LaaUbjYuIXZywROb"7200
TXT"v=spf1 ip4:84.198.170.56 ip4:91.183.47.114 include:spf.mandrillapp.com include:spf.ess.de.barracudanetworks.com include:spf.protection.outlook.com include:_mail.level27.eu ~all"7200
TXT"MS=ms72886022"7200
TXT"6YwcJK28s6D2+LKMZ946FprI/g3rIBRh+B9oFWldNecklklUlAEJc9uYkrHk3tvKxa50hnE2hdatBQk8k9H5Kg=="7200

Checks

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