Normalize the URL
Only public HTTP/HTTPS URLs on standard ports are allowed.
FREE HTTP RESPONSE CHECK
Enter a URL to inspect the actual HTTP security headers returned after redirects. This security header checker separates core, informational and deprecated headers without treating presence as a full security audit.
OBSERVED RESPONSE
| Group | Header | Status | Observed value |
|---|
METHOD
This is a focused HTTP security header check, not a vulnerability scanner. Use it to check HTTP security headers after a release, CDN change or server configuration update.
Only public HTTP/HTTPS URLs on standard ports are allowed.
Redirects are revalidated; cookies and credentials are not forwarded.
Each header shows its observed value or an explicit missing status.
WHAT IS CHECKED
The core group covers CSP, HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy. Cross-origin policies are reported separately, while X-XSS-Protection, Expect-CT and Feature-Policy are flagged as deprecated when sent.
LIMITS
The tool does not attack the site, test browser behavior or prove that a CSP is safe. The phrase security HTTP headers often refers to the same response-header family, but correct policy depends on the application.
FAQ
No. The checker uses the common response-header set and links to OWASP as a reference, but it is not an OWASP product and does not replace OWASP testing guidance.
This page reports only security headers from one HTTP response. Site Audit adds indexability, metadata, page structure, Schema and other SEO signals.
No. Local, private and reserved addresses, embedded credentials and non-standard ports are blocked to protect the service.
Sources for reviewing a result: OWASP Secure Headers Project · MDN HTTP headers
NEXT STEP
Run Site Audit for indexability, meta tags, Schema, links and the other signals available for one URL.