washingtonpost.com

SOA · The nameservers serve different versions of the zone: 1 on ns-1027.awsdns-00.org (205.251.196.3), ns-1027.awsdns-00.org (2600:9000:5304:300::1), ns-1840.awsdns-38.co.uk (205.251.199.48), ns-1840.awsdns-38.co.uk (2600:9000:5307:3000::1), ns-404.awsdns-50.com (205.251.193.148), ns-404.awsdns-50.com (2600:9000:5301:9400::1), ns-666.awsdns-19.net (205.251.194.154), ns-666.awsdns-19.net (2600:9000:5302:9a00::1); 2016123960 on sdns34.ultradns.biz (156.154.142.34), sdns34.ultradns.biz (2610:a1:1003::22), sdns34.ultradns.com (156.154.140.34), sdns34.ultradns.com (2610:a1:1001::22), sdns34.ultradns.net (156.154.141.34), sdns34.ultradns.net (2610:a1:1002::22), sdns34.ultradns.org (156.154.143.34), sdns34.ultradns.org (2610:a1:1004::22). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

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 1h; resolvers may use either.

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 · The following MX hosts could not be resolved to IPv6 addresses: mxa-001a3c01.gslb.pphosted.com, mxb-001a3c01.gslb.pphosted.com

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.