HTTP Status Codes
Complete, searchable HTTP status code reference. All 1xx–5xx codes with descriptions and use cases. Free, browser-based.
- Runs in your browser
- Tool input is not uploaded to ZeroTool servers
- Free · No Sign-Up
Scan with WeChat to share this tool
Examples, details and FAQ Worked examples, how it compares with other tools, and answers to common questions.
Status Code Categories
- 1xx Informational: Provisional responses — request received, server is still processing.
- 2xx Success: The request was received, understood, and accepted.
- 3xx Redirection: Further action must be taken to complete the request.
- 4xx Client Error: The request contains bad syntax or cannot be fulfilled.
- 5xx Server Error: The server failed to fulfill a valid request.
Common Status Codes at a Glance
- 200 OK — Standard success response.
- 201 Created — New resource created (common in POST/PUT APIs).
- 204 No Content — Success, no response body (common in DELETE).
- 301 Moved Permanently — SEO-safe permanent redirect.
- 400 Bad Request — Client sent malformed data.
- 401 Unauthorized — Authentication required.
- 403 Forbidden — Authenticated but not permitted.
- 404 Not Found — Resource does not exist.
- 429 Too Many Requests — Rate limit exceeded.
- 500 Internal Server Error — Unexpected server failure.
- 503 Service Unavailable — Server down or overloaded.
Searching the List
The search matches part of the code, the name or the English description, so a word can find fewer or more codes than you expect. redirect finds only 307 and 308, because the descriptions of 301 and 302 say "moved" instead; moved finds those two and 308:
307 Temporary Redirect
308 Permanent Redirect
301 Moved Permanently
302 Found
308 Permanent Redirect
A query of digits only matches codes that start with it, so 50 lists 500 to 508 and 4 lists every 4xx code; digits in names and descriptions are not searched. A short word also matches inside longer words: rate finds 429 and also 208, whose description contains the word "enumerated".
208 Already Reported
429 Too Many Requests
Choosing a Status Code for an API
| Situation | Code |
|---|---|
GET returns the resource | 200 |
POST creates a resource | 201, with a Location header |
Success with no response body (often DELETE) | 204 |
| Body is not valid JSON or has a syntax error | 400 |
| No token, or the token is invalid | 401 |
| Valid token, but the user does not have permission | 403 |
| The resource does not exist | 404 |
| Duplicate, such as an email that is already registered | 409 |
| The body parses, but a business rule fails (end date before start date) | 422 |
| Rate limit exceeded | 429 |
| Unhandled exception | 500 |
401 or 403. 401 means the server does not know who you are; the server that sends 401 must also send a WWW-Authenticate header (RFC 9110 §15.5.2). 403 means the server knows who you are, but you cannot do this. If the server must not reveal that the resource exists, it can send 404 instead of 403 (§15.5.4).
Redirects and the request method. For historical reasons, a browser can change a POST to a GET when it follows a 301 or 302 (§15.4.2). 307 and 308 must keep the method and body. Use 307 or 308 when a form POST must stay a POST.
Headers That Go With a Code
| Code | Header | Rule |
|---|---|---|
| 201 | Location: /api/users/456 | Points to the new resource |
| 401 | WWW-Authenticate: Bearer realm="api" | Required |
| 405 | Allow: GET, POST | Required (§15.5.6) |
| 429, 503 | Retry-After: 60 | Optional; seconds or an HTTP date (RFC 6585 §4) |
| 304 | — | No body; the client uses its cached copy |
Handling Status Codes in JavaScript
fetch() does not reject on 4xx or 5xx. It rejects only on network errors, so check res.ok (true for 200–299) or res.status:
const res = await fetch('/api/orders', { method: 'POST', body });
if (res.status === 401) return redirectToLogin();
if (res.status === 429) {
const wait = Number(res.headers.get('Retry-After') ?? 60);
return retryAfter(wait);
}
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const order = await res.json();
Limits
- The 64 codes of the IANA registry. The list matches the IANA HTTP Status Code Registry (last updated 2025-09-15) code for code and uses the registry's names: 104 is a temporary registration that expires on 2026-11-13, 305 Use Proxy is deprecated, 306 and 418 are listed as (Unused), and 510 is marked OBSOLETED. Codes that only one product uses, such as nginx 499 or Cloudflare 520–526, are in neither the registry nor the list.
- Former names stay searchable. RFC 9110 renamed 413 to Content Too Large and 422 to Unprocessable Content; their descriptions keep the old names Payload Too Large and Unprocessable Entity, so a search for either finds them. RFC 9110 section 15.5.19 reserves 418 because the April Fools' RFC 2324 used it for "I'm a teapot", and the description says so.
- English only. Names and descriptions are in English on every language version of this page. The search matches the code, the name, or words in the English description. The query is NFKC-normalized first, so full-width digits and letters such as
404work.
FAQ
What do the different HTTP status code ranges mean?
1xx = Informational (request received, continuing). 2xx = Success (request completed). 3xx = Redirection (further action needed). 4xx = Client error (bad request, not found, unauthorized). 5xx = Server error (the server failed to handle a valid request).
What is the difference between 301 and 302?
301 Moved Permanently says the resource has a new permanent URI and future references ought to use it (RFC 9110 section 15.4.2). 302 Found says the move is temporary, so clients ought to keep using the original URI (section 15.4.3). Google's crawlers treat a 301 as a strong signal and a 302 as a weak signal that the redirect target should be processed. A browser may change POST to GET when it follows either one; 308 and 307 keep the method.
When should I use 404 vs 410?
Use 410 Gone when the server knows the resource was removed on purpose and the condition is likely permanent; if the server cannot tell, RFC 9110 section 15.5.11 says to use 404. For Google Search the choice makes no difference: Google treats every 4xx code except 429 the same and drops the URL from the index.
Why does 429 matter for APIs?
429 Too Many Requests is the status code for rate limiting (RFC 6585 section 4). The response may include Retry-After with the number of seconds to wait; clients should wait at least that long and back off further on repeated 429s. Google's crawlers treat 429 like a server error and slow down.
Is my search sent anywhere?
No. The 64 codes are part of the page, and the search filters them in your browser. The search text is not sent or saved. When analytics is on, a search event records only the tool name and the action, not what you typed.