bnb.be

Checked 22 October 2026, 06:11 UTC · via 8.8.8.8
iAll checks passed
28 passed 0 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

info

ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info
NS in the zone
ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-03.azure-dns.com13.107.236.3 2603:1061:0:700::3AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2-03.azure-dns.net150.171.21.3 2620:1ec:8ec:700::3AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-03.azure-dns.org204.14.183.3 2a01:111:4000:700::3AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-03.azure-dns.info208.84.5.3 2620:1ec:bda:700::3AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-03.azure-dns.com 13.107.236.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-03.azure-dns.com 2603:1061:0:700::3NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-03.azure-dns.net 150.171.21.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-03.azure-dns.net 2620:1ec:8ec:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-03.azure-dns.org 204.14.183.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-03.azure-dns.org 2a01:111:4000:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-03.azure-dns.info 208.84.5.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-03.azure-dns.info 2620:1ec:bda:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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 1 · primary ns1-03.azure-dns.com

Found

Primary (MNAME)
ns1-03.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-03.azure-dns.com (13.107.236.3)1
ns1-03.azure-dns.com (2603:1061:0:700::3)1
ns2-03.azure-dns.net (150.171.21.3)1
ns2-03.azure-dns.net (2620:1ec:8ec:700::3)1
ns3-03.azure-dns.org (204.14.183.3)1
ns3-03.azure-dns.org (2a01:111:4000:700::3)1
ns4-03.azure-dns.info (208.84.5.3)1
ns4-03.azure-dns.info (2620:1ec:bda:700::3)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-03.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
23 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
29562ECDSAP256SHA256 (13)SHA256 9D6F1E4CA5D6411E…yes

DNSKEY in the zone

Key tagRoleAlgorithm
29562KSK (257)ECDSAP256SHA256 (13)
23679ZSK (256)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 29562 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 05:11 UTC and expires at 2026-10-23 07:11 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

7 records at the apex

Found

Read from
13.107.236.3:53
TypeValueTTL
SOAns1-03.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-03.azure-dns.com.172800
NSns2-03.azure-dns.net.172800
NSns3-03.azure-dns.org.172800
NSns4-03.azure-dns.info.172800
A185.3.217.1913600
A185.3.217.823600

Checks

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