SurfaceMap › n › nikhef.nl

nikhef.nl

Checked 2026-10-21 21:23 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

23 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers iSOA !DNSSEC ✓Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: cesano.nikhef.nl, dwalin.nikhef.nl; only in the zone: ns1.nikhef.nl, ns2.nikhef.nl, way.desy.de. cesano.nikhef.nl, dwalin.nikhef.nl, ext-dns-2.cern.ch, ns1.nikhef.nl, ns2.nikhef.nl, way.desy.de report NS ext-dns-2.cern.ch ns1.nikhef.nl ns2.nikhef.nl way.desy.de.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: cesano.nikhef.nl (glue 192.16.185.12, zone 192.16.185.12, 2001:610:120:1001::185:12). Update the glue at your registrar.
    #8
  • !
    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 nikhef.nl ›

Mail

fail

20 passed 5 warn 1 failed

Areas

iSPF ✗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
  • !
    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 nikhef.nl ›