HSTS & HTTPS
Strict-Transport-Security can tell browsers to prefer HTTPS on subsequent connections. Roll it out only when dependent hosts are ready.
STRONGER TRANSPORT POLICYSITEPROBELAB / FREE SECURITY TOOL
See what a public website reveals about its HTTP security headers. Identify reported HSTS, CSP and browser-protection gaps, then get practical fixes you can verify.
01 / SECURITY HEADERS CHECKER
Enter a public hostname. SiteProbeLab retrieves selected public-page evidence and highlights header findings from its website audit.
Check reported HTTP security header gaps for a public website. Results also offer the full SiteProbeLab audit for context.
Enter a public domain for verified findings. A missing warning is not proof that all headers are configured correctly.
This view highlights reported security header findings from the broader SiteProbeLab audit. It does not test every route, response code or subdomain and is not a security certification.
Want the underlying methodology? Read our field guide to security headers ↗
02 / UNDER THE HOOD
Headers matter, but no single HTTP response certifies an entire website. These checks help prioritize a closer look.
Strict-Transport-Security can tell browsers to prefer HTTPS on subsequent connections. Roll it out only when dependent hosts are ready.
STRONGER TRANSPORT POLICYContent Security Policy can constrain resource loading and embedding. Avoid copying untested CSP rules into production.
CONTROL RESOURCE LOADINGX-Content-Type-Options and Referrer-Policy influence browser behavior. Verify the headers that reach real users.
CHECK RESPONSE HEADERSYes. It uses SiteProbeLab's existing public website audit service. Its findings are informational and usage may be subject to backend limits.
Not automatically. Security depends on architecture, application behavior, threat model and test coverage. The checker highlights points worth reviewing.
No. It reuses the existing audit service; it is not a complete spider or penetration test. Check important routes and non-200 responses separately.
Check the actual response delivered to visitors at the CDN edge. The origin and proxy may use different security headers.
Review the effective configuration and add_header inheritance rules. Use always where appropriate, and test CSP before deploying. See our website trust guide.
YOUR NEXT CHECK
Inspect crawl access, search metadata, AI crawler rules and email policies — alongside security header observations.