SurfaceMap › h › hzs.be

hzs.be

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

Domain & DNS

warn

19 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns.hzs.be, ns1.belnet.be, ns2.belnet.be; only in the zone: mercator.hzs.be, ns.belnet.be. mercator.hzs.be, ns.belnet.be, ns.hzs.be, ns1.belnet.be, ns2.belnet.be report NS mercator.hzs.be ns.belnet.be.
    #7
  • !
    Unusual SOA timers
    SOA · refresh 5m is outside 20m–1d; retry 10m should be shorter than refresh 5m; expire 10m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 10m must be longer than refresh + retry. Current values: refresh 5m, retry 10m, expire 10m, negative TTL 10m.
    #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 hzs.be ›

Mail

fail

20 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 hzs.be ›