mozilla.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1-240.akam.net: "41824.10"; ns1-240.akam.net: "41824.8"; ns4-64.akam.net: "41824.7"; ns5-65.akam.net: "41824.8"; ns7-66.akam.net: "41824.6". Hide or replace the version string.

SOA · refresh 3m is outside 20m–1d; retry 3m should be shorter than refresh 3m; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3m, retry 3m, expire 14d, negative TTL 1m.

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: MX (1m). 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.

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

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

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.