// reference
HTTP Status Codes
Every common HTTP status code from 1xx to 5xx, with its name and what it means — grouped by category.
HTTP status codes report the outcome of a request in three digits. This reference groups the ones you actually see — informational, success, redirects, client errors and server errors — each with a short, plain-English explanation.
2xx — Success
| Code | Name | Meaning |
|---|---|---|
200 | OK | Standard response for a successful request. |
201 | Created | The request succeeded and a new resource was created. |
202 | Accepted | The request was accepted but processing isn't complete. |
204 | No Content | Success, with no response body to return. |
206 | Partial Content | Part of the resource is returned (range request). |
3xx — Redirection
| Code | Name | Meaning |
|---|---|---|
301 | Moved Permanently | The resource has permanently moved to a new URL. |
302 | Found | The resource is temporarily at a different URL. |
303 | See Other | Fetch the resource with a GET at another URL. |
304 | Not Modified | The cached copy is still valid; no body is sent. |
307 | Temporary Redirect | Temporary redirect that preserves the HTTP method. |
308 | Permanent Redirect | Permanent redirect that preserves the HTTP method. |
4xx — Client error
| Code | Name | Meaning |
|---|---|---|
400 | Bad Request | The server can't process a malformed request. |
401 | Unauthorized | Authentication is required or has failed. |
403 | Forbidden | Authenticated, but not allowed to access this resource. |
404 | Not Found | The resource doesn't exist. |
405 | Method Not Allowed | The HTTP method isn't supported for this resource. |
406 | Not Acceptable | Can't produce a response matching the Accept headers. |
408 | Request Timeout | The client took too long to send the request. |
409 | Conflict | The request conflicts with the current state of the resource. |
410 | Gone | The resource has been permanently removed. |
415 | Unsupported Media Type | The request body format isn't supported. |
422 | Unprocessable Entity | Well-formed but semantically invalid (validation failed). |
429 | Too Many Requests | The client has sent too many requests (rate limited). |
5xx — Server error
| Code | Name | Meaning |
|---|---|---|
500 | Internal Server Error | A generic server-side failure. |
501 | Not Implemented | The server doesn't support the requested functionality. |
502 | Bad Gateway | An upstream server returned an invalid response. |
503 | Service Unavailable | The server is temporarily overloaded or down. |
504 | Gateway Timeout | An upstream server didn't respond in time. |
505 | HTTP Version Not Supported | The HTTP version isn't supported. |
// related tools
Put this to work
// related guides
Go deeper
Anatomy of an HTTP Request and Response A line-by-line breakdown of an HTTP request and response — the request line, status line, headers, and body — so raw HTTP stops looking like noise. HTTP Headers Parser The Complete Guide to HTTP for Developers HTTP end to end — what it is, the anatomy of a request and response, methods, status codes, and headers — with links to focused deep-dives and tools. HTTP Status Code Lookup How to Read and Parse HTTP Headers The anatomy of HTTP request and response headers, how to turn raw headers into JSON, and why duplicates become arrays. HTTP Headers Parser HTTP Status Codes Explained (1xx–5xx) What HTTP status code classes mean, the codes you'll actually hit, and how to tell a client error from a server error. HTTP Status Code Lookup
More developer references
Cheat sheets and lookups paired with 36+ free, private, browser-based tools.