SurfaceMap › o › onlineagenda.nl

onlineagenda.nl

Checked 2026-10-22 15:01 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 !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.mailhet.nu (87.106.133.29): 29 records; ns1.mailhet.nu (2a01:239:290:ab00::1): 29 records; ns2.plazaxl-server2.nl (87.106.133.29): 29 records; ns2.plazaxl-server2.nl (2a01:239:290:ab00::1): 29 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.plazaxl-server2.nl, ns2.plazaxl-server2.nl; only in the zone: ns0.mailhet.nu, ns1.mailhet.nu. ns0.mailhet.nu, ns1.mailhet.nu, ns1.plazaxl-server2.nl, ns2.plazaxl-server2.nl report NS ns0.mailhet.nu ns1.mailhet.nu.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.mailhet.nu: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns2.plazaxl-server2.nl: "9.18.39-0ubuntu0.24.04.8-Ubuntu". Hide or replace the version string.
    #17
  • !
    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 onlineagenda.nl ›

Mail

fail

22 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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

Recent checks

✗

Full report

Mail report for onlineagenda.nl ›