SurfaceMap › b › bitdefender.de

bitdefender.de

Checked 2026-10-21 21:48 UTC · first added 2026-10-21
!Passed with warnings Score 73 of 100

Domain & DNS

warn

22 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-39.akam.net: "41824.8"; a1-39.akam.net: "41824.4"; a10-64.akam.net: "48878.31"; a10-64.akam.net: "48878.30"; a20-66.akam.net: "48878.27"; a20-66.akam.net: "48878.32"; a3-65.akam.net: "41824.11"; a3-65.akam.net: "41824.10"; a6-65.akam.net: "48878.29"; a6-65.akam.net: "48878.31"; a9-64.akam.net: "41824.11"; a9-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

Recent checks

!

Full report

Domain & DNS report for bitdefender.de ›

Mail

warn

22 passed 7 warn 0 failed

Areas

!SPF !DMARC ✓DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    9 of 10 DNS lookups, with problems
    SPF · SPF record needs 9 DNS lookups (limit is 10). Problems found: include:_spf.digitalrivercontent.net does not exist or has no records.
    #2
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx01.bitdefender.com, mx02.bitdefender.com
    #11
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    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 bitdefender.de ›