verisign.com

SOA · refresh 5m is outside 20m–1d; retry 2h should be shorter than refresh 5m. Current values: refresh 5m, retry 2h, expire 14d, negative TTL 1d.

DNSSEC · NSEC3 uses 0 iterations and a 6-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; 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.

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

MX · The following MX hosts could not be resolved to IPv6 addresses: mail1.verisign.com, mail2.verisign.com, mail3.verisign.com, mail4.verisign.com, mail5.verisign.com, mail6.verisign.com

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

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.