muhka.be

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

ns1.web14.unix-solutions.be, ns2.web14.unix-solutions.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.web14.unix-solutions.be, ns2.web14.unix-solutions.be
NS in the zone
ns1.web14.unix-solutions.be, ns2.web14.unix-solutions.be
NameserverAddressesNetwork (AS)Glue
ns1.web14.unix-solutions.be109.68.160.154 2a02:2a08:102::154AS39923 AS-UNIXSOLUTIONS - Unix-Solutions BV, BE AS39923 AS-UNIXSOLUTIONS - Unix-Solutions BV, BE-
ns2.web14.unix-solutions.be185.111.204.136 2a04:6480:101::136AS39923 AS-UNIXSOLUTIONS - Unix-Solutions BV, BE AS39923 AS-UNIXSOLUTIONS - Unix-Solutions BV, BE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.web14.unix-solutions.be, ns2.web14.unix-solutions.be.
    #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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS39923 (AS-UNIXSOLUTIONS - Unix-Solutions BV, BE): 4 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 .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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.web14.unix-solutions.be 109.68.160.154NOERROR, 13 ms, authoritativenoyes / yesrefused9.18.49-1~deb12u2-Debian
ns1.web14.unix-solutions.be 2a02:2a08:102::154NOERROR, 17 ms, authoritativenoyes / yesrefused9.18.49-1~deb12u2-Debian
ns2.web14.unix-solutions.be 185.111.204.136NOERROR, 13 ms, authoritativenoyes / yesrefused9.16.50-Debian
ns2.web14.unix-solutions.be 2a04:6480:101::136NOERROR, 13 ms, authoritativenoyes / yesrefused9.16.50-Debian

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.web14.unix-solutions.be: "9.18.49-1~deb12u2-Debian"; ns2.web14.unix-solutions.be: "9.16.50-Debian". 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

warn

serial 2026100600 · primary ns1.web14.unix-solutions.be

Found

Primary (MNAME)
ns1.web14.unix-solutions.be
Contact (RNAME)
hostmaster.muhka.be
Serial
2026100600
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.web14.unix-solutions.be (109.68.160.154)2026100600
ns1.web14.unix-solutions.be (2a02:2a08:102::154)2026100600
ns2.web14.unix-solutions.be (185.111.204.136)2026100600
ns2.web14.unix-solutions.be (2a04:6480:101::136)2026100600

Checks

  • ✓ Serial 2026100600 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.web14.unix-solutions.be is one of the listed nameservers.
  • ✓ Contact hostmaster@muhka.be #25
    The SOA RNAME hostmaster.muhka.be means hostmaster@muhka.be.
  • ✓ Date-based serial #26
    The serial 2026100600 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

10 records at the apex

Found

Read from
109.68.160.154:53
TypeValueTTL
SOAns1.web14.unix-solutions.be. hostmaster.muhka.be. 2026100600 3600 3600 1209600 864003600
NSns2.web14.unix-solutions.be.3600
NSns1.web14.unix-solutions.be.3600
A35.186.253.1453600
AAAA2600:1901:0:3ff::3600
MX0 muhka-be.mail.protection.outlook.com.3600
TXT"facebook-domain-verification=wuzhbcjssoffba87k3sltjai0hvojm"3600
TXT"asv=c5a6d09f249a7c269695d390be3385bb"3600
TXT"MS=ms73005824"3600
TXT"v=spf1 a mx include:spf.protection.outlook.com include:cmail1.com include:spf.mtasv.net include:_spf.createsend.com ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, 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.
  • 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