Skip to content

HTTP Status Checker

Check HTTP status codes and redirect chains.

Loading…

About HTTP Status Checker

A page can look fine in a browser and still answer crawlers with an error, or hide a redirect along the way. Enter an address and our server sends it a HEAD request, which asks for headers only, follows up to 10 redirects, and reports the final status code with its name, the address it ended on, the redirect count and the total time in milliseconds. When more than one hop was involved, the chain is listed under the result.

Features

  • Status code with its name, for example 404 Not Found
  • Final URL after up to 10 redirects
  • Response time for the whole request in milliseconds
  • Hop-by-hop chain with a status code for each URL
  • Refuses internal network and reserved addresses before any request is made

Limitations

  • Public http and https addresses only. Localhost, internal network ranges, .local and .internal names, and hostnames that do not resolve are refused.
  • The check uses a HEAD request and runs no JavaScript, so a server that treats HEAD differently from a normal page visit can report a different status.
  • Redirect following stops after 10 hops, the server waits up to 10 seconds for a connection or a response, and each IP address is limited to 20 checks per minute.
  • Only a fixed list of common status codes has a name here; others, such as 204 or 418, are labeled Unknown.

How it works

  1. Type or paste the address to check; if you leave out http:// or https://, https:// is added for you.
  2. Press Check Status and wait while our server requests the URL.
  3. Read the status badge: green for a 2xx code, amber for 3xx and red for anything else.
  4. Check the final URL, the response time and the number of redirects.
  5. If the address redirected, read the chain below the result for each hop and its code, then use Re-check or New URL.

Example input

https://example.com/old-page

Frequently asked questions