kvmechelen.be

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

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.web01.kvmechelen.be, ns2.web01.kvmechelen.be
NS in the zone
ns1.web01.kvmechelen.be, ns2.web01.kvmechelen.be
NameserverAddressesNetwork (AS)Glue
ns1.web01.kvmechelen.be109.68.161.32AS39923 AS-UNIXSOLUTIONS - Unix-Solutions BV, BE109.68.161.32
ns2.web01.kvmechelen.be109.68.161.32AS39923 AS-UNIXSOLUTIONS - Unix-Solutions BV, BE109.68.161.32

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.web01.kvmechelen.be, ns2.web01.kvmechelen.be.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.web01.kvmechelen.be, ns2.web01.kvmechelen.be.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 109.68.161.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS39923 (AS-UNIXSOLUTIONS - Unix-Solutions BV, BE): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.web01.kvmechelen.be 109.68.161.32NOERROR, 13 ms, authoritativenoyes / yesrefused9.16.50-Debian
ns2.web01.kvmechelen.be 109.68.161.32NOERROR, 13 ms, authoritativenoyes / yesrefused9.16.50-Debian

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.web01.kvmechelen.be: "9.16.50-Debian"; ns2.web01.kvmechelen.be: "9.16.50-Debian". Hide or replace the version string.
    #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

warn

serial 2026101301 · primary ns1.web01.kvmechelen.be

Found

Primary (MNAME)
ns1.web01.kvmechelen.be
Contact (RNAME)
hostmaster.kvmechelen.be
Serial
2026101301
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.web01.kvmechelen.be (109.68.161.32)2026101301
ns2.web01.kvmechelen.be (109.68.161.32)2026101301

Checks

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

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

info

9 records at the apex

Found

Read from
109.68.161.32:53
TypeValueTTL
SOAns1.web01.kvmechelen.be. hostmaster.kvmechelen.be. 2026101301 3600 3600 1209600 864003600
NSns2.web01.kvmechelen.be.300
NSns1.web01.kvmechelen.be.300
A109.106.245.86300
MX0 kvmechelen-be.mail.protection.outlook.com.300
TXT"google-site-verification=LkWj0zVNEu9fFG-UjHE5rpKRLJwLJCYrhbw2-m3STd0"300
TXT"facebook-domain-verification=jwudfs0yhn1jlybvqdcv9cwlycd3bh"300
TXT"apple-domain-verification=4wIuWv1MvETSV9E2"300
TXT"v=spf1 a mx include:spf.afas.online include:_spf.eu.sparkpostmail.com include:spf.protection.outlook.com include:netblocks.unix-solutions.be ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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