SurfaceMap › w › wer-zu-wem.de

wer-zu-wem.de

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

Domain & DNS

warn

19 passed 3 warn 0 failed

Areas

iRegistration iDelegation iNameservers !SOA !DNSSEC !Records

Problems

  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 7d, negative TTL 3m.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (3m), MX (3m), NS (3m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 3m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for wer-zu-wem.de ›

Mail

fail

23 passed 3 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 2001:550:2:61::2fc:100 (lastmx.spamexperts.net). Ask your hosting provider to set one.
    #30
  • !
    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 wer-zu-wem.de ›