SurfaceMap › z › zalando.de

zalando.de

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

Domain & DNS

warn

23 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    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 (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 5m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for zalando.de ›

Mail

fail

26 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    DMARC not strict enough for BIMI
    BIMI · Mail clients will not show the logo. BIMI requires DMARC pct=100.
    #39
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    More than 5 MX records
    MX · Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    Applies to 10% of mail
    DMARC · DMARC policy only applies to 10% of failing mail (pct=10). Raise pct to 100 once you are confident in your setup.
    #18
  • !
    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 zalando.de ›