SurfaceMap › i › iserlohn.de

iserlohn.de

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

Domain & DNS

warn

27 passed 1 warn 0 failed

Areas

iRegistration ✓Delegation iNameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 21 iterations and a 24-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 iserlohn.de ›

Mail

fail

21 passed 8 warn 1 failed

Areas

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

Problems

  • ✗
    TLSA records not DNSSEC-validated
    TLS · These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mx-in.kommunale.it.
    #36
  • !
    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
  • !
    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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx-in.kommunale.it
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Applies to 50% of mail
    DMARC · DMARC policy only applies to 50% of failing mail (pct=50). Raise pct to 100 once you are confident in your setup.
    #18
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    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 iserlohn.de ›