Find HTTP status codes, names, and explanations to quickly understand server and browser responses.
| Code | Name | Description | Reference |
|---|---|---|---|
| 100 | Continue | Initial part of the request received; client should continue. | RFC 9110 §15.2.1 |
| 101 | Switching Protocols | Server agrees to switch protocols (e.g., to WebSocket). | RFC 9110 §15.2.2 |
| 102 | Processing | WebDAV: server is processing but no response yet. | RFC 2518 |
| 103 | Early Hints | Preload Link headers before final response. | RFC 8297 |
| 200 | OK | Standard successful response. | RFC 9110 §15.3.1 |
| 201 | Created | Request succeeded and a new resource was created. | RFC 9110 §15.3.2 |
| 202 | Accepted | Request accepted but processing not complete. | RFC 9110 §15.3.3 |
| 203 | Non-Authoritative Information | Returned data is from a transforming proxy. | RFC 9110 §15.3.4 |
| 204 | No Content | Successful, but no body to return. | RFC 9110 §15.3.5 |
| 205 | Reset Content | Client should reset the document view. | RFC 9110 §15.3.6 |
| 206 | Partial Content | Range request fulfilled. | RFC 9110 §15.3.7 |
| 207 | Multi-Status | WebDAV: multiple statuses in body. | RFC 4918 |
| 208 | Already Reported | WebDAV: members already enumerated. | RFC 5842 |
| 226 | IM Used | Server fulfilled GET with delta encoding. | RFC 3229 |
| 300 | Multiple Choices | Multiple options for the resource. | RFC 9110 §15.4.1 |
| 301 | Moved Permanently | Resource permanently moved to new URL. | RFC 9110 §15.4.2 |
| 302 | Found | Resource temporarily at a different URL. | RFC 9110 §15.4.3 |
| 303 | See Other | Use GET to retrieve the resource. | RFC 9110 §15.4.4 |
| 304 | Not Modified | Cached version is still valid. | RFC 9110 §15.4.5 |
| 307 | Temporary Redirect | Redirect; preserve method. | RFC 9110 §15.4.8 |
| 308 | Permanent Redirect | Permanent redirect; preserve method. | RFC 9110 §15.4.9 |
| 400 | Bad Request | Malformed request. | RFC 9110 §15.5.1 |
| 401 | Unauthorized | Authentication required or failed. | RFC 9110 §15.5.2 |
| 402 | Payment Required | Reserved for future use; sometimes used by APIs for quota. | RFC 9110 §15.5.3 |
| 403 | Forbidden | Authenticated but not allowed. | RFC 9110 §15.5.4 |
| 404 | Not Found | Resource does not exist. | RFC 9110 §15.5.5 |
| 405 | Method Not Allowed | HTTP method not supported for resource. | RFC 9110 §15.5.6 |
| 406 | Not Acceptable | Cannot produce content matching Accept header. | RFC 9110 §15.5.7 |
| 407 | Proxy Authentication Required | Must authenticate with proxy. | RFC 9110 §15.5.8 |
| 408 | Request Timeout | Server timed out waiting for the request. | RFC 9110 §15.5.9 |
| 409 | Conflict | Request conflicts with current state. | RFC 9110 §15.5.10 |
| 410 | Gone | Resource permanently removed. | RFC 9110 §15.5.11 |
| 411 | Length Required | Content-Length header required. | RFC 9110 §15.5.12 |
| 412 | Precondition Failed | If-Match / If-None-Match precondition failed. | RFC 9110 §15.5.13 |
| 413 | Content Too Large | Request body too large. | RFC 9110 §15.5.14 |
| 414 | URI Too Long | Request URL too long. | RFC 9110 §15.5.15 |
| 415 | Unsupported Media Type | Content-Type not supported. | RFC 9110 §15.5.16 |
| 416 | Range Not Satisfiable | Requested byte range not available. | RFC 9110 §15.5.17 |
| 417 | Expectation Failed | Cannot meet Expect header requirements. | RFC 9110 §15.5.18 |
| 418 | I'm a teapot | April Fools joke from RFC 2324; sometimes used by APIs to refuse. | RFC 2324 |
| 421 | Misdirected Request | Request directed at server unable to produce response. | RFC 9110 §15.5.20 |
| 422 | Unprocessable Content | Semantic errors prevent processing. | RFC 9110 §15.5.21 |
| 423 | Locked | WebDAV: resource is locked. | RFC 4918 |
| 424 | Failed Dependency | WebDAV: failed due to a previous request failure. | RFC 4918 |
| 425 | Too Early | Server unwilling to risk replay. | RFC 8470 |
| 426 | Upgrade Required | Client must switch to a different protocol. | RFC 9110 §15.5.22 |
| 428 | Precondition Required | Server requires conditional headers. | RFC 6585 |
| 429 | Too Many Requests | Rate limit exceeded. | RFC 6585 |
| 431 | Request Header Fields Too Large | Headers too large to process. | RFC 6585 |
| 451 | Unavailable For Legal Reasons | Censored or legally restricted. | RFC 7725 |
| 500 | Internal Server Error | Generic server-side error. | RFC 9110 §15.6.1 |
| 501 | Not Implemented | Server does not support the request method. | RFC 9110 §15.6.2 |
| 502 | Bad Gateway | Invalid response from upstream server. | RFC 9110 §15.6.3 |
| 503 | Service Unavailable | Server temporarily overloaded or down for maintenance. | RFC 9110 §15.6.4 |
| 504 | Gateway Timeout | Upstream server did not respond in time. | RFC 9110 §15.6.5 |
| 505 | HTTP Version Not Supported | HTTP version is not supported. | RFC 9110 §15.6.6 |
| 506 | Variant Also Negotiates | Internal config error in negotiation. | RFC 2295 |
| 507 | Insufficient Storage | WebDAV: not enough storage. | RFC 4918 |
| 508 | Loop Detected | WebDAV: infinite loop detected. | RFC 5842 |
| 510 | Not Extended | Further extensions required. | RFC 2774 |
| 511 | Network Authentication Required | Captive portal: must authenticate to use network. | RFC 6585 |
Showing 61 of 61 codes.
Searchable table of every HTTP status code defined by IANA: informational (100–103), success (200–208, 226), redirection (300–308), client errors (400–451), and server errors (500–511). Each entry shows code, name, RFC reference, and common-use description. Filter by code or keyword to find the right one quickly.