Automated public DNS and web checks; results may be incomplete. These are passive observations, not an assessment of the organization.
Executive summary
washingtonpost.com
Good shape, with a few gaps worth closing this quarter.
Partial coverage: the score is based on 47% of applicable check weight. 9 unverified check(s) are excluded, not counted as failures.
2026-11-15 18:23 UTC
Useful for your IT provider or a colleague. Anyone with the link can view the report.
Track your progress
Fix the findings, then come back and rescan. Your scan history is saved in this browser so you can see exactly what improved.
Spoofing email from this domain is hard.
Traffic to the site is encrypted and the certificate is valid.
Nothing in this category could be verified from public data.
The domain's infrastructure works, but recommended hardening is missing.
Help someone else check their domain
Share this public report with a colleague. They can review the evidence and check their own domain.
What to do first
- 1.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS washingtonpost.com
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- washingtonpost.com
- Website request
- GET https://washingtonpost.com/ → https://www.washingtonpost.com/
- Scan time
- 2026-11-15 18:23:00 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
- HTTPS available · Unverified
- SSL/TLS certificate validity · Unverified
- HSTS — enforce encryption in the browser · Unverified
- CSP — protection from script injection · Unverified
- Clickjacking protection · Unverified
- X-Content-Type-Options · Unverified
- Referrer-Policy · Unverified
- Permissions-Policy · Unverified
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Get the badge
Show the live grade for washingtonpost.com in a README, docs or site footer. The badge links to the public report and refreshes every 24 hours.
Scan shown on this page: 2026-11-15 18:23:00 UTC. The badge may display a cached result for up to 24 hours. Open the linked report to check its scan time.
[](https://getmirror.online/report/washingtonpost.com)<a href="https://getmirror.online/report/washingtonpost.com"><img src="https://getmirror.online/badge/washingtonpost.com.svg" alt="Domain Armor grade"></a>https://getmirror.online/badge/washingtonpost.com.svgScan history
AI fix plan
Pick scans from this browser's history. The AI compares them, explains what changed and builds a prioritized, step-by-step plan.
Scans to analyze
0 of 6 selectedThe current scan is always included.
AI-generated from your scan results only. Review each step before applying it; nothing is sent to or changed on the domain.
Technical detail
Click a check to see the public data, a verification command, a safe fix recommendation and documentation sources.
Email security
25/25Encryption & certificate
7/7Browser protections
—DNS infrastructure
8/15Public DNS records
| A | washingtonpost.com | 23.216.147.206 23.216.147.207 |
| AAAA | washingtonpost.com | — |
| MX | washingtonpost.com | 10 mxa-001a3c01.gslb.pphosted.com 10 mxb-001a3c01.gslb.pphosted.com |
| NS | washingtonpost.com | ns-1027.awsdns-00.org ns-1840.awsdns-38.co.uk ns-404.awsdns-50.com ns-666.awsdns-19.net sdns34.ultradns.biz sdns34.ultradns.com sdns34.ultradns.net sdns34.ultradns.org |
| TXT | washingtonpost.com | MS=ms58521745 _40ij1ve2dtneubti00ikilfe0zlr0kz _dhwsbe1t7yht6p4dsc72mcajq9aaum9 _rm8r4wsr378iet73p2f9j7oecnksay1 _zj8o0fyk0qj8jy5pt1zr1543e97ew7c f3de1c77b72748ff92a68f88f4d93dfd rovag_verification_token=C2158E1BE1D041B78CC57ED72101FF6C knowbe4-site-verification=e04590e121eee5fbc18ada6449219119 slack-domain-verification=YsnaUOhPU4Y6dCz5a3TqBIs4DxEXrVFbuKbGFRyS google-site-verification=0R8HaEZPmx7XZBckUaQMssOU2e6Dspe3AOMsYxNrWq8 google-site-verification=6Bi3yUCN2g3lzvqapLfrbgkQxob5YCjmZidGa2qiM4g google-site-verification=Xq6gcVYYZJtb2DQN6h2bo-hkrdmZpcdAKO8CeYl8290 google-site-verification=qcYuOKvxobypPYmqzzrcw5KiwtpfLgdEEt-HwMfLwvo google-site-verification=xLI97dy4D9FGihhl23twW5HHhVSmpnr2nWComZhpQVo globalsign-domain-verification=8frsHcE2ag-0ccaaP5BTpPmUJC8ob8pdjDQchfAWzD _globalsign-domain-verification=R1bvWDvJUF1gpXlmc7Q3deFwpZciil5dpJR4t-a8XM _globalsign-domain-verification=SQONiBgTxRVzPPtIHjei_IUGCiAa0KxoVWFw1QfVes mBd2513ESDgG6ZfaSrFYw4WaOC2b0M21Ehl8KWI3GmgTDpfYKwGuBum8ivsayoYLzVCetyXDieRUdW4qdQe+hw== brave-ledger-verification=28c1597498b6eafc29aac1f3a42f31559dfe03a832058ead6f684a518f180d62 v=spf1 ip4:198.72.14.0/23 ip4:192.72.255.0/24 ip4:54.156.98.51 ip4:54.210.51.17 include:spf.protection.outlook.com include:madgexjb.com include:spf-001a3c01.pphosted.com include:amazonses.com -all |
| TXT | _dmarc.washingtonpost.com | v=DMARC1; p=reject; pct=100; fo=1; rua=mailto:dmarc_rua@washingtonpost.com,mailto:mylza-8368@rua.dmarc.emailanalyst.com; ruf=mailto:dmarc_ruf@washingtonpost.com,mailto:mylza-8368@ruf.dmarc.emailanalyst.com |
| CAA | washingtonpost.com | 0 issue "amazon.com" 0 issue "amazonaws.com" 0 issue "amazontrust.com" 0 issue "awstrust.com" 0 issue "entrust.net" 0 issue "letsencrypt.org" 0 issue "pki.goog" |
| DS | washingtonpost.com | — |