SurfaceMap › h › humanitas.nl

humanitas.nl

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

Domain & DNS

warn

30 passed 2 warn 0 failed

Areas

iRegistration ✓Delegation ✓Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 1 iteration and a 1-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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m), NS (1m40s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1m40s; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for humanitas.nl ›

Mail

fail

24 passed 3 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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (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 humanitas.nl ›