SurfaceMap › d › diabetesfonds.nl

diabetesfonds.nl

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

Domain & DNS

fail

27 passed 1 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.argewebhosting.eu (31.25.98.210): read tcp 46.225.38.91:52018->31.25.98.210:53: i/o timeout; ns1.argewebhosting.eu (2a05:1500:702:0:1c00:eff:fe00:ce): read tcp [2a01:4f8:1c1c:eebf::1]:49784->[2a05:1500:702:0:1c00:eff:fe00:ce]:53: i/o timeout.
    #19
  • !
    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

Recent checks

✗

Full report

Domain & DNS report for diabetesfonds.nl ›

Mail

fail

30 passed 3 warn 1 failed

Areas

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

Problems

  • ✗
    11 DNS lookups, over the limit of 10
    SPF · SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • !
    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: mail (1024 bits), mx (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Policy in testing mode
    TLS · With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33

Recent checks

✗

Full report

Mail report for diabetesfonds.nl ›