Skip to main content

HTTP Status Code Checker

Checks up to 25 addresses at once and reports the status code, final address and response time of each.

We fetch the page for you. Our server fetches the public address you enter and reads the response. Nothing you enter is stored. Free, no account.

How it works

Your page returns 200 in the browser, so you assume the redirect works. Paste a list of addresses and see what a server gets back: the first code, the final code, how many redirects were in between, the response time. Rows group into working, redirecting, client errors, server errors and unreachable.

  1. 1

    Paste a list of addresses. Each one is requested from our server and followed through any redirects.

  2. 2

    You see the first status code, the final one, how many redirects were in between, the response time, the server and the content type.

  3. 3

    Rows are grouped into working, redirecting, client errors, server errors and unreachable. Export the table as CSV.

What it does not do

  • A site can answer our server differently from a visitor in another country or behind a login.

  • 25 addresses per run.

When a source is busy or a site does not answer, this tool says so. It never fills the gap with a guess.

Questions

My page says "not found" but the tool reports 200. Which is right?

Both. The server answered 200, which tells a crawler the page is fine, while the page itself tells a visitor it is missing. That mismatch is called a soft 404, and search engines treat such pages as errors once they notice. The fix is on the server: a missing page should answer 404, or 410 when it is gone for good.

Why does a 403 show in the tool but the page opens fine for me?

The tool requests each address from our server, with no cookies and no logged-in session. A page that sits behind a login, or one that answers different countries differently, can refuse our request with a 403 while your browser opens it without trouble. Treat the code as what an anonymous visitor from our server sees, not as proof the page is broken.

Can I check more than 25 addresses?

Not in one run. The limit is 25 addresses per run, so split a longer list into batches of 25 and check the next batch after the first. Export the table as CSV before you clear it, otherwise the rows are gone. For hundreds of pages, work through them in batches.