uzgent.be

Checked 22 October 2026, 07:21 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 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

ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, uzg22.uzgent.be, uzg44.uzgent.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, uzg22.uzgent.be, uzg44.uzgent.be
NS in the zone
ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, uzg11.uzgent.be, uzg22.uzgent.be, uzg44.uzgent.be
NameserverAddressesNetwork (AS)Glue
ns1.belnet.be193.190.198.14 2001:6a8:3c80::14AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE193.190.198.14 2001:6a8:3c80::14
ns2.belnet.be193.190.182.40 2001:6a8:3c80:c000::40AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE193.190.182.40 2001:6a8:3c80:c000::40
ns3.belnet.be194.58.196.32 2a01:3f1:832::53AS8674 NETNOD-IX - Netnod AB, SE AS8674 NETNOD-IX - Netnod AB, SE194.58.196.32 2a01:3f1:832::53
uzg11.uzgent.be (zone only)193.191.170.50AS2611 BELNET - BELNET, BE-
uzg22.uzgent.be193.191.170.51AS2611 BELNET - BELNET, BE193.191.170.51
uzg44.uzgent.be54.38.184.94AS16276 OVH - OVH SAS, FR54.38.184.94

Checks

  • ✓ 5 nameservers #6
    Delegated to ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, uzg22.uzgent.be, uzg44.uzgent.be.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: uzg11.uzgent.be. ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, uzg11.uzgent.be, uzg22.uzgent.be, uzg44.uzgent.be report NS ns1.belnet.be ns2.belnet.be ns3.belnet.be uzg11.uzgent.be uzg22.uzgent.be uzg44.uzgent.be.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: uzg22.uzgent.be, uzg44.uzgent.be.
  • ✓ 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 5 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 1 address; AS2611 (BELNET - BELNET, BE): 6 addresses; AS8674 (NETNOD-IX - Netnod AB, SE): 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: uzg11.uzgent.be, uzg22.uzgent.be, uzg44.uzgent.be.
    #13

Nameservers

info

9 of 9 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.belnet.be 193.190.198.14NOERROR, 17 ms, authoritativenoyes / yesrefusedFor me to know, for you to guess!
ns1.belnet.be 2001:6a8:3c80::14NOERROR, 13 ms, authoritativenoyes / yesrefusedFor me to know, for you to guess!
ns2.belnet.be 193.190.182.40NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.belnet.be 2001:6a8:3c80:c000::40NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns3.belnet.be 194.58.196.32NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns3.belnet.be 2a01:3f1:832::53NOERROR, 9 ms, authoritativenoyes / yesrefused-
uzg11.uzgent.be 193.191.170.50NOERROR, 19 ms, authoritativenoyes / yesrefused-
uzg22.uzgent.be 193.191.170.51NOERROR, 19 ms, authoritativenoyes / yesrefused-
uzg44.uzgent.be 54.38.184.94NOERROR, 7 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 9 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: ns1.belnet.be: "For me to know, for you to guess!".
    #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

warn

serial 2026103163 · primary uzg11.uzgent.be

Found

Primary (MNAME)
uzg11.uzgent.be
Contact (RNAME)
root.uzg11.uzgent.be
Serial
2026103163
Refresh / retry
3600 s / 600 s
Expire
3600000 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns1.belnet.be (193.190.198.14)2026103163
ns1.belnet.be (2001:6a8:3c80::14)2026103163
ns2.belnet.be (193.190.182.40)2026103163
ns2.belnet.be (2001:6a8:3c80:c000::40)2026103163
ns3.belnet.be (194.58.196.32)2026103163
ns3.belnet.be (2a01:3f1:832::53)2026103163
uzg11.uzgent.be (193.191.170.50)2026103163
uzg22.uzgent.be (193.191.170.51)2026103163
uzg44.uzgent.be (54.38.184.94)2026103163

Checks

  • ✓ Serial 2026103163 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 1000h, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver uzg11.uzgent.be is one of the listed nameservers.
  • ✓ Contact root@uzg11.uzgent.be #25
    The SOA RNAME root.uzg11.uzgent.be means root@uzg11.uzgent.be.
  • !
    Serial date in the future
    The serial 2026103163 looks like a date (YYYYMMDDnn) in the future (2026-10-31). It can only grow, so a wrong date can't be undone without a serial wrap-around.
    #26

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
26959RSASHA256 (8)SHA256 AAA9BC28EDF781E4…yes
65124RSASHA256 (8)SHA256 A1494ABA04246BC4…yes

DNSKEY in the zone

Key tagRoleAlgorithm
26959KSK (257)RSASHA256 (8)
65124ZSK (256)RSASHA256 (8)

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 26959 (SHA256), key tag 65124 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-20 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-20 16:23 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

warn

24 records at the apex

Found

Read from
193.190.198.14:53
TypeValueTTL
SOAuzg11.uzgent.be. root.uzg11.uzgent.be. 2026103163 3600 600 3600000 72007200
NSuzg22.uzgent.be.7200
NSns2.belnet.be.7200
NSns3.belnet.be.7200
NSns1.belnet.be.7200
NSuzg11.uzgent.be.7200
NSuzg44.uzgent.be.7200
A194.32.154.517200
MX10 mail9.uzgent.be.99
MX20 mail10.uzgent.be.99
TXT"facebook-domain-verification=iz968p0o68qgcgbv7qzqs0h5se1l2v"7200
TXT"google-site-verification=GTFn1aVWB1G8NoDZYz9zFEb-cXK5_kY2wYOPmGUKWZk"7200
TXT"ZOOM_verify_xeSCoPIYvNxSlNBBhPVxgk"7200
TXT"google-gws-recovery-domain-verification=60435562"7200
TXT"rNy4UTXZfg91iFo8eQf9LIX5dbmzfbi2H/fBlimQuQXtb2SBOvXvtjZJRLPxx2xfWqbo1nfFcjCEhwYUVMurHg=="7200
TXT"apple-domain-verification=A1Zt0hWit7MvbdHV"7200
TXT"Zs6GMa/gdncECn4HTOkB1qfsmwU7B1y/Qg1PEslLTIU="7200
TXT"successfactors-site-verification=YjdjODY3N2M5YzdlZjBkZjMzYjdhZjI3ZmY1OGMyODc2MDU0NDViYjIwZmEzY2RlZjA5Y2QyNzhlZWY4ZWZmNg=="7200
TXT"v=spf1 mx a ip4:193.191.170.50 ip4:193.191.170.51 ip4:193.191.170.55 ip4:193.191.170.52 ip4:193.191.170.54 ip4:193.191.170.59 ip4:193.191.170.104 ip4:193.191.170.66 ip4:193.191.170.67 ip4:193.191.170.68 ip4:193.191.170.69 -all"7200
TXT"have-i-been-pwned-verification=dweb_cb36rp18usj94j823sqzrhdc"7200
TXT"google-site-verification=TdcrjuOS-67pCUzAJ7IR5H_yBEGsHgqTcvbga0CArMg"7200
TXT"google-site-verification=I3309ywUHGzWQcIYhS-xHsL6is1UaS2X8C78ZXLDxb8"7200
TXT"google-site-verification=ThRulYIQgcE1SRkB0tb-MODuf_w0kNWnOZmrxlqTTes"7200
TXT"MS=ms70534125"7200

Checks

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