HTTP Header Checker

Enter an address and see exactly what the server answers: the status code, every header, and each hop if the address redirects.

The request goes to our server, not to a third-party service — the site you check never sees you.

How to use

  1. Enter the address of the page — https:// is added if you omit it.
  2. Press «Check».
  3. Read the status code and the headers; a chain of blocks means redirects.

Good to know

The redirect chain is usually where the problem is

http to https, no-www to www, an old path to a new one — each hop is a separate request and a separate chance to get it wrong. Two redirects in a row cost real time on a phone, and a chain that ends in a 404 is invisible from the browser, which only shows you the final page. Here every hop is listed with its own status code.

Headers that decide how the page behaves

Cache-Control determines whether a visitor sees yesterday's page. Content-Type decides whether the browser renders the file or downloads it. Strict-Transport-Security, Content-Security-Policy and X-Frame-Options are the difference between a site that resists tampering and one that does not. All of them are invisible in the page itself and plainly visible here.

Frequently asked questions

Why does the status differ from what my browser shows?

The browser shows the final page after following every redirect. This tool shows each hop, so a chain of 301s ending in 200 appears as it really is.

Is the page content downloaded?

No. Only the headers are read, then the connection is closed. Nothing of the page body is fetched or stored.

How many redirects are followed?

Up to five. Anything longer is usually a loop, and a loop is the finding itself.

Does the checked site see me?

No. The request comes from our server with our own user agent; your address and browser are not passed on.

Related tools