SurfaceMap › p › plieger.nl

plieger.nl

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

Domain & DNS

error

15 passed 6 warn 1 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration ✗Delegation ✓Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): ns12.
    #9
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns12. ns12.pliegergroep.it report NS ns11.pliegergroep.it ns12 ns12.pliegergroep.it.
    #7
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 89.20.180.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2005120938 on ns12.pliegergroep.it (89.20.180.3); 2005120950 on ns11.pliegergroep.it (89.20.180.74). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · refresh 1m is outside 20m–1d; retry 1m should be shorter than refresh 1m; expire 1m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1m must be longer than refresh + retry; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1m, retry 1m, expire 1m, negative TTL 1m.
    #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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), NS (1s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1s; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for plieger.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: selector1 (1024 bits), selector2 (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 plieger.nl ›