SurfaceMap › m › mckinsey.de

mckinsey.de

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

Domain & DNS

warn

21 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers iSOA !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-89.akam.net: "41824.8"; a1-89.akam.net: "41824.4"; a12-64.akam.net: "48878.32"; a12-64.akam.net: "48878.27"; a18-65.akam.net: "48878.29"; a22-66.akam.net: "48878.27"; a22-66.akam.net: "48878.26"; a3-67.akam.net: "41824.4"; a9-64.akam.net: "41824.5"; a9-64.akam.net: "41824.4". 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). 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 mckinsey.de ›

Mail

fail

21 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.mckinsey.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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: geo-mail.mckinsey.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 93.187.113.108 (geo-mail.mckinsey.com). 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 mckinsey.de ›