SurfaceMap › w › wur.nl

wur.nl

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

Domain & DNS

error

23 passed 2 warn 1 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration ✓Delegation ✗Nameservers ✓SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns-ext-01.wur.nl (2001:610:a38:4302::229): read udp [2a01:4f8:1c1c:eebf::1]:38404->[2001:610:a38:4302::229]:53: i/o timeout.
    #14
  • !
    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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 8h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for wur.nl ›

Mail

fail

28 passed 2 warn 1 failed

Areas

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

Problems

  • ✗
    Policy not reachable
    TLS · The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.wur.nl/.well-known/mta-sts.txt": context deadline exceeded (Client.Timeout exceeded while awaiting headers).
    #33
  • !
    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

Recent checks

✗

Full report

Mail report for wur.nl ›