HTTP status checker with full redirect chains
This HTTP status checker requests a web address the way a browser or search-engine crawler would and reports the status code it gets back — 200, 301, 404, 503 and so on. When the server redirects, it follows each redirect hop by hand and shows the code, address, response time and Location header of every step, so you can see exactly where a link ends up and how it gets there.
Paste up to 25 URLs, one per line, to check a batch. Under each result you get plain-English advice: whether a redirect should be permanent, whether the chain is longer than it needs to be, whether HTTP is upgraded to HTTPS, whether a loop or a noindex header will keep the page out of search results, and what the HSTS and caching headers say. Every status code links to its full explanation in our HTTP status codes reference.
How to use the HTTP Status Checker
- Type or paste one or more addresses into “URLs to check — one per line, up to 25”. Addresses without http:// or https:// start from http://.
- Tick “Also check the http/https and www/non-www versions” to test all four ways people might reach a site.
- Press Check status (or Ctrl + Enter). Each result appears as soon as it is ready; a progress bar tracks longer lists.
- Read the final status, the redirect chain and the advice under each card. Click any code for its meaning.
- For several URLs, review the summary table, then use Download CSV for a hop-by-hop report or Copy summary.
HTTP Status Checker features
Every hop, not just the end
Up to 10 hops are followed one at a time, recording each status code, URL, response time and Location header.
Redirect advice
Flags temporary 302/307 redirects used for permanent moves, chains of two or more hops, HTTPS downgrades, www/non-www canonicalisation and loops.
SEO headers
Shows X-Robots-Tag (with a noindex warning), Cache-Control, Strict-Transport-Security, Content-Type, Server, Last-Modified and ETag from the final response.
Bulk checks with CSV
Check up to 25 URLs in one go, sequentially and politely, then export one CSV row per hop for a spreadsheet or audit.
Safe by design
Only status codes and a few headers come back — page bodies are never downloaded — and private or local addresses are refused.
301, 302, 307 or 308: which redirect to use
Search engines treat 301 and 308 as a strong signal that the new address should replace the old one in results; 302 and 307 suggest the old address should stay. For a permanent change, use a permanent code and redirect in a single hop — straight from http://example.com to https://www.example.com/, not via an intermediate address. If you manage an Apache server, the .htaccess Redirect Generator writes the rules for you.
| Code | Meaning | Method kept? | Use it for |
|---|---|---|---|
| 301 Moved Permanently | Permanent | Not guaranteed (POST may become GET) | Moved pages, HTTP → HTTPS, domain changes |
| 308 Permanent Redirect | Permanent | Yes | Permanent moves of APIs and forms |
| 302 Found | Temporary | Not guaranteed | Short-term moves, A/B tests, login bounces |
| 307 Temporary Redirect | Temporary | Yes | Temporary moves where POST must stay POST |
| 303 See Other | Temporary | Always becomes GET | Showing a result page after a form submission |
Why results can differ from your browser
The check runs on Galaxy of Tools’ server on Cloudflare’s global network, not on your computer. Sites that block data-centre traffic, show different pages by country, require a login or cookie, or protect themselves with a bot challenge can return 403, 429 or 503 to the checker while opening normally for you. Redirects made with JavaScript or a meta refresh tag are not followed, because only response headers are read. Intranet, localhost and other private addresses cannot be checked at all.
Some servers treat repeated requests as an attack, so lists are checked one URL at a time with a short pause, and each network may make up to 120 checks every 10 minutes. To look at the parts of a long address, use the URL Parser; to see where a domain points, try the DNS Lookup.
HTTP Status Checker FAQ
How do I check if a URL redirects?
Paste it into the HTTP status checker and press Check status. If the first code is 301, 302, 303, 307 or 308, the address redirects; the chain shows every hop until the final page and its status code.
What is a good status code for a web page?
200 OK for a page that exists, a single 301 or 308 for a page that has moved permanently, and 404 or 410 for a page that no longer exists. Avoid answering missing pages with 200 — search engines call that a soft 404.
How many redirects are too many?
Ideally one. Each extra hop adds latency, and Googlebot follows at most 10 redirect hops before giving up. Browsers stop after about 20 with a “too many redirects” error.
Why does the checker show 403 when the page works for me?
The request comes from a server on Cloudflare’s network. Some sites block or challenge data-centre and automated traffic, or show different content by country, so they answer the checker differently from your browser.
Can I check pages on my local network or localhost?
No. For safety, the checker refuses localhost, private (10.x, 192.168.x, 172.16–31.x), link-local and other non-public addresses, and only connects to ports 80 and 443.
Is this HTTP status checker free?
Yes. There is no sign-up. Each network can make up to 120 checks every 10 minutes; if you reach the limit, wait a few minutes and continue.