Free tool HTTP header checker: see what a server really sends
Enter a URL and get the status code and every response header the server returns, as a browser or a crawler would receive them. Each header comes with a one-line explanation, and the checklist flags what is missing: HSTS, a Content Security Policy, clickjacking protection, a stray noindex in X-Robots-Tag, insecure cookies.
- Status + every header
- Security and SEO checks
- Sent only when you click
Check the response headers of a URL
Enter a page address. Redirects are followed and the headers shown are those of the final page; tick the option to see every hop. Until you click Check, the result is a sample for github.com.
check.tapcub.com, which fetches it from Cloudflare’s network with the user-agent shown and a From: tools@tapcub.com header, then returns the status codes, response headers and at most 512 KB of the page. One click uses one request. The service records only the host name, status and timing for rate limiting, not the path, query or page content, and stores no results. Limits: 10 requests a minute and 200 a day per IP address.A full address or just a domain; https:// is added if you leave it out.
The User-Agent header sent with the request. Some servers answer crawlers differently.
Final response
200 OK · 1,366 ms · https://github.com/
Status, time spent on the server responses and the final address.
Checks
Missing or risky headers first. Notes are worth knowing but rarely urgent.
- OKNo missing security or indexing headers found.
- OKHSTS is set for a year or more with includeSubDomains and preload, which meets the browser preload list requirements.
Response headers
Grouped by purpose. Hover a cut-off value to read it in full.
| Header | Value | Type | What it does |
|---|---|---|---|
| content-security-policy | default-src 'none'; base-uri 'self'; child-src github.githubassets.com github.com/assets-cdn/worker/ github.com/assets/ gist.github.com/assets-cdn/worker/; conn… | Security | Content Security Policy: which sources scripts, styles, frames and connections may come from. |
| referrer-policy | origin-when-cross-origin, strict-origin-when-cross-origin | Security | How much of this page’s address is sent to the next site as the Referer. |
| strict-transport-security | max-age=31536000; includeSubdomains; preload | Security | Tells browsers to use only https for this host for max-age seconds. |
| x-content-type-options | nosniff | Security | nosniff: browsers must not guess a different file type. |
| x-frame-options | deny | Security | Whether other sites may show this page in a frame (DENY or SAMEORIGIN). |
| x-xss-protection | 0 | Security | Legacy XSS filter switch; modern browsers ignore it. |
| content-language | en-US | SEO | Language of the content; search engines mostly rely on the page itself. |
| cache-control | max-age=0, private, must-revalidate | Caching | Caching rules for browsers and CDNs: max-age, no-cache, private, s-maxage… |
| etag | W/"1ae45a932e4a2d23044a8015afb6c4a3" | Caching | Version tag; the browser revalidates with If-None-Match and can get a 304. |
| vary | X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, X-GitHub-Client-Version, Accept-Language, Sec-Fetch-Site,Accept-Encoding, Accept, X-Reques… | Caching | Request headers that change the response; caches keep one copy per value. |
| content-type | text/html; charset=utf-8 | Content | File type and character set. |
| transfer-encoding | chunked | Content | chunked: the size was not known in advance. |
| set-cookie | _gh_sess=… | Cookie | Cookie _gh_sess; the value is too long to show its flags here. |
| set-cookie | _octo=…; expires=Wed, 17 Nov 2027 12:57:22 GMT; domain=.github.com; path=/; secure; SameSite=Lax | Cookie | Cookie _octo, kept until it expires. Flags: Secure · SameSite=Lax. |
| set-cookie | logged_in=…; expires=Wed, 17 Nov 2027 12:57:22 GMT; domain=.github.com; path=/; HttpOnly; secure; SameSite=Lax | Cookie | Cookie logged_in, kept until it expires. Flags: Secure · HttpOnly · SameSite=Lax. |
| server | github.com | Server / CDN | Server software as announced by the server or CDN. |
| accept-ranges | bytes | Other | — |
| date | Tue, 17 Nov 2026 12:57:15 GMT | Other | — |
| x-github-edge-region | westus3 | Other | — |
| x-github-request-id | D294:38A454:69683:D932A:6AFC4F32 | Other | — |
Redirect hops
HTTP 200 OK
accept-ranges: bytes
cache-control: max-age=0, private, must-revalidate
content-language: en-US
content-security-policy: default-src 'none'; base-uri 'self'; child-src github.githubassets.com github.com/assets-cdn/worker/ github.com/assets/ gist.github.com/assets-cdn/worker/; connect-src 'self' uploads.github.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com *.rel.tunnels.api.visualstudio.com wss://*.rel.tunnels.api.visualstudio.com github.githubassets.com objects-origin.githubusercontent.com copilot-proxy.githubusercontent.com proxy.individual.githubcopilot.com proxy.business.githubcopilot.com proxy.enterprise.githubcopilot.com *.actions.githubusercontent.com wss://*.actions.githubusercontent.com productionresultssa0.blob.core.windows.net productionresultssa1.blob.core.windows.net productionresultssa2.blob.core.windows.net productionresultssa3.blob.core.windows.net productionresultssa4.blob.core.windows.net productionresultssa5.blob.core.windows.net productionresultssa6.blob.core.windows.net productionresultssa7.blob.core.windows.net productionresultssa8.blob.core.windows.net productionresultssa9.blob.core.windows.net productionresultssa10.blob.core.windows.net productionresultssa11.blob.core.windows.net productionresultssa12.blob.core.windows.net productionresultssa13.blob.core.windows.net productionresultssa14.blob.core.windows.net productionresultssa15.blob.core.windows.net productionresultssa16.blob.core.windows.net productionresultssa17.blob.core.windows.net productionresultssa18.blob.core.windows.net productionresultssa19.blob.core.windows.net productionresultssa30.blob.core.windows.net productionresultssa31.blob.core.windows.net productionresultssa32.blob.core.windows.net github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com wss://alive-s…
content-type: text/html; charset=utf-8
date: Tue, 17 Nov 2026 12:57:15 GMT
etag: W/"1ae45a932e4a2d23044a8015afb6c4a3"
referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin
server: github.com
strict-transport-security: max-age=31536000; includeSubdomains; preload
transfer-encoding: chunked
vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, X-GitHub-Client-Version, Accept-Language, Sec-Fetch-Site,Accept-Encoding, Accept, X-Requested-With
x-content-type-options: nosniff
x-frame-options: deny
x-github-edge-region: westus3
x-github-request-id: D294:38A454:69683:D932A:6AFC4F32
x-xss-protection: 0
set-cookie: _gh_sess=…
set-cookie: _octo=…; expires=Wed, 17 Nov 2027 12:57:22 GMT; domain=.github.com; path=/; secure; SameSite=Lax
set-cookie: logged_in=…; expires=Wed, 17 Nov 2027 12:57:22 GMT; domain=.github.com; path=/; HttpOnly; secure; SameSite=LaxShare these inputs: the values go after the # in the link, so they never reach a server.
https://tapcub.com/tools/http-header-checker
Version v1.0Updated Update history
What to look at first
Most header problems fall into four groups. The checklist is ordered the same way.
Status code
The first line decides everything else: 200 is a normal page, 301 / 308 a permanent redirect, 302 / 307 a temporary one, 404 / 410 gone, 5xx a server failure. A page you want in search must end on 200.
Security headers
HSTS forces https, CSP limits where scripts can come from, X-Frame-Options or frame-ancestors stops clickjacking, nosniff stops type guessing. Missing ones are warnings, not outages: the site works, it is just easier to attack.
Indexing headers
X-Robots-Tag can noindex a page without anything visible in its HTML, which is why it is easy to miss after a staging setting leaks to production. Link headers can carry the canonical URL and hreflang alternates.
Caching and cookies
Cache-Control and ETag decide whether repeat visits hit the network. Set-Cookie flags decide whether a cookie travels over http (missing Secure), is readable by scripts (missing HttpOnly) or crosses sites (SameSite).
Headers can differ between pages, between http and https, and between user-agents. Check the pages that matter (home, a product or article, a redirect target) and repeat with a crawler user-agent if search engines see something odd.
Three steps
No sign-up, and nothing is requested until you click.
-
1
Enter the URL
Paste the address of a page, a file (CSS, an image, a PDF) or just the domain.
-
2
Pick who fetches it
Chrome on desktop shows what visitors get. Switch to Googlebot, Bingbot or GPTBot to see whether the server answers crawlers differently.
-
3
Read and fix
Work down the checklist, then copy the raw headers into a ticket for whoever runs the server or CDN.
How the checker fetches and judges
One GET request from Cloudflare’s network through check.tapcub.com, the same way for every user-agent:
- Redirects are followed one hop at a time (each target is checked again), up to 5 hops; the headers shown are those of the final response
- The body is not returned to the page; only status line and headers are analysed. Time is the sum of the server responses, without our own DNS checks
- Long header values are cut at 2,000 characters and each Set-Cookie at 300 characters by the service
- Checks follow RFC 9110 / 9111 for HTTP and caching, RFC 6797 for HSTS, CSP Level 3, Google’s X-Robots-Tag specification and the MDN guidance on legacy headers
| Header | Good value | If missing |
|---|---|---|
Strict-Transport-Security | max-age=31536000; includeSubDomains | Warning on https pages |
Content-Security-Policy | A policy without bare 'unsafe-inline' | Warning |
X-Frame-Options or frame-ancestors | DENY / SAMEORIGIN / 'self' | Warning |
X-Content-Type-Options | nosniff | Note |
Referrer-Policy | strict-origin-when-cross-origin or stricter | Note (browser default applies) |
X-Robots-Tag | Absent on pages you want indexed | noindex is an error |
Set-Cookie | Secure; HttpOnly; SameSite=Lax | Warning per cookie |
Reading the github.com sample
The sample on this page was fetched on 2026-11-17 as Chrome on desktop. Here is what the headers say.
| Header | Value (shortened) | Reading |
|---|---|---|
| Status | 200 OK | Normal page, no redirect |
strict-transport-security | max-age=31536000; includeSubdomains; preload | One year, subdomains included, eligible for the browser preload list |
content-security-policy | default-src 'none'; … | Starts from “nothing allowed” and lists every source, the strictest style of policy |
x-frame-options | deny | No site, not even GitHub itself, may frame the page |
cache-control | max-age=0, private, must-revalidate | Personalised HTML: no shared caching, revalidate every time |
set-cookie | logged_in=…; HttpOnly; secure; SameSite=Lax | Hidden from scripts, https only, not sent on cross-site requests |
The checklist shows only OK items for this page. Try your own site next: a typical small site misses CSP and frame protection, and often sends a version number in Server or X-Powered-By.
Header problems that slip through
They do not break the page, so nobody notices until something goes wrong.
noindex left in X-Robots-Tag
A staging rule copied to production removes pages from search with nothing visible in the HTML. Check the header after every deploy.
Origin and CDN disagree
Headers added on the origin server can be stripped or replaced by the CDN, and the other way round. Test the public URL, not the server directly.
HSTS on www only
If the bare domain does not send HSTS (or does not redirect to https first), the very first visit is still unprotected.
Cookies without flags
Session cookies need Secure and HttpOnly; SameSite=None without Secure is rejected outright by current browsers.
Watch what crawlers and visitors actually get
A header check is a snapshot. TapCub keeps watching: which crawlers fetch your pages, which pages error, and how fast they are for real visitors.
Bots counted separately
Five layers and 197+ rules keep crawlers out of the denominator by default.
Learn moreErrors next to speed
JavaScript, resource and API errors with affected sessions, in the same report.
Learn moreCrawl compliance
Your robots.txt and llms.txt are fetched daily and compared with what actually crawled you.
Learn moreHTTP header checker questions
Still have a question?
Chat with the team behind TapCub — we usually reply within a few hours on business days.
How do I check the HTTP headers of a website?
Enter the URL above and click Check. In your own browser you can also open developer tools (F12), go to the Network tab, reload and click the first request; on the command line, curl -I https://example.com/ prints the headers of a HEAD request. This checker adds explanations, follows redirects and can fetch as a crawler.
What are the most important security headers?
Strict-Transport-Security, Content-Security-Policy, X-Frame-Options (or CSP frame-ancestors), X-Content-Type-Options and Referrer-Policy. Permissions-Policy and the cross-origin isolation headers (COOP, COEP, CORP) matter for sites with sensitive features. X-XSS-Protection is obsolete.
Why do I see different headers than in my browser?
The request comes from Cloudflare’s network, not your computer, and carries no cookies. Servers can vary headers by location, user-agent, cookies and A/B tests, and a CDN cache may answer instead of your server.
How do I check if X-Robots-Tag is blocking a page?
Run the page through the checker. A noindex or none value is shown as an error. Pick Googlebot as the user-agent too, because a header can be scoped to one crawler (for example googlebot: noindex).
Can I check headers of images, PDFs or JavaScript files?
Yes. Enter the file URL. X-Robots-Tag is in fact the only way to noindex a PDF or image, and Cache-Control on static files decides how long browsers keep them.
Does the checker follow redirects?
Yes, up to 5 hops, and it reports the headers of the final response. Tick “Show every redirect hop” to see each step, or use the redirect checker for a full analysis of 301 versus 302.
Is the URL I check stored?
No. The checking service logs only the host name, status and timing for rate limiting, and the result lives in this browser tab until you leave the page.
Update history
New features, fixes and data refreshes for this tool, newest first.
-
· v1.0
LaunchedFirst release.
Data this tool relies on
- Sample fetches (github.com, apple.com, wikipedia.org, example.com, bbc.com) — checked 2026-11-17, reviewed every 6 months (next review by 2027-05-17)
Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates
See which crawlers visit you
Add the TapCub snippet and the bot report shows every search engine and AI crawler that loads your pages, separately from human visitors.