SurfaceMap › f › focus.de

focus.de

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

Domain & DNS

warn

21 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-195.akam.net: "41824.7"; a1-195.akam.net: "41824.5"; a11-64.akam.net: "41824.11"; a11-64.akam.net: "41824.7"; a18-65.akam.net: "48878.30"; a18-65.akam.net: "48878.31"; a20-66.akam.net: "48878.31"; a20-66.akam.net: "48878.29"; a26-67.akam.net: "48878.29"; a7-64.akam.net: "41824.4"; a7-64.akam.net: "41824.5". Hide or replace the version string.
    #17
  • !
    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 (20s), AAAA (20s), MX (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for focus.de ›

Mail

fail

16 passed 4 warn 1 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 key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    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
  • !
    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 focus.de ›