SurfaceMap › k › kmm.nl

kmm.nl

Checked 2026-10-22 14:03 UTC · first added 2026-10-21
✗Problems found Score 61 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:34898->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]:52204->[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 kmm.nl ›

Mail

fail

18 passed 2 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.kmm.nl does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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 kmm.nl ›