HTTP Header Checker
Enter a URL to see the response headers its server sends, taken from the final page after any redirects: the status line, Content-Type, Cache-Control, Server, cookies and everything else, as received. Below them, six security headers are graded one by one: Strict-Transport-Security (HSTS), Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy, each with what goes wrong without it. Few big sites pass all six: on 10 November 2026 bbc.co.uk did, github.com, cloudflare.com and youtube.com passed five, and only 3 of the 12 sites below sent a Permissions-Policy at all.
Free, no sign-in, 20 checks a minute. http and https on the standard ports only; private and local addresses are refused. Also: Redirect checker, Website down checker.
Security headers of well-known sites
Checked on November 10, 2026 from one US connection, with the same code this tool runs. Click a site to run it live.
| Site | HSTS | CSP | XFO | XCTO | Referrer | Permissions | Good |
|---|---|---|---|---|---|---|---|
| google.com | none | none | good | none | none | none | 1 of 6 |
| github.com | 365d, preload | good | good | good | good | none | 5 of 6 |
| amazon.com | none | none | none | none | none | none | 0 of 6 |
| apple.com | 365d, preload | weak | good | good | weak | none | 3 of 6 |
| microsoft.com | 365d | none | none | none | none | none | 1 of 6 |
| wikipedia.org | 1231d, preload | none | none | none | none | none | 1 of 6 |
| cloudflare.com | 365d | weak | good | good | good | good | 5 of 6 |
| netflix.com | 365d | none | good | good | none | none | 3 of 6 |
| youtube.com | 365d | good | good | good | none | good | 5 of 6 |
| bbc.co.uk | 365d, preload | good | good | good | good | good | 6 of 6 |
| stripe.com | 730d, preload | good | good | good | weak | none | 4 of 6 |
| example.com | none | none | none | none | none | none | 0 of 6 |
Good counts the six graded headers that passed. github.com and stripe.com allow 'unsafe-inline' only for styles, which is not held against them; apple.com's and cloudflare.com's script policies allow inline scripts. amazon.com answered this checker 202 with none of the six.
HTTP Header Checker questions
Which security headers should a website send?
Five do real work on any site: Strict-Transport-Security with a max-age of at least a year (31536000 seconds), X-Content-Type-Options: nosniff, a Content-Security-Policy, clickjacking protection through CSP frame-ancestors or X-Frame-Options: SAMEORIGIN, and a Referrer-Policy such as strict-origin-when-cross-origin. Permissions-Policy is the sixth: it switches off browser features your pages never use, such as camera, microphone and geolocation. Skip X-XSS-Protection: browsers removed the filter it controlled (Chrome in version 78, in 2019), and OWASP advises leaving it out or setting it to 0.
What does HSTS preload mean?
Browsers ship a built-in list of domains that are only ever loaded over https, so even a first visit never touches plain http. To join it at hstspreload.org, a site serves a valid certificate, redirects http to https on the same host, serves every subdomain over https, and sends Strict-Transport-Security on the bare domain with max-age of at least 31536000, includeSubDomains and preload. The list is built into Chrome and used by Firefox, Safari and Edge, so leaving it again takes months of browser releases. github.com, apple.com, wikipedia.org, stripe.com and bbc.co.uk all asked for preload on 10 November 2026.
Should I use X-Frame-Options or CSP frame-ancestors?
frame-ancestors, with X-Frame-Options as a backup for old clients. When both are present, every current browser obeys frame-ancestors and ignores X-Frame-Options. frame-ancestors can also list the sites allowed to frame your pages, which X-Frame-Options cannot do: its ALLOW-FROM option never worked in Chrome or Safari and is obsolete. Sending frame-ancestors 'self' and X-Frame-Options: SAMEORIGIN together covers both.
Why are the headers here different from the ones in my browser?
The request is not the same. This checker asks from a Cloudflare data center with no cookies and its own User-Agent, so a CDN may answer from a different cache (cf-cache-status HIT instead of MISS, a different Age), a signed-in browser gets other Set-Cookie and Cache-Control headers, and bot protection may send a challenge or a stripped-down page instead: amazon.com answered this checker with a 202 instead of a 200 on 10 November 2026. Names also arrive in lower case over HTTP/2 and HTTP/3; header names are case-insensitive (RFC 9110), so Content-Type and content-type are one header.
What do Cache-Control, Age and cf-cache-status tell me?
How the page is cached. Cache-Control is the server's instruction: max-age is how many seconds a browser may reuse the response, s-maxage the same for shared caches such as CDNs, no-cache means check back with the server before reusing it, and no-store means never keep a copy. Age is how many seconds a CDN had held the copy it served. cf-cache-status is Cloudflare's own report: HIT (served from cache), MISS (fetched from the server), EXPIRED, BYPASS, or DYNAMIC, meaning Cloudflare does not cache that kind of response by default, as with most HTML. CloudFront and Fastly send x-cache with Hit or Miss instead.
More free website and domain tools
The redirect checker follows a URL through every 301, 302, 307 and 308 to the page that answers. The website down checker checks from outside your network whether a site answers, and how fast. When a name does not resolve at all, the DNS lookup, the DNS propagation checker, the CNAME lookup and the Nameserver lookup show what its DNS says. For who owns a domain and when it expires, use the WHOIS lookup; to find a name that is still free, the domain availability checker.