HTTP Status Checker

See the exact HTTP status code any address answers with, plus its response time, size, server and every response header, without following redirects.

Checked from our serverOnly what you enter is sentNo sign-up

What the HTTP Status Checker does

The HTTP Status Checker sends one request to an address and shows exactly what came back: the status code and what it means, how long the server took, the content type and size, the server software, the secure connection used and every response header. It does not follow redirects, so a 301 or 302 is shown as it is, with the address it points to. Choose GET to download the page as a browser would, or HEAD to ask for the headers only. It is handy for checking redirects after a site move, finding pages that return errors, and seeing which headers a server sends.

How to use it

  1. Type the full address of the page, for example https://example.com/old-page.
  2. Choose GET, the usual choice, or HEAD to fetch the headers only.
  3. Press Check and read the status code, what it means and the tip under it.
  4. Open All response headers to see or copy every header.

Example

Checking http://kitlantis.com/ shows 301 Moved Permanently, pointing to https://kitlantis.com/, which is how the site sends visitors to the secure address. Checking https://kitlantis.com/no-such-page shows 404 Not Found, with the site’s own error page of about 20 KB.

Status codes that matter for search

Search engines index pages that answer 200. After moving a page, the old address should answer 301 or 308, so its ranking passes to the new one; a 302 says the move is only temporary. A page that is gone for good should answer 404 or 410, not 200 with an error message, which search engines call a soft 404.

Codes from 500 up mean the server failed. Search engines retry these, but if they last for days, the pages can drop out of results. 503 with a Retry-After header is the right answer during planned maintenance.

Questions people ask

What is sent to your server, and is it kept?

Only the address you type is sent, so the Kitlantis server can request it for you. It is not saved with anything about you; the admin only sees that the tool was used.

Why does a page work in my browser but show an error here?

Some sites block requests that do not come from a browser, or answer differently by country. Our server is in the United States (N. Virginia) and identifies itself as Kitlantis.

How do I see where a chain of redirects ends?

This tool shows one step. The Redirect Checker follows every step to the final page.

When should I use HEAD instead of GET?

HEAD fetches the headers without the page itself, which is quicker for large files. A few servers answer HEAD differently, so use GET when in doubt.

Related tools