kaaitheater.be

Checked 22 October 2026, 06:41 UTC · via 8.8.8.8
✗Problems found
21 passed 2 warnings 1 failed 5 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.db-ops.net, ns2.db-ops.net, ns3.db-ops.net, ns4.db-ops.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.db-ops.net, ns2.db-ops.net, ns3.db-ops.net, ns4.db-ops.net
NS in the zone
ns1.db-ops.net, ns2.db-ops.net, ns4.db-ops.net
NameserverAddressesNetwork (AS)Glue
ns1.db-ops.net176.9.34.18 2a01:4f8:150:4008::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.db-ops.net94.237.41.39 2a04:3544:1000:1510:432:ff:fe79:5b36AS202053 UPCLOUD - UpCloud Ltd, FI AS202053 UPCLOUD - UpCloud Ltd, FI-
ns3.db-ops.net (parent only)85.215.114.34AS8560 IONOS-AS - IONOS SE, DE-
ns4.db-ops.net194.42.75.194AS3257 GTT-BACKBONE - GTT Communications Inc., US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.db-ops.net, ns2.db-ops.net, ns3.db-ops.net, ns4.db-ops.net.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns3.db-ops.net. ns1.db-ops.net, ns2.db-ops.net, ns3.db-ops.net, ns4.db-ops.net report NS ns1.db-ops.net ns2.db-ops.net ns4.db-ops.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 4 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS202053 (UPCLOUD - UpCloud Ltd, FI): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS3257 (GTT-BACKBONE - GTT Communications Inc., US): 1 address; AS8560 (IONOS-AS - IONOS SE, DE): 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns3.db-ops.net, ns4.db-ops.net.
    #13

Nameservers

fail

5 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.db-ops.net 176.9.34.18NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns1.db-ops.net 2a01:4f8:150:4008::1NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns2.db-ops.net 94.237.41.39NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.db-ops.net 2a04:3544:1000:1510:432:ff:fe79:5b36no responsenono / no--
ns3.db-ops.net 85.215.114.34NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns4.db-ops.net 194.42.75.194NOERROR, 14 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns2.db-ops.net (2a04:3544:1000:1510:432:ff:fe79:5b36): read udp [2a01:4f8:1c1c:eebf::1]:50707->[2a04:3544:1000:1510:432:ff:fe79:5b36]:53: read: connection refused.
    #14
  • ✓ 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 2019021082 · primary ns1.db-ops.net

Found

Primary (MNAME)
ns1.db-ops.net
Contact (RNAME)
dns.db-ops.net
Serial
2019021082
Refresh / retry
10800 s / 1800 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.db-ops.net (176.9.34.18)2019021082
ns1.db-ops.net (2a01:4f8:150:4008::1)2019021082
ns2.db-ops.net (94.237.41.39)2019021082
ns3.db-ops.net (85.215.114.34)2019021082
ns4.db-ops.net (194.42.75.194)2019021082

Checks

  • ✓ Serial 2019021082 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.db-ops.net is one of the listed nameservers.
  • ✓ Contact dns@db-ops.net #25
    The SOA RNAME dns.db-ops.net means dns@db-ops.net.
  • ✓ Date-based serial #26
    The serial 2019021082 follows the YYYYMMDDnn convention (2019-02-10).

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

10 records at the apex

Found

Read from
176.9.34.18:53
TypeValueTTL
SOAns1.db-ops.net. dns.db-ops.net. 2019021082 10800 1800 604800 3003600
NSns4.db-ops.net.86400
NSns1.db-ops.net.86400
NSns2.db-ops.net.86400
A91.214.189.218300
MX0 kaaitheater-be.mail.protection.outlook.com.300
TXT"google-site-verification=KsFKrlikiHXnnq-pvnmHiWdo3r-O7HWEHYDcVQutnVI"300
TXT"v=spf1 a mx ip4:62.148.163.33 include:spf.protection.outlook.com include:spf.mtasv.net include:spf.mailjet.com -all"300
TXT"apple-domain-verification=YGLdvuZNWVDV9Rws"300
TXT"MS=ms22432706"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 1d.
  • ✓ 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