Browse 40 common HTTP status codes with descriptions, real-world examples, and guidance on when to use each. Filter by class (1xx–5xx) or search by code, name, or keyword.
Try a different keyword such as a code (e.g. 404, 5xx),
name, or description fragment.
Five status code classes and what they signal.
| Class | Range | Meaning |
|---|---|---|
| 1xx | 100–199 | Informational. Request received, processing continues. |
| 2xx | 200–299 | Success. Request was understood and accepted. |
| 3xx | 300–399 | Redirection. Further action required to complete the request. |
| 4xx | 400–499 | Client error. The request has bad syntax or cannot be fulfilled. |
| 5xx | 500–599 | Server error. The server failed to fulfil a valid request. |
Practical reminders.
Status codes are advisory. The body of the response often contains more useful detail than the status itself.
4xx vs 5xx. 4xx blames the client, 5xx blames the server. Frameworks regularly mislabel — always check the actual cause before assigning blame.
Don't invent codes. Use the closest standard code rather than custom ones — clients, proxies, and CDNs treat unknown codes as the generic class default (e.g. 4xx → 400).