What this checks
- Content-Security-Policy
- Strict-Transport-Security
- X-Content-Type-Options
- Referrer-Policy
A security headers checker inspects the HTTP response headers a public page returns, including protections that reduce framing, content-type and browser policy risks. Enter a URL to see which signals are present or missing and what to review next. Results describe header posture; they are not a penetration test or security guarantee.

Ask Richard about your report
Paid reports include direct founder help. If a finding is unclear, send it with the page, evidence and suggested fix attached, and Richard will explain what to do next.
Public pages only. No account, no card, no worker job.
Use the checker above for a deterministic header check. The full scan adds context, severity and route-by-route evidence.
Get Launch Pass โ $29Review before launch
The free tool gives you a visible first-pass signal. A paid PageLens AI report adds page evidence, severity, screenshots, ownership context and a scoped repair prompt.
Review this page for security headers checker. Start with this finding: "Content-Security-Policy". Make the smallest production-safe fix, preserve the existing design, then list verification steps for desktop, mobile and crawler-visible HTML.
Ship Check
$0
Verdict and top three launch risks
Launch Pass
$29
Key flows, AI-ready fixes, and verification
Use the checker above for a deterministic header check. The full scan adds context, severity and route-by-route evidence.
Headers are one layer of web security. This check does not test application logic, dependencies, authentication, infrastructure, exploitability or whether a policy is correctly tuned for every route.
A security headers checker reviews the browser-level protections your server sends with each public page. These headers do not make an insecure application secure by themselves, but they reduce common attack paths and show that the site has moved beyond framework defaults. For startups, agencies and AI-built sites, missing headers are often one of the quickest trust wins.
Good security header posture starts with HTTPS and HSTS so browsers know to use secure connections. X-Content-Type-Options helps prevent MIME sniffing. Referrer-Policy limits the data leaked when users click away. A careful Content-Security-Policy can reduce the blast radius of cross-site scripting, though it needs testing so it does not break legitimate scripts.
This free check is useful before launch, procurement reviews, app store submissions and customer security questionnaires. It gives you a concrete list of response headers to add or tune, then a full audit can connect those findings to cookies, third-party scripts and page-specific evidence.