SurfaceMap › m › markantinternet.nl

markantinternet.nl

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

Domain & DNS

error

29 passed 1 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration ✓Delegation ✓Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 7 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

Recent checks

!

Full report

Domain & DNS report for markantinternet.nl ›

Mail

fail

21 passed 4 warn 2 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
  • ✗
    Syntax errors
    SPF · Receivers reject the whole SPF record (permerror) because of: unknown mechanism "id".
    #25
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (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 markantinternet.nl ›