SurfaceMap › z › zeeuwseankers.nl

zeeuwseankers.nl

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

Domain & DNS

error

25 passed 4 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

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.zebi.nl: "9.18.49-1~deb12u2-Debian"; ns2.zebi.nl: "9.18.49-1~deb12u2-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d. Current values: refresh 15m, retry 10m, expire 14d, negative TTL 1h.
    #23
  • !
    Signatures expire soon
    DNSSEC · The earliest signature expires at 2026-10-29 03:59 UTC (in 155h0m0s). Check that automatic re-signing works.
    #30
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 50 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

Recent checks

!

Full report

Domain & DNS report for zeeuwseankers.nl ›

Mail

fail

18 passed 5 warn 1 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 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
  • !
    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 155h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-29T03:59:20Z (in 155h0m0s). Check that re-signing works.
    #21
  • !
    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 zeeuwseankers.nl ›