kinepolis.be

Checked 22 October 2026, 06:41 UTC · via 8.8.8.8
!Passed with warnings
19 passed 4 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

warn

a1-67.akam.net, a13-66.akam.net, a24-67.akam.net, a4-67.akam.net, a5-66.akam.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
a1-67.akam.net, a13-66.akam.net, a24-67.akam.net, a4-67.akam.net, a5-66.akam.net
NS in the zone
a1-67.akam.net, a13-66.akam.net, a24-67.akam.net, a4-67.akam.net, a5-66.akam.net, a6-66.akam.net
NameserverAddressesNetwork (AS)Glue
a1-67.akam.net193.108.91.67 2600:1401:2::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a13-66.akam.net2.22.230.66 2600:1480:800::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a24-67.akam.net2.16.130.67 2600:1480:9800::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a4-67.akam.net72.246.46.67 2600:1480:9000::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a5-66.akam.net95.100.168.66 2600:1480:b000::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a6-66.akam.net (zone only)23.211.133.66 2600:1401:1::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 5 nameservers #6
    Delegated to a1-67.akam.net, a13-66.akam.net, a24-67.akam.net, a4-67.akam.net, a5-66.akam.net.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: a6-66.akam.net. a1-67.akam.net, a13-66.akam.net, a24-67.akam.net, a4-67.akam.net, a5-66.akam.net, a6-66.akam.net report NS a1-67.akam.net a13-66.akam.net a24-67.akam.net a4-67.akam.net a5-66.akam.net a6-66.akam.net.
    #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 6 IPv4 /24s and 6 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 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 .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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-67.akam.net 193.108.91.67NOERROR, 3 ms, authoritativenoyes / yesrefused41824.10
a1-67.akam.net 2600:1401:2::43NOERROR, 3 ms, authoritativenoyes / yesrefused41824.11
a13-66.akam.net 2.22.230.66NOERROR, 4 ms, authoritativenoyes / yesrefused41824.10
a13-66.akam.net 2600:1480:800::42NOERROR, 4 ms, authoritativenoyes / yesrefused41824.8
a24-67.akam.net 2.16.130.67NOERROR, 4 ms, authoritativenoyes / yesrefused48878.26
a24-67.akam.net 2600:1480:9800::43NOERROR, 4 ms, authoritativenoyes / yesrefused48878.26
a4-67.akam.net 72.246.46.67NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
a4-67.akam.net 2600:1480:9000::43NOERROR, 3 ms, authoritativenoyes / yesrefused48878.31
a5-66.akam.net 95.100.168.66NOERROR, 4 ms, authoritativenoyes / yesrefused41824.4
a5-66.akam.net 2600:1480:b000::42NOERROR, 4 ms, authoritativenoyes / yesrefused41824.9
a6-66.akam.net 23.211.133.66NOERROR, 4 ms, authoritativenoyes / yesrefused48878.32
a6-66.akam.net 2600:1401:1::42NOERROR, 3 ms, authoritativenoyes / yesrefused48878.29

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-67.akam.net: "41824.10"; a1-67.akam.net: "41824.11"; a13-66.akam.net: "41824.10"; a13-66.akam.net: "41824.8"; a24-67.akam.net: "48878.26"; a4-67.akam.net: "48878.29"; a4-67.akam.net: "48878.31"; a5-66.akam.net: "41824.4"; a5-66.akam.net: "41824.9"; a6-66.akam.net: "48878.32"; a6-66.akam.net: "48878.29". 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

pass

serial 2020042165 · primary a1-67.akam.net

Found

Primary (MNAME)
a1-67.akam.net
Contact (RNAME)
hostmaster.kinepolis.be
Serial
2020042165
Refresh / retry
43200 s / 3600 s
Expire
777600 s
Negative TTL
901 s

Serial per nameserver

NameserverSerial
a1-67.akam.net (193.108.91.67)2020042165
a1-67.akam.net (2600:1401:2::43)2020042165
a13-66.akam.net (2.22.230.66)2020042165
a13-66.akam.net (2600:1480:800::42)2020042165
a24-67.akam.net (2.16.130.67)2020042165
a24-67.akam.net (2600:1480:9800::43)2020042165
a4-67.akam.net (72.246.46.67)2020042165
a4-67.akam.net (2600:1480:9000::43)2020042165
a5-66.akam.net (95.100.168.66)2020042165
a5-66.akam.net (2600:1480:b000::42)2020042165
a6-66.akam.net (23.211.133.66)2020042165
a6-66.akam.net (2600:1401:1::42)2020042165

Checks

  • ✓ Serial 2020042165 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 1h, expire 9d, negative TTL 15m1s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a1-67.akam.net is one of the listed nameservers.
  • ✓ Contact hostmaster@kinepolis.be #25
    The SOA RNAME hostmaster.kinepolis.be means hostmaster@kinepolis.be.
  • ✓ Date-based serial #26
    The serial 2020042165 follows the YYYYMMDDnn convention (2020-04-21).

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

16 records at the apex

Found

Read from
193.108.91.67:53
TypeValueTTL
SOAa1-67.akam.net. hostmaster.kinepolis.be. 2020042165 43200 3600 777600 9013600
NSa13-66.akam.net.3600
NSa4-67.akam.net.3600
NSa5-66.akam.net.3600
NSa6-66.akam.net.3600
NSa24-67.akam.net.3600
NSa1-67.akam.net.3600
A2.23.176.15520
A2.23.176.17820
AAAA2a02:26f0:b700:14::215:6ec420
AAAA2a02:26f0:b700:14::215:6ecd20
MX0 kinepolis-be.mail.protection.outlook.com.901
TXT"facebook-domain-verification=m9vhapmy3n9eveh3f0j51d8vg70xev"901
TXT"google-site-verification=EjDsEiGTT085FBmoAvIIEmhX-O_W11lMiUNlAgoAe9U"901
TXT"v=spf1 include:kinepolis.com include:_spf.afasonline.nl -all"901
TXT"have-i-been-pwned-verification=399d476160eff4a7ca626c96e49fe15e"901

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32
  • ✓ 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