Every web request ends with a three-digit verdict. 200, 404, 500 — you’ve seen them in browsers, logs, and API responses. The number is a sentence in code: it tells you exactly which party the problem belongs to.
The five families
| Range | Meaning | Whose fault |
|---|---|---|
| 2xx | Success | — |
| 3xx | Redirection | — |
| 4xx | Client error | You (the requester) |
| 5xx | Server error | The server |
That last column is the practical takeaway: a 4xx means fix your request; a 5xx means wait or contact the site owner. Debugging time is wasted when you’re chasing the wrong party.
The ones you’ll actually meet
| Code | Meaning | When you see it |
|---|---|---|
| 200 | OK | Everything worked |
| 301 | Moved permanently | Old URL → new URL |
| 302 | Found (temporary) | Login redirects |
| 400 | Bad request | Malformed API call |
| 401 | Unauthorized | Missing/wrong login |
| 403 | Forbidden | Logged in, but not allowed |
| 404 | Not found | Dead link |
| 429 | Too many requests | Rate limit hit |
| 500 | Internal server error | Server bug |
| 502/503 | Bad gateway / unavailable | Upstream down or overloaded |
Reading a status code like a pro
- 404 on an API call: your URL is wrong, not the server’s fault.
- 403 after login: your account lacks permission — the token works, the role doesn’t.
- 429: slow down; check the API’s rate-limit header (
Retry-After) and back off. - 5xx cluster: one request fails, retry; all requests fail, the site is down.
The full list lives in the HTTP status code reference — every code, its meaning, and typical causes, searchable in one page.
Status codes are the web’s oldest debugging language. Learn the big ten and you can read most of the internet’s error messages at a glance.