SurfaceMap › i › isgeschiedenis.nl

isgeschiedenis.nl

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

Domain & DNS

error

27 passed 2 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation ✓Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 0 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for isgeschiedenis.nl ›

Mail

warn

25 passed 7 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:webmaster@virtumedia.nl (needs isgeschiedenis.nl._report._dmarc.virtumedia.nl). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 2001:550:2:61::2fc:100 (lastmx.spamexperts.net). Ask your hosting provider to set one.
    #30
  • !
    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
  • !
    Not all MX hosts use DANE
    TLS · These MX hosts publish no TLSA records, so mail to them is not protected by DANE: mx.spamexperts.com, fallbackmx.spamexperts.eu, lastmx.spamexperts.net.
    #36

Recent checks

!

Full report

Mail report for isgeschiedenis.nl ›