rechtbanken-tribunaux.be

Checked 22 October 2026, 07:02 UTC · via 8.8.8.8
iAll checks passed
25 passed 0 warnings 0 failed 8 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.f5clouddns.com, ns2.f5clouddns.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.f5clouddns.com, ns2.f5clouddns.com
NS in the zone
ns1.f5clouddns.com, ns2.f5clouddns.com
NameserverAddressesNetwork (AS)Glue
ns1.f5clouddns.com107.162.234.197 2604:e180:1071::3:1AS55002 DEFENSE-NET - F5, Inc., US AS55002 DEFENSE-NET - F5, Inc., US-
ns2.f5clouddns.com107.162.176.221 2604:e180:1071::ffff:6ba2:b0ddAS55002 DEFENSE-NET - F5, Inc., US AS55002 DEFENSE-NET - F5, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.f5clouddns.com, ns2.f5clouddns.com.
    #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.
  • i
    One address family in one network
    all IPv6 addresses are in 2604:e180:1071::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS55002 (DEFENSE-NET - F5, Inc., US): 4 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 .com
    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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.f5clouddns.com 107.162.234.197NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns1.f5clouddns.com 2604:e180:1071::3:1NOERROR, 182 ms, authoritativenoyes / yesrefused-
ns2.f5clouddns.com 107.162.176.221NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.f5clouddns.com 2604:e180:1071::ffff:6ba2:b0ddNOERROR, 26 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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

pass

serial 2026050408 · primary ns1.f5clouddns.com

Found

Primary (MNAME)
ns1.f5clouddns.com
Contact (RNAME)
f5xc-dns.f5.com
Serial
2026050408
Refresh / retry
10800 s / 1080 s
Expire
2419200 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.f5clouddns.com (107.162.234.197)2026050408
ns1.f5clouddns.com (2604:e180:1071::3:1)2026050408
ns2.f5clouddns.com (107.162.176.221)2026050408
ns2.f5clouddns.com (2604:e180:1071::ffff:6ba2:b0dd)2026050408

Checks

  • ✓ Serial 2026050408 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 18m, expire 28d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.f5clouddns.com is one of the listed nameservers.
  • ✓ Contact f5xc-dns@f5.com #25
    The SOA RNAME f5xc-dns.f5.com means f5xc-dns@f5.com.
  • ✓ Date-based serial #26
    The serial 2026050408 follows the YYYYMMDDnn convention (2026-05-04).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
8115ECDSAP256SHA256 (13)SHA256 50A4C3BFF8E712FF…yes

DNSKEY in the zone

Key tagRoleAlgorithm
8115KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 8115 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

6 records at the apex

Found

Read from
107.162.234.197:53
TypeValueTTL
SOAns1.f5clouddns.com. f5xc-dns.f5.com. 2026050408 10800 1080 2419200 90028800
NSns2.f5clouddns.com.86400
NSns1.f5clouddns.com.86400
A193.191.241.11428800
TXT"HARICA-R677Tjig1DTaZ2rG6n4"28800
TXT"v=spf1 -all"28800

Checks

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