HTTP status code checker
The HTTP status code checker tells you what status code each URL returns, for up to 10 URLs at once, with every redirect hop, its Location header, and the response time.
- Free, no sign-up
- Results in seconds
- Checker · 35 free tools
How to read the results
- 2xx means the final URL answered successfully. 3xx hops are redirects; the Location column shows where each one sent us, exactly as the server wrote it.
- 301 and 308 are permanent moves, 302 and 307 temporary ones. A permanent move behind a temporary code is the most common surprise here.
- 404 and 410 mean the page is not there; 5xx means the server failed. 403 and 429 to an automated request are often bot rules, not missing pages.
- Time is how long each hop took to send its headers. It adds up across redirects, which is why short chains matter, but it is not a page-load measurement.
- X-Robots-Tag: noindex on the final response keeps a URL out of search results even when the HTML has no robots meta tag.
Related: redirect chain checker to trace one URL in detail, HTTP header inspector for every response header, broken link checker for the links on a page, and canonical checker for where the page says it lives.
This checks one page. The same problem usually repeats on every page built from the same template. Plans start at $14.99 a month.
How to use the http status code checker
- 1
Paste an address
A full URL or just a domain. We add https:// when it is missing.
- 2
We fetch it live
Our server requests the page now, the way a crawler would, and records what came back.
- 3
Read the evidence
Every result shows the value we read, so you can see why it passed or failed.
- 4
Fix and check again
Change the page, run it once more, and ship when the second run agrees.
What this does not measure
We would rather say what a tool cannot see than let a clean result mislead you.
- It checks up to 10 URLs per run. URLs beyond that are counted and skipped, not checked.
- It sends one automated request from one location. A site that answers bots differently, or a CDN region that disagrees, can return a different code to a browser.
- Response time is the time to the response headers of each hop, not how long the page takes to load or render.
- It follows HTTP redirects only, up to six hops. A JavaScript or meta refresh redirect is invisible to it.
Want the full picture?
This tool answers one question. A full audit runs every check on a page, scores it, and gives you a short list of what to fix first.
Questions about the http status code checker
More in the guides.
Keep reading

HTTP status codes for SEO: 404 vs 410, soft 404s, 5xx, and 429
Google treats 404 and 410 the same. 5xx and 429 slow crawling. A 200 error page is a soft 404.

Redirect chains and loops: 301 vs 302 vs 308, and how many hops is too many
Use 301 or 308 for permanent moves, redirect straight to the final URL, and keep any chain under five hops.

noindex vs robots.txt disallow: which one removes a page from Google?
Disallow stops crawling. noindex stops indexing. Using both at once means Google never reads the noindex.