vab.be

Checked 22 October 2026, 07:21 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-248.akam.net, a11-66.akam.net, a16-65.akam.net, a2-64.akam.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
a1-248.akam.net, a11-66.akam.net, a16-65.akam.net, a2-64.akam.net
NS in the zone
a1-248.akam.net, a11-66.akam.net, a16-65.akam.net, a2-64.akam.net, a24-67.akam.net, a3-67.akam.net
NameserverAddressesNetwork (AS)Glue
a1-248.akam.net193.108.91.248 2600:1401:2::f8AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a11-66.akam.net84.53.139.66 2600:1480:1::42AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a16-65.akam.net23.211.132.65 2600:1406:1b::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a2-64.akam.net95.100.174.64 2600:1480:7000::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a24-67.akam.net (zone only)2.16.130.67 2600:1480:9800::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a3-67.akam.net (zone only)96.7.49.67 2600:1408:1c::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 4 nameservers #6
    Delegated to a1-248.akam.net, a11-66.akam.net, a16-65.akam.net, a2-64.akam.net.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: a24-67.akam.net, a3-67.akam.net. a1-248.akam.net, a11-66.akam.net, a16-65.akam.net, a2-64.akam.net, a24-67.akam.net, a3-67.akam.net report NS a1-248.akam.net a11-66.akam.net a16-65.akam.net a2-64.akam.net a24-67.akam.net a3-67.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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 2 addresses; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 10 addresses.
  • 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-248.akam.net 193.108.91.248NOERROR, 3 ms, authoritativenoyes / yesrefused41824.4
a1-248.akam.net 2600:1401:2::f8NOERROR, 4 ms, authoritativenoyes / yesrefused41824.5
a11-66.akam.net 84.53.139.66NOERROR, 3 ms, authoritativenoyes / yesrefused41824.11
a11-66.akam.net 2600:1480:1::42NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11
a16-65.akam.net 23.211.132.65NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a16-65.akam.net 2600:1406:1b::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a2-64.akam.net 95.100.174.64NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
a2-64.akam.net 2600:1480:7000::40NOERROR, 4 ms, authoritativenoyes / yesrefused48878.26
a24-67.akam.net 2.16.130.67NOERROR, 5 ms, authoritativenoyes / yesrefused48878.29
a24-67.akam.net 2600:1480:9800::43NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a3-67.akam.net 96.7.49.67NOERROR, 3 ms, authoritativenoyes / yesrefused41824.7
a3-67.akam.net 2600:1408:1c::43NOERROR, 4 ms, authoritativenoyes / yesrefused41824.7

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-248.akam.net: "41824.4"; a1-248.akam.net: "41824.5"; a11-66.akam.net: "41824.11"; a16-65.akam.net: "48878.31"; a2-64.akam.net: "48878.29"; a2-64.akam.net: "48878.26"; a24-67.akam.net: "48878.29"; a24-67.akam.net: "48878.31"; a3-67.akam.net: "41824.7". 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 2025051611 · primary a1-248.akam.net

Found

Primary (MNAME)
a1-248.akam.net
Contact (RNAME)
hostmaster.vab.be
Serial
2025051611
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
a1-248.akam.net (193.108.91.248)2025051611
a1-248.akam.net (2600:1401:2::f8)2025051611
a11-66.akam.net (84.53.139.66)2025051611
a11-66.akam.net (2600:1480:1::42)2025051611
a16-65.akam.net (23.211.132.65)2025051611
a16-65.akam.net (2600:1406:1b::41)2025051611
a2-64.akam.net (95.100.174.64)2025051611
a2-64.akam.net (2600:1480:7000::40)2025051611
a24-67.akam.net (2.16.130.67)2025051611
a24-67.akam.net (2600:1480:9800::43)2025051611
a3-67.akam.net (96.7.49.67)2025051611
a3-67.akam.net (2600:1408:1c::43)2025051611

Checks

  • ✓ Serial 2025051611 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a1-248.akam.net is one of the listed nameservers.
  • ✓ Contact hostmaster@vab.be #25
    The SOA RNAME hostmaster.vab.be means hostmaster@vab.be.
  • ✓ Date-based serial #26
    The serial 2025051611 follows the YYYYMMDDnn convention (2025-05-16).

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

28 records at the apex

Found

Read from
193.108.91.248:53
TypeValueTTL
SOAa1-248.akam.net. hostmaster.vab.be. 2025051611 3600 600 604800 300900
NSa24-67.akam.net.900
NSa16-65.akam.net.900
NSa11-66.akam.net.900
NSa1-248.akam.net.900
NSa3-67.akam.net.900
NSa2-64.akam.net.900
A2.16.204.2220
A2.16.204.520
AAAA2a02:26f0:b700:5::210:cc0520
AAAA2a02:26f0:b700:5::210:cc1620
MX0 vab-be.mail.protection.outlook.com.900
TXT"google-site-verification=TvJo1ShmYyZz_t9DkLMozgBmGnRjHF6aNhWV3NMVuwc"1800
TXT"atlassian-domain-verification=h/tKtBRSiuvGE0v3T1NDQ7PBJ/JR5JpJVxxq8ZaIU6948mFjRzJuDHoHrbwnsk9c"1800
TXT"atlassian-sending-domain-verification=18883cbb-dec7-4733-82f2-4038c0f01728"1800
TXT"spycloud-domain-verification=d7b7ed61-df43-4dd8-9f95-1a1e51664e52"1800
TXT"d365mktkey=faT2H9jkWmPyeBIxHHnxxMc09pkoENfscuq92os4d3wx"1800
TXT"_globalsign-domain-verification=oPsIKGmDXrkfrB6uEeqVF32wNOPxbJlbZSvXwOZu5X"1800
TXT"cc8cd97c9ea692056a7b6ab151d8d07a"1800
TXT"_globalsign-domain-verification=P556Xxj40PvTbksJOeAVz4RB3e1iGL87bBxJRg9LCY"1800
TXT"2NU2YzmDbET8SnyTdivCp/QsdFSvy/YiT4W0CTTyOA9kUNl6sIoJKKvyGyehEjgOD/2JkmanSsPBuBIyHgxjGg=="1800
TXT"miro-verification=169684d4d5eb11fe9c8eb1e708ac53a7c8090713"1800
TXT"d365mktkey=702yhgiww585l928a7mx7w2ws"1800
TXT"d365mktkey=Bu1AtAipc3OQmmv2NsoX1TmKkJGANFz3xLiUv17cAHgx"1800
TXT"bw=qKUCn1BZrRrdNmgXSV7Jl24gk3D2DUMyqUEUa5XSF52r"1800
TXT"v=spf1 ip4:84.199.66.5 ip4:84.199.66.14 ip4:185.56.145.25 a:mailout.hr-technologies.com include:spf.protection.outlook.com include:servers.mcsv.net include:spf.topdesk.net include:spf.totaalholding.nl include:spf.us.exclaimer.net -all"1800
TXT"google-site-verification=rM2vT4W3_um5k-WxzzcvZgkGH33IH-hrp-_lsP2glfs"1800
TXT"d365mktkey=4p4uwxr7av547errces4o695c"1800

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 15m; resolvers may use either.
    #32
  • ✓ 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