SurfaceMap › r › rotterdam.nl

rotterdam.nl

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

Domain & DNS

fail

29 passed 1 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns3.rotterdam.nl (2a02:a400:b3::f001:1003): read udp [2a01:4f8:1c1c:eebf::1]:52910->[2a02:a400:b3::f001:1003]:53: i/o timeout.
    #14
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations and a 14-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 rotterdam.nl ›

Mail

warn

25 passed 4 warn 0 failed

Areas

iSPF ✓DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Signatures expire in 73h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-24T22:04:51Z (in 73h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (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 rotterdam.nl ›