How to use
Paste the URL or a list
Enter a full address like https://example.com/page; https:// is added if missing. For many pages, switch to Bulk and paste up to 20 URLs, one per line.
Press Check
Our server sends a HEAD request and follows redirects. You get the status, response time, server or CDN, final URL, redirect chain, security grade with its checklist, and a caching verdict.
Review and copy headers
Filter the header list, read the meaning under each name, and copy a single value or all of them. Download the set as TXT or JSON, or the bulk table as CSV.
Why HTTP Header Checker
- Every response header from any URL, with status code, final URL, redirect hops and response time.
- A security grade from A+ to F, based on six key headers plus HSTS, CSP, cookie and version-leak checks.
- Plain-English meaning for over 40 common headers, a caching verdict and CDN detection.
- Bulk mode checks up to 20 URLs at once. Copy or download the results as text, JSON or CSV.
Common response headers and what they control
A typical response carries 10 to 30 headers. These are the ones most worth reading when you debug caching, redirects, indexing or security. Header names are case-insensitive, which is why the list shows them in lower case.
| Header | What it controls | Example value |
|---|---|---|
| content-type | The format and character set of the response | text/html; charset=utf-8 |
| cache-control | How long browsers and CDNs may reuse the response | public, max-age=3600 |
| location | Where a 3xx redirect sends the visitor | https://example.com/new-page |
| x-robots-tag | Indexing rules for search engines, set in the header | noindex, nofollow |
| strict-transport-security | Forces HTTPS on future visits | max-age=31536000; includeSubDomains |
| content-security-policy | Which sources scripts, styles and frames may load from | default-src 'self' |
| access-control-allow-origin | Which other sites may read the response (CORS) | * |
| server | The web server or CDN that answered | nginx or cloudflare |
| set-cookie | Cookies the server asks the browser to store | session=abc; Secure; HttpOnly |
Caching headers for SEO and speed
Caching decides whether a repeat visitor or a CDN downloads a file again or reuses the copy it has. Good caching makes pages faster, which helps visitors and Core Web Vitals. Bad caching either wastes bandwidth or keeps serving old content after you publish a change.
Check these headers on your HTML pages and on a CSS or image file, because they usually need different rules.
- Cache-Control: the main rule. Long max-age values suit versioned CSS, JS and images; HTML usually needs a short max-age or no-cache.
- ETag and Last-Modified: let the browser ask whether a file changed and get a small 304 Not Modified reply if it did not.
- Age: how many seconds a CDN or proxy has held its copy. A large Age on HTML can explain why an update is not showing.
- Vary: tells caches to store separate copies per request header, such as Accept-Encoding. Vary on User-Agent can reduce CDN hit rates.
- Expires: an older way to set a cache date. Cache-Control max-age takes priority when both are present.