SurfaceMap › m › muhka.be

muhka.be

Checked 2026-10-22 06:51 UTC · first added 2026-10-21
✗Problems found Score 72 of 100

Domain & DNS

warn

19 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · 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
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 1d.
    #23
  • !
    Not signed
    DNSSEC · 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

Recent checks

!

Full report

Domain & DNS report for muhka.be ›

Mail

fail

25 passed 3 warn 1 failed

Areas

✓SPF ✓DMARC ✗DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Weak DKIM key
    DKIM · RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): pm (768 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for muhka.be ›