SurfaceMap › h › hoo.be

hoo.be

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

Domain & DNS

warn

26 passed 2 warn 0 failed

Areas

iRegistration iDelegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    Unusual SOA timers
    SOA · expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 2h, retry 1h, expire 1d, negative TTL 1h.
    #23
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 5 iterations and a 4-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

!

Full report

Domain & DNS report for hoo.be ›

Mail

fail

26 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    Multiple SPF records
    SPF · Found 3 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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: google (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 hoo.be ›