roche.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-178.akam.net: "41824.6"; a1-178.akam.net: "41824.7"; a18-66.akam.net: "48878.31"; a18-66.akam.net: "48878.26"; a4-67.akam.net: "48878.26"; a4-67.akam.net: "48878.31"; a6-65.akam.net: "48878.27"; a6-65.akam.net: "48878.30"; a7-66.akam.net: "41824.5"; a7-66.akam.net: "41824.4"; a9-66.akam.net: "41824.7"; a9-66.akam.net: "41824.5". 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 (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1h0m10s; resolvers may use either.

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: rkamtaext01.roche.com, rkamtaext02.roche.com, rmumtaext01.roche.com, rmumtaext02.roche.com, ridesmtaext01.roche.com, ridesmtaext02.roche.com, sc1esmtaext01.gene.com, sc1esmtaext02.gene.com

MX · Found 8 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

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