SurfaceMap › r › ruuda.nl

ruuda.nl

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

Domain & DNS

error

19 passed 3 warn 1 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.ruuda.nl (2a04:c46:e00:fce6:404:26ff:fe00:82e): read udp [2a01:4f8:1c1c:eebf::1]:58693->[2a04:c46:e00:fce6:404:26ff:fe00:82e]:53: read: connection refused.
    #14
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.ruuda.nl: "NSD 4.15.2"; ns2.ruuda.nl: "NSD 4.15.2". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 14d is outside 20m–1d; retry 14d should be shorter than refresh 14d; expire 14d must be longer than refresh + retry. Current values: refresh 14d, retry 14d, expire 14d, negative TTL 1h.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

!

Full report

Domain & DNS report for ruuda.nl ›

Mail

warn

24 passed 5 warn 0 failed

Areas

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

Problems

  • !
    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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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
  • !
    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 ruuda.nl ›