SurfaceMap › s › security.nl

security.nl

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

Domain & DNS

warn

27 passed 4 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.certifiedsecure.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 5 2026 13:12:37 by root@localhost)"; ns2.certifiedsecure.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 5 2026 13:12:37 by root@localhost)"; ns3.certifiedsecure.com: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:12:54 by root@localhost)"; ns4.certifiedsecure.com: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:12:54 by root@localhost)". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 5m is outside 20m–1d; retry 30m should be shorter than refresh 5m. Current values: refresh 5m, retry 30m, expire 28d, negative TTL 5m.
    #23
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 100 iterations and a 8-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). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 5m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for security.nl ›

Mail

fail

21 passed 4 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
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx2.certifiedsecure.com
    #11
  • !
    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 security.nl ›