SITEPROBELAB / FREE SECURITY TOOL

Security headers.
Know what’s missing.

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.

HSTSCONTENT SECURITY POLICYCLICKJACKINGHTTP HEADERS
✓ No signup · Public domains · Actionable findings
HEADER SIGNALS / EXAMPLENOT LIVE
#
EXAMPLE TARGETyour-company.com
HTTPS
WHAT THIS AUDIT LOOKS FOR EXAMPLE TOPICS
HSTS configurationREVIEW
Content Security PolicyREVIEW
MIME sniffing controlsREVIEW
Framing & referrer rulesREVIEW
FINDINGS, NOT A SECURITY SCORE↗
PUBLIC HTTP CHECKS/NO SIGNUP REQUIRED/EXPLAINABLE FINDINGS/FULL JSON EXPORT

Check the response.
Not a vanity score.

Enter a public hostname. SiteProbeLab retrieves selected public-page evidence and highlights header findings from its website audit.

✳
Open diagnostics deskHTTP security header inspection
ON-DEMAND CHECK
LIVE HTTP CHECK

Which browser protections are missing?

Check reported HTTP security header gaps for a public website. Results also offer the full SiteProbeLab audit for context.

↗ Remote HTTPS fetch
Only public domains · No logins
https://
Domain only is recommended (e.g. example.com). We check public website responses, not private servers or internal IP addresses.
◎
Your header report starts here.

Enter a public domain for verified findings. A missing warning is not proof that all headers are configured correctly.

LIVE REPORT / HEADER FINDINGS

Security header findings

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 ↗

Browser defenses.
Practical context.

Headers matter, but no single HTTP response certifies an entire website. These checks help prioritize a closer look.

A / TRANSPORT
↗

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 POLICY
B / CONTENT
#

CSP & framing

Content Security Policy can constrain resource loading and embedding. Avoid copying untested CSP rules into production.

CONTROL RESOURCE LOADING
C / BROWSER
{ }

MIME & referrers

X-Content-Type-Options and Referrer-Policy influence browser behavior. Verify the headers that reach real users.

CHECK RESPONSE HEADERS

Understand the
findings.

Read the full field guide ↗
Is this security headers checker free?

Yes. It uses SiteProbeLab's existing public website audit service. Its findings are informational and usage may be subject to backend limits.

Does a missing header mean a website is vulnerable?

Not automatically. Security depends on architecture, application behavior, threat model and test coverage. The checker highlights points worth reviewing.

Does the checker test every URL?

No. It reuses the existing audit service; it is not a complete spider or penetration test. Check important routes and non-200 responses separately.

What if Cloudflare and my origin send different headers?

Check the actual response delivered to visitors at the CDN edge. The origin and proxy may use different security headers.

What should I do with an Nginx header warning?

Review the effective configuration and add_header inheritance rules. Use always where appropriate, and test CSP before deploying. See our website trust guide.

Explore the full website toolkit.

Inspect crawl access, search metadata, AI crawler rules and email policies — alongside security header observations.

Open the toolkit ↗