HTTP Status Checker

Paste up to 50 web addresses and see the status code each one answers with — 200, 301, 404, 500 — plus the redirect chain, the response headers and the response time. The requests are made by the ToolCMB server.

  • 200 · 301 · 404 · 500
  • Up to 50 URLs
  • Redirect chains
  • Checked by our server
This tool works through our server

Your browser is not allowed to read the answers of other websites, so the addresses you enter are requested by the ToolCMB server. Only the addresses are sent — we do not store them or the results, and the pages themselves are never passed on.

Request method

GET downloads the page like a browser. HEAD asks for the headers only: faster, but a few servers answer it differently.

How it works

How to check HTTP status codes

One address per line, one click.

  1. 1

    Paste the addresses

    Enter up to 50 URLs, one per line. They are sent to the ToolCMB server, which requests each one — a browser is not allowed to read the answers of other websites.

  2. 2

    Choose how to ask

    Pick GET or HEAD, decide whether redirects are followed, and choose who the request claims to be: the ToolCMB checker, a desktop or phone browser, Googlebot or Bingbot.

  3. 3

    Read and export the results

    Each row shows the status, the final address, the number of redirects, the time and the content type. Open a row for the chain and the headers, then export everything as CSV.

Why ToolCMB

More than a three-digit number

Every answer comes with the details you need to fix it.

Bulk check

Up to 50 addresses per run, checked two at a time. A progress bar shows how far the run is, and Stop ends it early. Duplicate lines are checked only once.

Redirect chain per address

Every hop is listed with its status code, target address, IP address, HTTP version and time. Chains are followed for up to 10 redirects; loops are reported as errors.

Response headers

Open any row to read the headers of each hop — Location, Cache-Control, Content-Type, Server, X-Robots-Tag and the rest. Cookie values are masked.

Choice of user agent

Ask as the ToolCMB checker, Chrome on a desktop, Safari on an iPhone, Googlebot, Googlebot Smartphone or Bingbot to find pages that answer bots differently.

Summary and filters

Counters for 2xx, 3xx, 4xx and 5xx or failed requests sit above the table. Tap a class to show only those rows, for example every 404 in the list.

CSV export

Save the table as a CSV file or copy it as tab-separated text for a spreadsheet. The export includes the whole redirect chain of each address.

Honest about what is sent

The check runs on our server because a browser is not allowed to do it. Only the address you enter is sent; it is not stored.

Protected against abuse

Only public addresses can be checked, and the number of checks per minute is limited so the tool cannot be misused against other sites.

What HTTP status codes tell you

Every answer a web server gives starts with a three-digit status code. Browsers hide it, but search engines, link checkers and monitoring tools rely on it. The first digit names the class: 2xx means the request worked, 3xx sends the client to another address, 4xx says the request was wrong — the page is missing, or access is not allowed — and 5xx says the server itself failed. Knowing the code is the fastest way to tell a broken link from a server outage or a redirect that was set up the wrong way.

For each address, our server sends one request with the method and user agent you chose and records the answer. If the answer is a redirect and following is switched on, it requests the target too, hop by hop, for up to 10 redirects. With GET, the final HTML is read only to pick up the page title and a meta refresh; the page content is never returned to your browser. The request carries no cookies and comes from our server, not from your network, so a site that depends on login, location or bot filtering may answer differently than it does for you.

The most common mistake is the soft 404: an error page that says “not found” but answers with 200, so search engines keep crawling it. A missing page should return 404, or 410 if it is gone for good. The second is using a temporary 302 for a permanent move; use 301 or 308 instead. During maintenance, answer with 503 rather than 200 or 404, so crawlers come back later. And if a HEAD request returns 405 or another unexpected code, repeat the check with GET — some servers do not handle HEAD properly.

Status code classes and what to do

ClassMeaningWhat to do
2xx (200, 204)The request succeededNothing — unless an error page answers with 200 (soft 404)
3xx (301, 302, 307, 308)The address redirectsUse 301 or 308 for permanent moves and link straight to the target
4xx (403, 404, 410, 429)Missing page, no access or too many requestsFix or redirect broken links; check firewall and bot rules for 403
5xx (500, 502, 503, 504)The server or a proxy in front of it failedRead the server error log; use 503 only for planned downtime
FailedNo answer: DNS error, timeout, refused connection or TLS problemCheck the domain, the certificate and whether the server is running

Tips

  • For a single address, the Redirect Checker explains the chain in detail and tests the http, https and www variants.
  • A row that fails with a TLS error? Look at the certificate with the SSL Checker; a DNS error is a job for the DNS Checker.
  • Turn a list of dead URLs into 301 rules with the .htaccess Generator.
  • Check the same list once as a browser and once as Googlebot. Different status codes for the two often point to a firewall or bot rule. A site that verifies Googlebot by its IP address will notice that our request is not the real crawler and may refuse it.
FAQ

Frequently asked questions

Can’t find your answer? Contact us — we reply quickly.

What is an HTTP status code?

A three-digit number that a web server sends with every answer. 200 means the page loaded, 301 and 302 redirect to another address, 404 means the page was not found and 500 means the server ran into an error.

What is the difference between a 301 and a 302 redirect?

301 is a permanent move: search engines replace the old address with the new one in their index. 302 is temporary: the old address stays indexed. Use 301 (or 308) when a page has moved for good.

Why do I get 403 here when the page opens in my browser?

The request comes from our server and carries no cookies. Firewalls and bot filters often block requests from data centers or unknown user agents. Try the Chrome or Safari option under “Request as”; if the answer stays 403, the site is blocking automated requests.

What is the difference between 404 and 410?

Both say that the page is not available. 404 leaves open whether it may come back, while 410 says it was removed on purpose. Search engines drop both from the index; 410 is the clearer signal.

What is sent to your server?

Only the address or domain name you enter. A browser is not allowed to make this kind of request itself, so our server makes it for you and returns the result. We do not store the address or the result, and the content of the checked pages is never passed on.

Why is there a limit on the number of checks?

Each check makes our server contact another website. To keep the tool from being used to flood or probe other sites, the number of checks per minute and per day is limited, and private or internal network addresses are refused. Wait a moment and try again.

More free SEO and website tools

Generate tags and files, check status codes, redirects, DNS and certificates — free, without an account.

Browse all tools