SurfaceMap › r › rtvnof.nl

rtvnof.nl

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

Domain & DNS

error

21 passed 4 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.rtvnof.nl (178.19.119.252): 162 records; ns1.rtvnof.nl (2001:67c:b0:0:178:19:119:252): 162 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.rtvnof.nl (glue 178.19.119.252, zone 178.19.119.252, 2001:67c:b0:0:178:19:119:252); ns2.rtvnof.nl (glue 161.97.72.154, zone 161.97.72.154, 2a02:c207:2131:3376::1). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.rtvnof.nl: "9.18.30-0ubuntu0.20.04.2-Ubuntu"; ns2.rtvnof.nl: "9.16.48-Ubuntu". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 30m.
    #23
  • !
    Signed but not delegated securely
    DNSSEC · The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27

Recent checks

!

Full report

Domain & DNS report for rtvnof.nl ›

Mail

fail

25 passed 2 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
  • !
    Signed, but no DS at parent
    DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • !
    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 rtvnof.nl ›