SurfaceMap › e › emo-hannover.de

emo-hannover.de

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

Domain & DNS

warn

26 passed 1 warn 0 failed

Areas

iRegistration iDelegation iNameservers ✓SOA ✓DNSSEC !Records

Problems

  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for emo-hannover.de ›

Mail

fail

21 passed 5 warn 1 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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: web.vdw.de
    #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
  • !
    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: default (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 emo-hannover.de ›