seattlepi.com

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.hearstnp.com (glue 98.129.228.70, zone 34.198.18.191); ns2.hearstnp.com (glue 98.129.228.71, zone 34.192.165.114). Update the glue at your registrar.

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns2.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns3.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns4.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns5.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns6.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu". 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.

SPF · SPF record needs 4 DNS lookups (limit is 10). Problems found: include:mail.azure.localedge.com does not exist or has no records.

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

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

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.

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.