SurfaceMap › d › denhaag.nl

denhaag.nl

Checked 2026-10-21 21:00 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

26 passed 2 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation !Nameservers iSOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-207.akam.net: "41824.6"; a1-207.akam.net: "41824.4"; a13-64.akam.net: "41824.9"; a13-64.akam.net: "41824.6"; a16-64.akam.net: "48878.27"; a16-64.akam.net: "48878.26"; a22-64.akam.net: "48878.29"; a22-64.akam.net: "48878.27"; a5-64.akam.net: "41824.4"; a5-64.akam.net: "41824.11"; a8-65.akam.net: "48878.26"; a8-65.akam.net: "48878.27". Hide or replace the version string.
    #17
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations and a 13-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 denhaag.nl ›

Mail

warn

25 passed 6 warn 0 failed

Areas

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

Problems

  • !
    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
  • !
    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 93h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-25T17:49:17Z (in 93h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), k1 (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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

!

Full report

Mail report for denhaag.nl ›