1. Home
  2. Free tools
  3. HTTP header checker

HTTP header checker

See exactly what a server sends back for a page: the status code, the redirect chain, every response header with a plain-English note, the protocol (HTTP/1.1, HTTP/2) and the time to first byte.

No sign-up.Try:
Check several addresses at once (up to 10)
0 of 10

How to use it

  1. Enter a page address.
  2. Read the status, protocol and first-byte time at the top, then the fix list.
  3. Open the full header table to see each header with a short note on what it does.

What it checks

  • HTTP status code and the redirect chain
  • Every response header, annotated
  • HTTP/2 support and whether HTTP/3 is offered (Alt-Svc)
  • Time to first byte and total time
  • Version leaks in Server and X-Powered-By
  • Cookie flags (Secure, HttpOnly, SameSite)
  • Content-Type charset, Cache-Control and compression

Limits

  • Shows the response to a single GET request from our server. Other clients, locations and cookies can get different headers.
  • The notes explain common headers. Unusual or custom headers are listed without commentary.
  • Does not test HTTP/3 connections, only whether the server advertises them.

Public pages only, one page at one point in time. See the methodology and terms.

Frequently asked questions

What is an HTTP header?

A name and value pair sent with every request and response. Response headers tell the browser how to treat the content: its type, how long to cache it, whether to use HTTPS only, and more.

What do status codes like 200, 301 and 404 mean?

200 is success. 301 and 308 are permanent redirects, 302 and 307 temporary ones. 404 means not found, 410 gone. 500 to 599 are server errors.

Which headers matter for security?

Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options and Referrer-Policy are the main ones. The security headers checker grades them and gives copy-paste values.

Why is my Server header a problem?

Showing an exact version (for example nginx/1.18.0) helps attackers choose known exploits. It is not a vulnerability by itself, but hiding it is free.

What is a good time to first byte?

Under about 600 ms is a good target. Slow first bytes usually mean uncached pages, a slow database or a distant server.

How is this different from the security headers checker?

This tool shows the whole response and timing as a developer would read it. The security headers checker grades only the protective headers and explains each.

↑ ↓ to moveEnter to openEsc to closeAll results