sophos.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-100.akam.net: "41824.9"; a10-65.akam.net: "48878.31"; a10-65.akam.net: "48878.33"; a11-66.akam.net: "41824.6"; a11-66.akam.net: "41824.10"; a14-67.akam.net: "48878.31"; a14-67.akam.net: "48878.30"; a18-64.akam.net: "48878.26"; a18-64.akam.net: "48878.31"; a9-65.akam.net: "41824.8"; a9-65.akam.net: "41824.6". Hide or replace the version string.

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.

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 2d and in the zone 1h; resolvers may use either.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · The following MX hosts could not be resolved to IPv6 addresses: mx-01-eu-west-1.prod.hydra.sophos.com, mx-02-eu-west-1.prod.hydra.sophos.com

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits). Rotate to a 2048-bit key.

TLS · With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.