SurfaceMap › n › nam.nl

nam.nl

Checked 2026-10-22 14:40 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

27 passed 2 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration !Delegation ✓Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations 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 nam.nl ›

Mail

warn

24 passed 8 warn 0 failed

Areas

✓SPF !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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: nam-nl.j-v1.mx.microsoft
    #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
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    Signatures expire in 87h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-26T06:07:36Z (in 87h0m0s). Check that re-signing works.
    #21
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:SITI-Cyberdefence-DMARC-Analysis@shell.com (needs nam.nl._report._dmarc.shell.com). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 nam.nl ›