huderf.be

Checked 22 October 2026, 06:40 UTC · via 8.8.8.8
!Passed with warnings
21 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.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
ns1.belnet.be, ns2.belnet.be, ns3.belnet.be
NameserverAddressesNetwork (AS)Glue
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.be194.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.
  • ✓ 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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS2611 (BELNET - BELNET, BE): 4 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

6 of 6 addresses answer authoritatively

Found

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

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.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

warn

serial 59 · primary nsmaster.hubruxelles.be

Found

Primary (MNAME)
nsmaster.hubruxelles.be
Contact (RNAME)
network.erasme.ulb.ac.be
Serial
59
Refresh / retry
900 s / 600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

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

Checks

  • ✓ Serial 59 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d. Current values: refresh 15m, retry 10m, expire 14d, negative TTL 1h.
    #23
  • i
    Hidden master (not resolvable)
    The primary nameserver nsmaster.hubruxelles.be is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact network@erasme.ulb.ac.be #25
    The SOA RNAME network.erasme.ulb.ac.be means network@erasme.ulb.ac.be.
  • ✓ Counter serial #26
    The serial 59 is a plain counter.

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

14 records at the apex

Found

Read from
193.190.198.14:53
TypeValueTTL
SOAnsmaster.hubruxelles.be. network.erasme.ulb.ac.be. 59 900 600 1209600 36003600
NSns3.belnet.be.3600
NSns1.belnet.be.3600
NSns2.belnet.be.3600
A20.74.41.1903600
MX20 mx2.hubruxelles.be.1800
MX10 mx1.hubruxelles.be.1800
TXT"HARICA-8kdGE3TNWtg0Hxuf7Vw"3600
TXT"MS=ms89234952"3600
TXT"onetrust-domain-verification=f2dffedc865448d5ac50d228846d43f1"3600
TXT"google-site-verification=xoqGsco1rCR8gVSKdKI9zbZd6Y1hZHGkLYWT2I1atUs"3600
TXT"HARICA-wanoFA921zutzrqbang"3600
TXT"t8528perlm3t66d3jtq0dnudf9"3600
TXT"v=spf1 a ip4:193.191.184.208 ip4:193.191.184.209 include:hubruxelles.be include:spf-00585401.pphosted.com -all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 30m, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; 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