uza.be

Checked 22 October 2026, 07:21 UTC · via 8.8.8.8
✗Problems found
15 passed 6 warnings 1 failed 7 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

ns.uza.be, ns2.uza.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns.uza.be, ns2.uza.be
NS in the zone
ns.uza.be, ns2.uza.be
NameserverAddressesNetwork (AS)Glue
ns.uza.be193.190.131.96AS2611 BELNET - BELNET, BE193.190.131.96 2001:6a8:460:1149:ffff:ffff:ffff:1a01
ns2.uza.be193.190.131.109AS2611 BELNET - BELNET, BE193.190.131.109 2001:6a8:460:1149:ffff:ffff:ffff:1a02

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.uza.be, ns2.uza.be.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns.uza.be (glue 193.190.131.96, 2001:6a8:460:1149:ffff:ffff:ffff:1a01, zone 193.190.131.96); ns2.uza.be (glue 193.190.131.109, 2001:6a8:460:1149:ffff:ffff:ffff:1a02, zone 193.190.131.109). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 193.190.131.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS2611 (BELNET - BELNET, BE): 2 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 .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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.uza.be 193.190.131.96NOERROR, 18 ms, authoritativenoyes / yesALLOWED (325 records)0
ns2.uza.be 193.190.131.109NOERROR, 18 ms, authoritativenoyes / yesALLOWED (325 records)0

Checks

  • ✓ All respond #14
    All 2 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns.uza.be: "0"; ns2.uza.be: "0".
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns.uza.be (193.190.131.96): 325 records; ns2.uza.be (193.190.131.109): 325 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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

warn

serial 2026100701 · primary ns.uza.be

Found

Primary (MNAME)
ns.uza.be
Contact (RNAME)
hostmaster.uza.be
Serial
2026100701
Refresh / retry
3600 s / 3600 s
Expire
43200 s
Negative TTL
43200 s

Serial per nameserver

NameserverSerial
ns.uza.be (193.190.131.96)2026100701
ns2.uza.be (193.190.131.109)2026100701

Checks

  • ✓ Serial 2026100701 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h; expire 12h is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 1h, expire 12h, negative TTL 12h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.uza.be is one of the listed nameservers.
  • ✓ Contact hostmaster@uza.be #25
    The SOA RNAME hostmaster.uza.be means hostmaster@uza.be.
  • ✓ Date-based serial #26
    The serial 2026100701 follows the YYYYMMDDnn convention (2026-10-07).

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

24 records at the apex

Found

Read from
193.190.131.96:53
TypeValueTTL
SOAns.uza.be. hostmaster.uza.be. 2026100701 3600 3600 43200 4320060
NSns.uza.be.60
NSns2.uza.be.60
A151.101.67.5260
A151.101.3.5260
A151.101.195.5260
A151.101.131.5260
MX0 uza-be.mail.protection.outlook.com.60
TXT"tmes=51bdc205d8eb82d79a7a587ea94e932b"60
TXT"domain-verification:c9a93560a106929af31ee04b500b4c7cc50fbd51"60
TXT"spycloud-domain-verification=81892dc2-19b4-4a78-9d99-d1ed4fec9cfb"60
TXT"HARICA-lrVy7Q6lw6NN52Ntyuu"60
TXT"v=spf1 include:_spf.zivver.com ip4:193.190.131.64/26 ip4:143.169.236.0/24 include:spf.protection.outlook.com -all"60
TXT"domain-verification:66098058c1fa7311af9d3aacb53febdbda2f6979"60
TXT"MS=ms48951676"60
TXT"MS=8F3E492BE946321C535CBBB0DAA810D28DCB00FB"60
TXT"MS=ms19191267"60
TXT"hpe-greenlake-domain-verification=524f43487656686e736e48556145716c567844793156383773746b3659704656"60
TXT"google-site-verification=rOJ-W9kgkswc7IdiT1yAd29tXQQ2uf5mmGg_P5xeZF4"60
TXT"apple-domain-verification=FjJJ5v8wUt0wqtjO"60
TXT"google-site-verification=dfmNo3gSrR_uOasQWdqcBJVwg5JFp1tt283dQQbXW8M"60
TXT"atlassian-domain-verification=apNCvogu5HSVmvnUYVQYI6IWawXy/kWVIIIrm3Jf0/GnPCDbKTDgoc4qy6SfGAHx"60
TXT"cFwvtvGzgJ/2HT1yOiBSLZ6apjc39uDM64/kZwG9/MM="60
TXT"pexip-ms-tenant-domain-verification=baa08184-4799-49ec-b190-641ce832b63e"60

Checks

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