zwevegem.be

Checked 22 October 2026, 07:31 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 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

info

ns.zwevegem.be, ns1.belnet.be, ns2.belnet.be, ns3.belnet.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns.zwevegem.be, ns1.belnet.be, ns2.belnet.be, ns3.belnet.be
NS in the zone
ns.zwevegem.be, ns1.belnet.be, ns2.belnet.be, ns3.belnet.be
NameserverAddressesNetwork (AS)Glue
ns.zwevegem.be193.191.178.94AS2611 BELNET - BELNET, BE193.191.178.94
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

Checks

  • ✓ 4 nameservers #6
    Delegated to ns.zwevegem.be, ns1.belnet.be, ns2.belnet.be, ns3.belnet.be.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns.zwevegem.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 4 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS2611 (BELNET - BELNET, BE): 5 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: ns.zwevegem.be.
    #13

Nameservers

info

7 of 7 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.zwevegem.be 193.191.178.94NOERROR, 25 ms, authoritativenoyes / yesrefused-
ns1.belnet.be 193.190.198.14NOERROR, 18 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, 17 ms, authoritativenoyes / yesrefused-
ns3.belnet.be 194.58.196.32NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns3.belnet.be 2a01:3f1:832::53NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 7 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 2026100607 · primary gmpdmz02.perimeter.local

Found

Primary (MNAME)
gmpdmz02.perimeter.local
Contact (RNAME)
hostmaster.zwevegem.be
Serial
2026100607
Refresh / retry
900 s / 600 s
Expire
7200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.zwevegem.be (193.191.178.94)2026100607
ns1.belnet.be (193.190.198.14)2026100607
ns1.belnet.be (2001:6a8:3c80::14)2026100607
ns2.belnet.be (193.190.182.40)2026100607
ns2.belnet.be (2001:6a8:3c80:c000::40)2026100607
ns3.belnet.be (194.58.196.32)2026100607
ns3.belnet.be (2a01:3f1:832::53)2026100607

Checks

  • ✓ Serial 2026100607 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; expire 2h is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 15m, retry 10m, expire 2h, negative TTL 1h.
    #23
  • i
    Hidden master (not resolvable)
    The primary nameserver gmpdmz02.perimeter.local is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact hostmaster@zwevegem.be #25
    The SOA RNAME hostmaster.zwevegem.be means hostmaster@zwevegem.be.
  • ✓ Date-based serial #26
    The serial 2026100607 follows the YYYYMMDDnn convention (2026-10-06).

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

info

18 records at the apex

Found

Read from
193.191.178.94:53
TypeValueTTL
SOAgmpdmz02.perimeter.local. hostmaster.zwevegem.be. 2026100607 900 600 7200 36003600
NSns3.belnet.be.3600
NSns.zwevegem.be.3600
NSns2.belnet.be.3600
NSns1.belnet.be.3600
A94.176.99.1403600
A94.176.99.1423600
MX10 zwevegem-be.mail.protection.outlook.com.3600
TXT"kcrl2pbm9tx7n9hsdvfdkrbr7lq4lhwb"3600
TXT"google-site-verification=ceQPHVf63_Es-1a5Mn9YxNZkA89St4wloE93hun0cN18"3600
TXT"fc375535874042a98b560ada815c54e3"3600
TXT"HARICA-mXGU0FaPVSNB3DTyNE7"3600
TXT"v=spf1 include:_spf1.zwevegem.be include:_spf2.zwevegem.be -all" ""3600
TXT"adobe-idp-site-verification=97dde569fcba8d374a0355bed46e77c908a9e4970bfa07773e3d194abe43e7cd"3600
TXT"apple-domain-verification=1pNATyqbjJFUjlij"3600
TXT"brevo-code:3ff469f7d4862443a10fe4fd47070b3c"3600
TXT"X6wkATzHz+AN1XR3Ps2lj+Aq7E2UWtqyzlv4q80KSERsoLJCuwvTKWukx7tu69ofZi7hxB7Kn23oxN0oWll/yg=="3600
TXT"facebook-domain-verification=lyz2u8rztgbe4y47n4js1ljhnx5g92"3600

Checks

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