SurfaceMap › p › phoenix.de

phoenix.de

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

Domain & DNS

warn

18 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: a1-107.akam.net, a10-64.akam.net, a11-65.akam.net, a14-66.akam.net, a22-67.akam.net, a9-66.akam.net. a1-107.akam.net, a10-64.akam.net, a11-65.akam.net, a14-66.akam.net, a22-67.akam.net, a9-66.akam.net, ns01.zdf.de, ns02.zdf.de report NS a1-107.akam.net a10-64.akam.net a11-65.akam.net a14-66.akam.net a22-67.akam.net a9-66.akam.net ns01.zdf.de ns02.zdf.de.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-107.akam.net: "41824.10"; a1-107.akam.net: "41824.8"; a10-64.akam.net: "48878.26"; a10-64.akam.net: "48878.30"; a11-65.akam.net: "41824.9"; a11-65.akam.net: "41824.5"; a14-66.akam.net: "48878.27"; a14-66.akam.net: "48878.29"; a22-67.akam.net: "48878.33"; a9-66.akam.net: "41824.11"; a9-66.akam.net: "41824.10". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d; negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 15m, retry 5m, expire 30d, 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: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 45m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for phoenix.de ›

Mail

fail

20 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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
  • !
    Unreadable DKIM key
    DKIM · These keys could not be parsed, so signatures made with them will fail: default (public key is not valid base64).
    #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 phoenix.de ›