wikifin.be

Checked 22 October 2026, 07:30 UTC · via 8.8.8.8
✗Problems found
21 passed 2 warnings 2 failed 4 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

fail

ns3.nrb.be, ns4.nrb.be, ns6.nrb.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns3.nrb.be, ns4.nrb.be, ns6.nrb.be
NS in the zone
ns3.nrb.be, ns4.nrb.be, ns5.nrb.be
NameserverAddressesNetwork (AS)Glue
ns3.nrb.be217.117.34.74 2a02:7100:0:301::100AS204013 NRB - Network Research Belgium S.A., BE AS204013 NRB - Network Research Belgium S.A., BE217.117.34.74 2a02:7100:0:301::100
ns4.nrb.be217.117.34.75 2a02:7100:0:301::101AS204013 NRB - Network Research Belgium S.A., BE AS204013 NRB - Network Research Belgium S.A., BE217.117.34.75 2a02:7100:0:301::101
ns5.nrb.be (zone only)20.107.17.246 2603:1020:201:9::d4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns6.nrb.be (parent only)(does not resolve)13.80.155.61 2603:1020:203:3::25a

Checks

  • ✓ 3 nameservers #6
    Delegated to ns3.nrb.be, ns4.nrb.be, ns6.nrb.be.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns6.nrb.be; only in the zone: ns5.nrb.be. ns3.nrb.be, ns4.nrb.be, ns5.nrb.be report NS ns3.nrb.be ns4.nrb.be ns5.nrb.be.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✗
    Nameserver names don't resolve
    These nameservers have no A or AAAA record, so they can't be reached (lame delegation): ns6.nrb.be.
    #9
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS204013 (NRB - Network Research Belgium S.A., BE): 4 addresses; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 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

fail

4 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.nrb.be 217.117.34.74NOERROR, 26 ms, authoritativenoyes / yesrefused-
ns3.nrb.be 2a02:7100:0:301::100no responsenono / no--
ns4.nrb.be 217.117.34.75NOERROR, 27 ms, authoritativenoyes / yesrefused-
ns4.nrb.be 2a02:7100:0:301::101no responsenono / no--
ns5.nrb.be 20.107.17.246NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns5.nrb.be 2603:1020:201:9::d4NOERROR, 10 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns3.nrb.be (2a02:7100:0:301::100): read udp [2a01:4f8:1c1c:eebf::1]:47560->[2a02:7100:0:301::100]:53: i/o timeout; ns4.nrb.be (2a02:7100:0:301::101): read udp [2a01:4f8:1c1c:eebf::1]:38093->[2a02:7100:0:301::101]:53: i/o timeout.
    #14
  • ✓ 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

pass

serial 87 · primary ns3.nrb.be

Found

Primary (MNAME)
ns3.nrb.be
Contact (RNAME)
hostmaster.nrb.be
Serial
87
Refresh / retry
10800 s / 3600 s
Expire
2419200 s
Negative TTL
28800 s

Serial per nameserver

NameserverSerial
ns3.nrb.be (217.117.34.74)87
ns4.nrb.be (217.117.34.75)87
ns5.nrb.be (20.107.17.246)87
ns5.nrb.be (2603:1020:201:9::d4)87

Checks

  • ✓ Serial 87 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 28d, negative TTL 8h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.nrb.be is one of the listed nameservers.
  • ✓ Contact hostmaster@nrb.be #25
    The SOA RNAME hostmaster.nrb.be means hostmaster@nrb.be.
  • ✓ Counter serial #26
    The serial 87 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

13 records at the apex

Found

Read from
217.117.34.74:53
TypeValueTTL
SOAns3.nrb.be. hostmaster.nrb.be. 87 10800 3600 2419200 28800600
NSns4.nrb.be.600
NSns3.nrb.be.600
NSns5.nrb.be.600
A217.117.44.15600
MX100 mta01.nrb.be.600
MX100 mta02.nrb.be.600
TXT"xRrneAjaH8s0O1YgwYyqzKyauEva3gx+/jes8qV0CJQ="600
TXT"globalsign-domain-verification=V5I8yWa1XaA-zGoYaFz1ZM2pp00J5HVre7VAhG4Stn"600
TXT"MS=ms40792351"600
TXT"globalsign-domain-verification=PAWZGcNoT3zK7nlT0-7cuil3qVgxpgYIE3ZA8nGVAW"600
TXT"v=spf1 a mx include:_spf.nrb.be include:servers.mcsv.net ip4:212.72.62.129/27 include:spf.protection.outlook.com -all"600
TXT"google-site-verification=U0BObi2AqJILg8kzUloVqTUhsvHAKg34MYE2L2t9qa8"600

Checks

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