zoutleeuw.be

Checked 22 October 2026, 07:31 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 warnings 0 failed 6 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

lcpnos1.corp.lcpnet.com, ns3.corp.lcpnet.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
lcpnos1.corp.lcpnet.com, ns3.corp.lcpnet.com
NS in the zone
lcpnos1.corp.lcpnet.com, ns3.corp.lcpnet.com
NameserverAddressesNetwork (AS)Glue
lcpnos1.corp.lcpnet.com193.110.252.72 2a02:5940:4001::2AS42160 LCPDCO - DC STAR nv, BE AS42160 LCPDCO - DC STAR nv, BE-
ns3.corp.lcpnet.com81.82.216.58 2a02:1807:2704:8c80::2AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: lcpnos1.corp.lcpnet.com, ns3.corp.lcpnet.com.
    #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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS42160 (LCPDCO - DC STAR nv, BE): 2 addresses; AS6848 (TELENET-AS - Telenet BV, BE): 2 addresses.
  • i
    All nameserver names under .com
    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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
lcpnos1.corp.lcpnet.com 193.110.252.72NOERROR, 15 ms, authoritativenoyes / yesrefused-
lcpnos1.corp.lcpnet.com 2a02:5940:4001::2NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns3.corp.lcpnet.com 81.82.216.58NOERROR, 38 ms, authoritativenoyes / yesrefused-
ns3.corp.lcpnet.com 2a02:1807:2704:8c80::2NOERROR, 47 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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 2026100304 · primary lcpnos1.corp.lcpnet.com

Found

Primary (MNAME)
lcpnos1.corp.lcpnet.com
Contact (RNAME)
hostmaster.corp.lcpnet.com
Serial
2026100304
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
lcpnos1.corp.lcpnet.com (193.110.252.72)2026100304
lcpnos1.corp.lcpnet.com (2a02:5940:4001::2)2026100304
ns3.corp.lcpnet.com (81.82.216.58)2026100304
ns3.corp.lcpnet.com (2a02:1807:2704:8c80::2)2026100304

Checks

  • ✓ Serial 2026100304 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver lcpnos1.corp.lcpnet.com is one of the listed nameservers.
  • ✓ Contact hostmaster@corp.lcpnet.com #25
    The SOA RNAME hostmaster.corp.lcpnet.com means hostmaster@corp.lcpnet.com.
  • ✓ Date-based serial #26
    The serial 2026100304 follows the YYYYMMDDnn convention (2026-10-03).

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
24744ECDSAP256SHA256 (13)SHA256 F8D17914A765C737…yes

DNSKEY in the zone

Key tagRoleAlgorithm
24744KSK (257)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 24744 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 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

8 records at the apex

Found

Read from
193.110.252.72:53
TypeValueTTL
SOAlcpnos1.corp.lcpnet.com. hostmaster.corp.lcpnet.com. 2026100304 10800 3600 604800 36003600
NSns3.corp.lcpnet.com.3600
NSlcpnos1.corp.lcpnet.com.3600
A193.110.252.82900
AAAA2a02:5940:4001::113600
MX0 zoutleeuw-be.mail.protection.outlook.com.3600
TXT"_globalsign-domain-verification=-v5lGogkTp9_33KA9JTyksK97oK9HgMadyNR5tCDAj"3600
TXT"v=spf1 include:spf.protection.outlook.com ip4:78.24.172.225 ip4:78.24.168.37 include:spf.lcp.be include:_spf.bibliotheek.be include:spf.ciport.be -all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, AAAA 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