A status code checker tells you exactly what the server is saying in its response. This guide explains what those three-digit numbers mean, how to read them, and why it matters when you’re browsing or managing a site.
What those server numbers really say
Every time your browser requests a page, the server replies with a three-digit code. The first digit tells you the broad category: 1 means it’s still processing, 2 means success, 3 is a redirect, 4 is your fault, and 5 is the server’s fault. Anything outside 200–399 deserves a closer look. For instance, if you click a link and get a 404, the server isn’t guessing—it’s clearly stating that the page doesn’t exist, not that you should wait and try again.
Take a real site: you request https://example.com/blog. The server responds with a 301, meaning the page has moved permanently. The Location header then points to https://example.com/blog/. Your browser follows the redirect and lands on the new address. Without that 301, you’d hit a dead link and waste time wondering where the page went.
How to check a code yourself
- Enter a URL.
- Click Check status.
- See the final status code and every redirect along the way.
The five classes, and what each one means for you
| Class | Meaning | What to do about it |
|---|---|---|
| 1xx | Informational — the request was received | Nothing; you will rarely see one |
| 2xx | Success — 200 is the one you want | Nothing |
| 3xx | Redirect — 301 permanent, 302 temporary | Check it points where you meant, and only once |
| 4xx | Your request was the problem — 404, 403 | Fix the URL, the link, or the permissions |
| 5xx | The server was the problem — 500, 502, 503 | Check the server or host; retrying may work |
Where these mistakes bite you
Misinterpreting these codes can cost you traffic and rankings. If Googlebot sees a 404 on a page that once ranked well, it drops that page from its index. If visitors hit a 503 because your server is overwhelmed, they’ll leave and likely won’t return. A quick status check prevents small mistakes from becoming major problems.
Free shortcut to save the hassle
| Tool | What it does |
|---|---|
| HTTP Status Code Checker | Check a URL's HTTP status code and follow its full redirect chain. |
| HTTP Header Checker | See the full HTTP response headers any URL returns. |
| URL Parser | Break any URL into its protocol, host, path, hash and query parameters. |
| DNS Lookup | Look up all of a domain's DNS records in one place. |
Try the HTTP Status Code Checker
Run it here, free and in your browser — nothing to install and no sign-up.
Open the HTTP Status Code Checker →One last thing to watch
Bookmark this page so the tool is only a tap away next time you need a quick, reliable answer. It works on your phone just as well as on a computer, with no app to install.
Quick checklist to keep in your pocket
- 200 means all good, 404 means gone, 503 means server busy.
- 301 is a permanent move; 302 is temporary.
- Always follow the redirect chain to see the final destination.
Frequently asked questions
What do the common status codes mean?
200 is OK, 301 is a permanent redirect, 302 is temporary, 404 is not found, 410 is gone, and 500/502/503 are server errors. The tool spells out the one it finds.
Why should I care about the redirect chain?
Extra hops slow pages down and waste crawl budget, and mixing redirect types can confuse search engines. A clean setup is usually a single 301.
What is the difference between 301 and 302?
301 says the move is permanent, so search engines pass ranking to the new URL. 302 says temporary, so the original is kept. Using the wrong one is a common SEO mistake.
Does it check the final page or the first URL?
Both. It shows every redirect hop and the status of the final destination it lands on.
Are internal URLs allowed?
No. Only public http and https URLs; private and local addresses are blocked for safety.
