📖 HTTP Status Codes Lookup
Find status codes by number or phrase and understand when to use each one.
Last updated: November 8, 2026 · By the BoltQuickTools team
Select a status code
Use search or click a code from the list.
Looking up a status code while you debug
A log line says 425, or a proxy keeps returning 502 and you need to know whose fault that is. This page is a searchable table of 39 common HTTP status codes for anyone reading logs, writing API error handling or mocking responses.
Three ways to reach a code
- Type in Search by Code or Name. It checks the code number plus the title, meaning and typical-use text, so
uploadworks as well as413. The list refreshes about 300 ms after you stop typing. - Pick a family from Status Class to show only 1xx, 2xx, 3xx, 4xx or 5xx codes.
- If you already know the number, enter it in the field marked "Jump to code" and press Jump. Jumping overwrites the search box and sets the class back to All.
Clicking a result fills in Category, Meaning, Typical Use and Caching Hint. Copy Status Line copies the line printed under those rows.
What a few searches return
| Input | Results |
|---|---|
Search timeout | 2 results: 408, 504 |
Search upload | 3 results: 100, 408, 413 |
Search 42 | 4 results: 422, 425, 426, 429 |
Status Class 5xx Server Error, empty search | 6 results: 500 to 505 |
Jumping to 429 shows the meaning "Rate limit exceeded.", the typical use "API throttling windows." and the caching hint "Usually not cached; honor Retry-After." The copied line is:
HTTP/1.1 429 Too Many Requests
Where the table stops
- It is a selection, not the full registry. Among the codes left out are 203, 205, 207, 300, 402, 407, 411, 414, 416, 417, 428, 507 and 511. Jumping to one of those does nothing at all: no message appears and the previous result stays on screen.
- Search skips the Caching Hint text.
retry-afterfinds nothing, even though the 429 entry mentions that header. - Pressing Enter in the jump field does not trigger the jump. Use the button.
- When a search has no matches the detail panel resets and the status line goes back to the placeholder
HTTP/1.1 200 OK. Copy Status Line does nothing until you select a code again. - The copied line always says HTTP/1.1. HTTP/2 and HTTP/3 responses carry only the number and no reason phrase, so do not expect that exact text in those captures.
- Caching hints are rules of thumb. Under RFC 9110, responses such as 404, 410 and 501 may be cached by default when headers do not say otherwise, which is more permissive than some hints here suggest. Check your actual
Cache-Controlheaders.
Choosing between similar codes
Should an expired token get 401 or 403?
The entries draw the line this way: 401 is for "Authentication is missing or invalid", with "Missing token or expired auth" as the typical use. 403 is for a request that was understood but refused, with "Insufficient permissions despite auth". An expired token is a 401.
Is a failed field validation 400 or 422?
This table lists 400 for invalid syntax or a bad payload shape, and 422 for input that parses but fails semantic validation, such as "Field validation errors in APIs". Pick one convention and use it across your API.
Can I search by symptom rather than by name?
Often, yes, because the meaning and typical-use text is searched too. rate limit lands on 429. It only matches the words in the entry, though, so a phrase the entry does not use will come up empty.
To see these codes on real requests, send one from the API Tester. The HTTP methods reference covers the other half of the exchange, and the API testing guide walks through checking responses.