visithasselt.be

Checked 22 October 2026, 07:21 UTC · via 8.8.8.8
!Passed with warnings
18 passed 5 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.smaakkamer.be, ns2.smaakkamer.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.smaakkamer.be, ns2.smaakkamer.be
NS in the zone
ns1.smaakkamer.be, ns2.smaakkamer.be
NameserverAddressesNetwork (AS)Glue
ns1.smaakkamer.be37.252.124.170AS196752 TILAA - Tilaa B.V., NL37.252.124.170
ns2.smaakkamer.be37.252.124.201AS196752 TILAA - Tilaa B.V., NL37.252.124.201

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.smaakkamer.be, ns2.smaakkamer.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 one network
    all IPv4 addresses are in 37.252.124.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 (AS196752 (TILAA - Tilaa B.V., NL): 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.smaakkamer.be 37.252.124.170NOERROR, 9 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)
ns2.smaakkamer.be 37.252.124.201NOERROR, 9 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)

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.smaakkamer.be: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)"; ns2.smaakkamer.be: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)". 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 2026012004 · primary ns1.smaakkamer.be

Found

Primary (MNAME)
ns1.smaakkamer.be
Contact (RNAME)
steven.thys.hasselt.be
Serial
2026012004
Refresh / retry
900 s / 900 s
Expire
3600000 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.smaakkamer.be (37.252.124.170)2026012004
ns2.smaakkamer.be (37.252.124.201)2026012004

Checks

  • ✓ Serial 2026012004 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; retry 15m should be shorter than refresh 15m. Current values: refresh 15m, retry 15m, expire 1000h, negative TTL 15m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.smaakkamer.be is one of the listed nameservers.
  • ✓ Contact steven@thys.hasselt.be #25
    The SOA RNAME steven.thys.hasselt.be means steven@thys.hasselt.be.
  • ✓ Date-based serial #26
    The serial 2026012004 follows the YYYYMMDDnn convention (2026-01-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

info

6 records at the apex

Found

Read from
37.252.124.170:53
TypeValueTTL
SOAns1.smaakkamer.be. steven.thys.hasselt.be. 2026012004 900 900 3600000 90086400
NSns1.smaakkamer.be.86400
NSns2.smaakkamer.be.86400
A194.32.153.51900
MX0 visithasselt.be.14400
TXT"google-site-verification=N2KkIUviT4nayTXSRMbtYDfVbBueL3IkKmlsvPNqg7c"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, MX 4h, NS 1d.
  • ✓ 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