immaterieelerfgoed.be

Checked 22 October 2026, 06:40 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

warn

ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com
NS in the zone
ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be
NameserverAddressesNetwork (AS)Glue
ns.be.hostbasket.com (parent only)85.255.200.200 2a01:498:8301:1c0::200AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-
ns.fr.hostbasket.com (parent only)185.35.52.200 2a01:498:8501:4090::6:1AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-
ns.nl.hostbasket.com (parent only)195.130.154.74 2a01:498:8101:4c0::200AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-
ns1.cloud.telenet.be (zone only)85.255.200.200 2a01:498:8301:1c0::200AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-
ns2.cloud.telenet.be (zone only)195.130.154.74 2a01:498:8101:4c0::200AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-
ns3.cloud.telenet.be (zone only)185.35.52.200 2a01:498:8501:4090::6:1AS6848 TELENET-AS - Telenet BV, BE AS6848 TELENET-AS - Telenet BV, BE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com; only in the zone: ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be. ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com, ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be report NS ns1.cloud.telenet.be ns2.cloud.telenet.be ns3.cloud.telenet.be.
    #7
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS6848 (TELENET-AS - Telenet BV, BE): 12 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 .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

info

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.be.hostbasket.com 85.255.200.200NOERROR, 19 ms, authoritativenoyes / yesrefused<HIDDEN>
ns.be.hostbasket.com 2a01:498:8301:1c0::200NOERROR, 15 ms, authoritativenoyes / yesrefused<HIDDEN>
ns.fr.hostbasket.com 185.35.52.200NOERROR, 19 ms, authoritativenoyes / yesrefused<HIDDEN>
ns.fr.hostbasket.com 2a01:498:8501:4090::6:1NOERROR, 15 ms, authoritativenoyes / yesrefused<HIDDEN>
ns.nl.hostbasket.com 195.130.154.74NOERROR, 25 ms, authoritativenoyes / yesrefused<HIDDEN>
ns.nl.hostbasket.com 2a01:498:8101:4c0::200NOERROR, 13 ms, authoritativenoyes / yesrefused<HIDDEN>
ns1.cloud.telenet.be 85.255.200.200NOERROR, 19 ms, authoritativenoyes / yesrefused<HIDDEN>
ns1.cloud.telenet.be 2a01:498:8301:1c0::200NOERROR, 13 ms, authoritativenoyes / yesrefused<HIDDEN>
ns2.cloud.telenet.be 195.130.154.74NOERROR, 24 ms, authoritativenoyes / yesrefused<HIDDEN>
ns2.cloud.telenet.be 2a01:498:8101:4c0::200NOERROR, 13 ms, authoritativenoyes / yesrefused<HIDDEN>
ns3.cloud.telenet.be 185.35.52.200NOERROR, 18 ms, authoritativenoyes / yesrefused<HIDDEN>
ns3.cloud.telenet.be 2a01:498:8501:4090::6:1NOERROR, 15 ms, authoritativenoyes / yesrefused<HIDDEN>

Checks

  • ✓ All respond #14
    All 12 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.be.hostbasket.com: "<HIDDEN>"; ns.fr.hostbasket.com: "<HIDDEN>"; ns.nl.hostbasket.com: "<HIDDEN>"; ns1.cloud.telenet.be: "<HIDDEN>"; ns2.cloud.telenet.be: "<HIDDEN>"; ns3.cloud.telenet.be: "<HIDDEN>".
    #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

pass

serial 1786348138 · primary ns1.cloud.telenet.be

Found

Primary (MNAME)
ns1.cloud.telenet.be
Contact (RNAME)
postmaster.immaterieelerfgoed.be
Serial
1786348138
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns.be.hostbasket.com (85.255.200.200)1786348138
ns.be.hostbasket.com (2a01:498:8301:1c0::200)1786348138
ns.fr.hostbasket.com (185.35.52.200)1786348138
ns.fr.hostbasket.com (2a01:498:8501:4090::6:1)1786348138
ns.nl.hostbasket.com (195.130.154.74)1786348138
ns.nl.hostbasket.com (2a01:498:8101:4c0::200)1786348138
ns1.cloud.telenet.be (85.255.200.200)1786348138
ns1.cloud.telenet.be (2a01:498:8301:1c0::200)1786348138
ns2.cloud.telenet.be (195.130.154.74)1786348138
ns2.cloud.telenet.be (2a01:498:8101:4c0::200)1786348138
ns3.cloud.telenet.be (185.35.52.200)1786348138
ns3.cloud.telenet.be (2a01:498:8501:4090::6:1)1786348138

Checks

  • ✓ Serial 1786348138 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 1000h, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.cloud.telenet.be is one of the listed nameservers.
  • ✓ Contact postmaster@immaterieelerfgoed.be #25
    The SOA RNAME postmaster.immaterieelerfgoed.be means postmaster@immaterieelerfgoed.be.
  • ✓ Timestamp serial #26
    The serial 1786348138 is a Unix timestamp (2026-08-10 07:48 UTC).

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

12 records at the apex

Found

Read from
85.255.200.200:53
TypeValueTTL
SOAns1.cloud.telenet.be. postmaster.immaterieelerfgoed.be. 1786348138 86400 7200 3600000 90086400
NSns3.cloud.telenet.be.86400
NSns2.cloud.telenet.be.86400
NSns1.cloud.telenet.be.86400
A188.208.37.20186400
AAAA2a00:1c98:1000:12f4:0:4:491f:69c286400
MX10 alt4.aspmx.l.google.com.86400
MX5 alt2.aspmx.l.google.com.86400
MX5 alt1.aspmx.l.google.com.86400
MX1 aspmx.l.google.com.86400
MX10 alt3.aspmx.l.google.com.86400
TXT"v=spf1 include:_mail.level27.eu include:_spf.createsend.com include:_spf.google.com ?all"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, AAAA 1d, MX 1d, NS 1d.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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