SurfaceMap › i › ifw-dresden.de

ifw-dresden.de

Checked 2026-10-21 22:51 UTC · first added 2026-10-21
✗Problems found Score 71 of 100

Domain & DNS

warn

26 passed 1 warn 0 failed

Areas

iRegistration iDelegation iNameservers ✓SOA !DNSSEC ✓Records

Problems

  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 5 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 ifw-dresden.de ›

Mail

fail

20 passed 2 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.ifw-dresden.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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 ifw-dresden.de ›