SurfaceMap › m › mainz.de

mainz.de

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

Domain & DNS

warn

28 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 mainz.de ›

Mail

fail

18 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.mainz.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mailmx0001.rlp.de, mailmx0002.rlp.de, mailmx0003.rlp.de, mailmx0004.rlp.de
    #11
  • !
    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 mainz.de ›