HTTP Status Code Reference
| Code | Name | Category | Description |
|---|---|---|---|
| 100 | Continue | 1xx Informational | The initial part of the request has been received and the client should continue with the rest, or ignore this if the request is already finished. |
| 101 | Switching Protocols | 1xx Informational | The server agrees to switch protocols in response to an Upgrade request header, e.g. to WebSocket. |
| 200 | OK | 2xx Success | The request succeeded. The meaning of success depends on the HTTP method used. |
| 201 | Created | 2xx Success | The request succeeded and a new resource was created as a result, typically after a POST or PUT. |
| 202 | Accepted | 2xx Success | The request has been received but not yet acted upon; processing may complete asynchronously. |
| 204 | No Content | 2xx Success | The request succeeded but there is no content to return in the response body. |
| 206 | Partial Content | 2xx Success | Only part of the resource is being returned, matching a Range header sent by the client. |
| 301 | Moved Permanently | 3xx Redirection | The resource has been permanently moved to a new URL given by the Location header. |
| 302 | Found | 3xx Redirection | The resource temporarily resides at a different URL; the client should keep using the original URL for future requests. |
| 303 | See Other | 3xx Redirection | The response to the request can be found at another URL, retrieved with a GET request. |
| 304 | Not Modified | 3xx Redirection | The resource has not changed since the version specified by the request’s conditional headers; the client should use its cached copy. |
| 307 | Temporary Redirect | 3xx Redirection | The resource temporarily resides at a different URL; unlike 302, the request method and body must not change on redirect. |
| 308 | Permanent Redirect | 3xx Redirection | The resource has permanently moved to a new URL; unlike 301, the request method and body must not change on redirect. |
| 400 | Bad Request | 4xx Client Error | The server cannot process the request due to a client error, such as malformed syntax. |
| 401 | Unauthorized | 4xx Client Error | The request lacks valid authentication credentials for the target resource. |
| 402 | Payment Required | 4xx Client Error | Reserved for future use; occasionally used by APIs to signal a payment or billing problem. |
| 403 | Forbidden | 4xx Client Error | The server understood the request but refuses to authorize it. |
| 404 | Not Found | 4xx Client Error | The server cannot find the requested resource. |
| 405 | Method Not Allowed | 4xx Client Error | The request method is not supported for the requested resource. |
| 406 | Not Acceptable | 4xx Client Error | No content matching the criteria given in the request’s Accept headers is available. |
| 408 | Request Timeout | 4xx Client Error | The server timed out waiting for the request from the client. |
| 409 | Conflict | 4xx Client Error | The request conflicts with the current state of the target resource. |
| 410 | Gone | 4xx Client Error | The requested resource is no longer available and no forwarding address is known; this condition is expected to be permanent. |
| 411 | Length Required | 4xx Client Error | The server requires a Content-Length header that was not supplied. |
| 412 | Precondition Failed | 4xx Client Error | One or more conditions in the request’s header fields evaluated to false. |
| 413 | Content Too Large | 4xx Client Error | The request body is larger than the server is willing or able to process. |
| 414 | URI Too Long | 4xx Client Error | The request target is longer than the server is willing to interpret. |
| 415 | Unsupported Media Type | 4xx Client Error | The request body’s media type is not supported by the server or resource. |
| 418 | I'm a teapot | 4xx Client Error | A joke status from the 1998 HTCPCP RFC 2324; a server declining to brew coffee because it is a teapot. Not part of any serious spec. |
| 422 | Unprocessable Content | 4xx Client Error | The request was well-formed but contains semantic errors that prevent it from being processed. |
| 425 | Too Early | 4xx Client Error | The server is unwilling to process a request that might be replayed, typically sent over early (0-RTT) TLS data. |
| 429 | Too Many Requests | 4xx Client Error | The client has sent too many requests in a given period of time (rate limiting). |
| 500 | Internal Server Error | 5xx Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Not Implemented | 5xx Server Error | The server does not support the functionality required to fulfill the request. |
| 502 | Bad Gateway | 5xx Server Error | The server, acting as a gateway or proxy, received an invalid response from an upstream server. |
| 503 | Service Unavailable | 5xx Server Error | The server is temporarily unable to handle the request, often due to overload or maintenance. |
| 504 | Gateway Timeout | 5xx Server Error | The server, acting as a gateway or proxy, did not receive a timely response from an upstream server. |
| 507 | Insufficient Storage | 5xx Server Error | The server is unable to store the representation needed to complete the request (WebDAV). |
How it works
This is a reference table, not a live server check — it does not send any request. Type
a status code (e.g. 404) or part of a name (e.g. teapot) to
filter the table above; clear the box to see every code again.