SurfaceMap › v › voorschoten.nl

voorschoten.nl

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

Domain & DNS

error

27 passed 1 warn 1 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC ✓Records

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:40142->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]:36676->[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 voorschoten.nl ›

Mail

warn

25 passed 7 warn 0 failed

Areas

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

Problems

  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: wsn-mail.voorschoten.nl
    #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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.
    #24
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 20.103.184.16 (wsn-mail.voorschoten.nl). Ask your hosting provider to set one.
    #30
  • !
    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 voorschoten.nl ›