Executive summary
example.com
Critical findings in the observed public configuration. Some basic protections were not detected.
Partial coverage: the score is based on 95% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.
2026-11-11 08:47 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.
Encryption is in place, but a gap could expose users.
Several browser hardening headers are missing, which removes layers of protection against script injection and framing.
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.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://example.com/ | grep -i "Strict-Transport-Security"
- 2.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://example.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- example.com
- Website request
- GET https://example.com/
- Scan time
- 2026-11-11 08:47:27 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
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 example.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-11 08:47:27 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/example.com)<a href="https://getmirror.online/report/example.com"><img src="https://getmirror.online/badge/example.com.svg" alt="Domain Armor grade"></a>https://getmirror.online/badge/example.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.
Agent access & discovery signals
Optional and unscored — it never changes the grade. Reads up to three public files from this site (robots.txt, llms.txt and /.well-known/security.txt) and reuses the homepage headers already fetched. llms.txt is an emerging proposal, not an official standard. It is informational and does not affect the grade.
Technical detail
Click a check to see the public data, a verification command, a safe fix recommendation and documentation sources.
Email security
24/25Encryption & certificate
18/25Browser protections
0/30DNS infrastructure
10/15Public DNS records
| A | example.com | 172.66.147.243 104.20.23.154 |
| AAAA | example.com | 2606:4700:10::ac42:93f3 2606:4700:10::6814:179a |
| MX | example.com | 0 . |
| NS | example.com | hera.ns.cloudflare.com elliott.ns.cloudflare.com |
| TXT | example.com | v=spf1 -all _k2n1y4vw3qtb4skdx9e7dxt97qrmmq9 |
| TXT | _dmarc.example.com | v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s |
| CAA | example.com | — |
| DS | example.com | 2371 13 2 c988ec423e3880eb8dd8a46fe06ca230ee23f35b578d64e78b29c3e1c83d245a |