bbforum.be

Checked 22 October 2026, 06:10 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 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.futureweb.be, ns2.futureweb.be, ns3.futureweb.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.futureweb.be, ns2.futureweb.be, ns3.futureweb.be
NS in the zone
ns1.futureweb.be, ns2.futureweb.be, ns3.futureweb.be
NameserverAddressesNetwork (AS)Glue
ns1.futureweb.be51.210.150.177 2001:41d0:304:200::7ed4AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR51.210.150.177 2001:41d0:304:200::7ed4
ns2.futureweb.be81.95.126.138 2a04:b80:1:4::bAS42160 LCPDCO - DC STAR nv, BE AS42160 LCPDCO - DC STAR nv, BE81.95.126.138 2a04:b80:1:4::b
ns3.futureweb.be185.70.72.73 2a05:2880::cAS59827 Futureweb-AS - Futureweb BVBA, BE AS59827 Futureweb-AS - Futureweb BVBA, BE185.70.72.73 2a05:2880::c

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.futureweb.be, ns2.futureweb.be, ns3.futureweb.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 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 2 addresses; AS42160 (LCPDCO - DC STAR nv, BE): 2 addresses; AS59827 (Futureweb-AS - Futureweb BVBA, BE): 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

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.futureweb.be 51.210.150.177NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns1.futureweb.be 2001:41d0:304:200::7ed4NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns2.futureweb.be 81.95.126.138NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2.futureweb.be 2a04:b80:1:4::bNOERROR, 15 ms, authoritativenoyes / yesrefused-
ns3.futureweb.be 185.70.72.73NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns3.futureweb.be 2a05:2880::cNOERROR, 13 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.
  • ✓ 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 2026102100 · primary ns1.futureweb.be

Found

Primary (MNAME)
ns1.futureweb.be
Contact (RNAME)
hostmaster.bbforum.be
Serial
2026102100
Refresh / retry
14400 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.futureweb.be (51.210.150.177)2026102100
ns1.futureweb.be (2001:41d0:304:200::7ed4)2026102100
ns2.futureweb.be (81.95.126.138)2026102100
ns2.futureweb.be (2a04:b80:1:4::b)2026102100
ns3.futureweb.be (185.70.72.73)2026102100
ns3.futureweb.be (2a05:2880::c)2026102100

Checks

  • ✓ Serial 2026102100 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.futureweb.be is one of the listed nameservers.
  • ✓ Contact hostmaster@bbforum.be #25
    The SOA RNAME hostmaster.bbforum.be means hostmaster@bbforum.be.
  • ✓ Date-based serial #26
    The serial 2026102100 follows the YYYYMMDDnn convention (2026-10-21).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
11 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
48515ED25519 (15)SHA256 428FD3EBE22CFBB6…yes

DNSKEY in the zone

Key tagRoleAlgorithm
55436ZSK (256)ED25519 (15)
48515KSK (257)ED25519 (15)

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 48515 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ED25519 (15).
  • ✓ Signatures valid until 2026-11-11 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-11 04:32 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

8 records at the apex

Found

Read from
51.210.150.177:53
TypeValueTTL
SOAns1.futureweb.be. hostmaster.bbforum.be. 2026102100 14400 3600 1209600 8640014400
NSns1.futureweb.be.14400
NSns2.futureweb.be.14400
NSns3.futureweb.be.14400
A185.70.73.24314400
AAAA2a05:2880:e:c::14400
MX10 mail1.futureweb.be.14400
TXT"v=spf1 a mx ip4:185.70.72.0/22 ip6:2a05:2880::/29"14400

Checks

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