rbfa.be

Checked 22 October 2026, 07:02 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 warnings 0 failed 5 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

a1-247.akam.net, a11-64.akam.net, a20-65.akam.net, a28-66.akam.net, a6-67.akam.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
a1-247.akam.net, a11-64.akam.net, a20-65.akam.net, a28-66.akam.net, a6-67.akam.net
NS in the zone
a1-247.akam.net, a11-64.akam.net, a20-65.akam.net, a28-66.akam.net, a6-67.akam.net, a9-64.akam.net
NameserverAddressesNetwork (AS)Glue
a1-247.akam.net193.108.91.247 2600:1401:2::f7AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a11-64.akam.net84.53.139.64 2600:1480:1::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a20-65.akam.net95.100.175.65 2a02:26f0:67::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a28-66.akam.net95.100.173.66 2600:1480:d800::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a6-67.akam.net23.211.133.67 2600:1401:1::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a9-64.akam.net (zone only)184.85.248.64 2a02:26f0:117::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 5 nameservers #6
    Delegated to a1-247.akam.net, a11-64.akam.net, a20-65.akam.net, a28-66.akam.net, a6-67.akam.net.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: a9-64.akam.net. a1-247.akam.net, a11-64.akam.net, a20-65.akam.net, a28-66.akam.net, a6-67.akam.net, a9-64.akam.net report NS a1-247.akam.net a11-64.akam.net a20-65.akam.net a28-66.akam.net a6-67.akam.net a9-64.akam.net.
    #7
  • ✓ 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 6 IPv4 /24s and 6 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 12 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 .net
    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

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-247.akam.net 193.108.91.247NOERROR, 4 ms, authoritativenoyes / yesrefused41824.7
a1-247.akam.net 2600:1401:2::f7NOERROR, 4 ms, authoritativenoyes / yesrefused41824.7
a11-64.akam.net 84.53.139.64NOERROR, 4 ms, authoritativenoyes / yesrefused41824.6
a11-64.akam.net 2600:1480:1::40NOERROR, 4 ms, authoritativenoyes / yesrefused41824.6
a20-65.akam.net 95.100.175.65NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
a20-65.akam.net 2a02:26f0:67::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.27
a28-66.akam.net 95.100.173.66NOERROR, 3 ms, authoritativenoyes / yesrefused48878.31
a28-66.akam.net 2600:1480:d800::42NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a6-67.akam.net 23.211.133.67NOERROR, 4 ms, authoritativenoyes / yesrefused48878.26
a6-67.akam.net 2600:1401:1::43NOERROR, 4 ms, authoritativenoyes / yesrefused48878.26
a9-64.akam.net 184.85.248.64NOERROR, 4 ms, authoritativenoyes / yesrefused41824.4
a9-64.akam.net 2a02:26f0:117::40NOERROR, 4 ms, authoritativenoyes / yesrefused41824.10

Checks

  • ✓ All respond #14
    All 12 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: a1-247.akam.net: "41824.7"; a11-64.akam.net: "41824.6"; a20-65.akam.net: "48878.29"; a20-65.akam.net: "48878.27"; a28-66.akam.net: "48878.31"; a6-67.akam.net: "48878.26"; a9-64.akam.net: "41824.4"; a9-64.akam.net: "41824.10". 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

pass

serial 2020031022 · primary a1-247.akam.net

Found

Primary (MNAME)
a1-247.akam.net
Contact (RNAME)
hostmaster.rbfa.be
Serial
2020031022
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
40000 s

Serial per nameserver

NameserverSerial
a1-247.akam.net (193.108.91.247)2020031022
a1-247.akam.net (2600:1401:2::f7)2020031022
a11-64.akam.net (84.53.139.64)2020031022
a11-64.akam.net (2600:1480:1::40)2020031022
a20-65.akam.net (95.100.175.65)2020031022
a20-65.akam.net (2a02:26f0:67::41)2020031022
a28-66.akam.net (95.100.173.66)2020031022
a28-66.akam.net (2600:1480:d800::42)2020031022
a6-67.akam.net (23.211.133.67)2020031022
a6-67.akam.net (2600:1401:1::43)2020031022
a9-64.akam.net (184.85.248.64)2020031022
a9-64.akam.net (2a02:26f0:117::40)2020031022

Checks

  • ✓ Serial 2020031022 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 11h6m40s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a1-247.akam.net is one of the listed nameservers.
  • ✓ Contact hostmaster@rbfa.be #25
    The SOA RNAME hostmaster.rbfa.be means hostmaster@rbfa.be.
  • ✓ Date-based serial #26
    The serial 2020031022 follows the YYYYMMDDnn convention (2020-03-10).

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

warn

23 records at the apex

Found

Read from
193.108.91.247:53
TypeValueTTL
SOAa1-247.akam.net. hostmaster.rbfa.be. 2020031022 10800 3600 604800 400003600
NSa9-64.akam.net.3600
NSa11-64.akam.net.3600
NSa20-65.akam.net.3600
NSa28-66.akam.net.3600
NSa1-247.akam.net.3600
NSa6-67.akam.net.3600
A2.16.204.8720
A2.16.204.7220
AAAA2a02:26f0:b700:5::210:cc0c20
AAAA2a02:26f0:b700:5::210:cc1b20
MX0 rbfa-be.mail.protection.outlook.com.3600
TXT"facebook-domain-verification=wq8zmvpcdg9sedhglavwy07pl08hfb"300
TXT"v=spf1" " ip4:18.156.0.20" " ip4:3.74.126.139" " ip4:3.72.196.143" " ip4:3.212.20.253" " ip4:40.92.0.0/15" " ip4:50.31.57.204" " ip4:195.238.5.72" " ip4:54.240.0.0/18" " ip4:52.202.71.114" " ip4:54.145.52.119" " ip4:34.225.87.138" " ip4:40.107.0.0/16" " ip4:52.100.0.0/14" " ip4:104.47.0.0/17" " ip4:185.139.44.14" " ip4:206.17.168.28" " ip4:213.181.53.221" " ip4:213.181.53.220" " ip4:54.240.64.0/19" " ip4:54.240.96.0/19" " include:_spf2.rbfa.be" " ~all"300
TXT"google-site-verification=uxf39t0Zq3u7D3XmEjRtXXlQdfvwJ0bRNT7ZnNKgoCE"300
TXT"ica6k67eia69uoomrbr1bodu3s"300
TXT"anthropic-domain-verification-m1kfah=Fc9tLfSKHmcFnTdLm15oDOiaa"300
TXT"ms69388241.msv1.invalid"300
TXT"google-site-verification=V58297F_JVmqZ-1vgfUYOsXNfNtyKSQMKOolulbk7fU"300
TXT"hes=681186686753d85251cc7f6084b60764"300
TXT"google-site-verification=V6lTTYz-v8iBucesSKoHawqt8elUKdVW3pTHZv_S44w"300
TXT"vnhmmlbr4jdeqdrmo7740a0mbe"300
TXT"MS=ms69388241"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32
  • ✓ 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