uvcw.be

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

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.thgnet.net, ns2.thgnet.net
NS in the zone
ns1.thgnet.net, ns2.thgnet.net
NameserverAddressesNetwork (AS)Glue
ns1.thgnet.net193.105.73.7AS6696 VERIXI - VERIXI SA, BE-
ns2.thgnet.net85.234.212.22AS9031 EDPNETapp - EDPNET Belgium BV, BE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.thgnet.net, ns2.thgnet.net.
    #6
  • ✓ 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 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS6696 (VERIXI - VERIXI SA, BE): 1 address; AS9031 (EDPNETapp - EDPNET Belgium BV, BE): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.thgnet.net 193.105.73.7NOERROR, 17 ms, authoritativenoyes / yesrefused9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.9
ns2.thgnet.net 85.234.212.22NOERROR, 13 ms, authoritativenoyes / yesrefused9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.thgnet.net: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.9"; ns2.thgnet.net: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16". 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

warn

serial 2026100502 · primary ns1.thgnet.net

Found

Primary (MNAME)
ns1.thgnet.net
Contact (RNAME)
hostmaster.uvcw.be
Serial
2026100502
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.thgnet.net (193.105.73.7)2026100502
ns2.thgnet.net (85.234.212.22)2026100502

Checks

  • ✓ Serial 2026100502 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.thgnet.net is one of the listed nameservers.
  • ✓ Contact hostmaster@uvcw.be #25
    The SOA RNAME hostmaster.uvcw.be means hostmaster@uvcw.be.
  • ✓ Date-based serial #26
    The serial 2026100502 follows the YYYYMMDDnn convention (2026-10-05).

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

18 records at the apex

Found

Read from
193.105.73.7:53
TypeValueTTL
SOAns1.thgnet.net. hostmaster.uvcw.be. 2026100502 3600 3600 1209600 864003600
NSns2.thgnet.net.180
NSns1.thgnet.net.180
A193.138.101.120180
MX20 uvcw-be-2.fortimailcloud.com.180
MX10 uvcw-be-1.fortimailcloud.com.180
TXT"cisco-ci-domain-verification=5c0d6c9099a6b05a42448b199b957f2df6b9a6d0ee38a16553fb378a69b2f97b"180
TXT"google-site-verification=UBHOWMVBJKVB5TK5OvX9MRR9-LStsiZ_VcYhdlu-Ato"180
TXT"mistral-domain-verification=2b943b2585859001640f5009ed248e654f1df5cd"180
TXT"v=spf1 mx ip4:212.166.46.11 ip4:91.183.114.104 ip4:81.241.226.123 ip4:188.118.33.54 ip4:188.118.27.30 ip4:146.59.239.175 ip4:51.178.114.169 ip4:135.1" "25.57.155 ip4:217.182.163.140 ip4:57.128.7.27 a:gw000040-eu.fortimail.com include:spf.protection.outlook.com include:spf.oximailing.com include:relayc" "loud1.dgnus.net include:ispmail.spf.secure-mail.be include:_spf.fortimailcloud.com -all"180
TXT"MS=ms69208197"180
TXT"MS=ms40081347"180
CAA0 issue "letsencrypt.org"180
CAA0 issue "sectigo.com"180
CAA0 issue "amazon.com"180
CAA0 issue "trustprovider.com"180
CAA0 issue "digicert.com"180
CAA0 iodef "mailto:security@uvcw.be"180

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (3m), MX (3m), NS (3m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 3m; 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.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, sectigo.com, amazon.com, trustprovider.com, digicert.com.