A complete reference of the HTTP status codes in the IANA registry that are defined by a published RFC, color-coded by category, with the defining RFC next to each one. Names follow RFC 9110 (so 413 is Content Too Large and 422 is Unprocessable Content). Search by code number, name, or description to quickly find what you need. Covers informational (1xx), success (2xx), redirection (3xx), client error (4xx), and server error (5xx) responses. Looking up the other half of the response? The MIME type reference maps every file extension to its Content-Type.
HTTP Status Code Reference
Searchable list of HTTP status codes
| Code | Name | Description |
|---|---|---|
| 100 | Continue | Server received the request headers; the client should send the body. (RFC 9110) |
| 101 | Switching Protocols | Server is switching protocols as requested (for example, to WebSocket). (RFC 9110) |
| 102 | Processing | WebDAV: request received and still being processed. Rarely sent today. (RFC 2518) |
| 103 | Early Hints | Preliminary headers (often Link preload hints) sent before the final response. (RFC 8297) |
| 200 | OK | Request succeeded. (RFC 9110) |
| 201 | Created | Request succeeded and a new resource was created. (RFC 9110) |
| 202 | Accepted | Request accepted for processing, but processing is not complete. (RFC 9110) |
| 203 | Non-Authoritative Information | Success, but the payload was modified by a transforming proxy. (RFC 9110) |
| 204 | No Content | Request succeeded, no content to return. (RFC 9110) |
| 205 | Reset Content | Request succeeded; the client should reset the document view (for example, clear a form). (RFC 9110) |
| 206 | Partial Content | Partial resource returned (range request). (RFC 9110) |
| 207 | Multi-Status | WebDAV: body contains separate status codes for multiple operations. (RFC 4918) |
| 208 | Already Reported | WebDAV: members of a binding already listed earlier in the response. (RFC 5842) |
| 226 | IM Used | Response is the result of instance manipulations (delta encoding) applied to the resource. (RFC 3229) |
| 300 | Multiple Choices | Several representations are available; the client may choose one. (RFC 9110) |
| 301 | Moved Permanently | Resource permanently moved to a new URL. Clients may change POST to GET. (RFC 9110) |
| 302 | Found | Resource temporarily at a different URL. Clients may change POST to GET. (RFC 9110) |
| 303 | See Other | Fetch the result at another URL with GET (common after a form POST). (RFC 9110) |
| 304 | Not Modified | Resource not modified since the cached version (conditional request). (RFC 9110) |
| 305 | Use Proxy | Deprecated. Must be accessed through a proxy; not supported by browsers. (RFC 9110) |
| 307 | Temporary Redirect | Temporary redirect; method and body are preserved. (RFC 9110) |
| 308 | Permanent Redirect | Permanent redirect; method and body are preserved. (RFC 9110) |
| 400 | Bad Request | Server cannot process the request due to a client error. (RFC 9110) |
| 401 | Unauthorized | Authentication required or failed (sent with WWW-Authenticate). (RFC 9110) |
| 402 | Payment Required | Reserved for future use; some APIs use it for billing errors. (RFC 9110) |
| 403 | Forbidden | Server understood the request but refuses to fulfill it. (RFC 9110) |
| 404 | Not Found | Resource not found. (RFC 9110) |
| 405 | Method Not Allowed | HTTP method not supported for this resource. (RFC 9110) |
| 406 | Not Acceptable | No representation matches the Accept headers sent. (RFC 9110) |
| 407 | Proxy Authentication Required | Client must authenticate with the proxy. (RFC 9110) |
| 408 | Request Timeout | Server timed out waiting for the request. (RFC 9110) |
| 409 | Conflict | Request conflicts with the current state of the resource. (RFC 9110) |
| 410 | Gone | Resource permanently removed with no forwarding address. (RFC 9110) |
| 411 | Length Required | Server requires a Content-Length header. (RFC 9110) |
| 412 | Precondition Failed | A conditional header (If-Match, If-Unmodified-Since) evaluated false. (RFC 9110) |
| 413 | Content Too Large | Request content exceeds server limits. Formerly "Payload Too Large". (RFC 9110) |
| 414 | URI Too Long | Request target URI is longer than the server will accept. (RFC 9110) |
| 415 | Unsupported Media Type | Request content format is not supported. (RFC 9110) |
| 416 | Range Not Satisfiable | Requested Range cannot be served for this resource. (RFC 9110) |
| 417 | Expectation Failed | Server cannot meet the Expect request header. (RFC 9110) |
| 418 | (Unused) | Reserved by RFC 9110 because of the April Fools "I'm a teapot" code (RFC 2324). Not a real status. (RFC 9110) |
| 421 | Misdirected Request | Request was sent to a server that cannot answer for this origin. (RFC 9110) |
| 422 | Unprocessable Content | Request is well-formed but semantically invalid. Formerly "Unprocessable Entity". (RFC 9110) |
| 423 | Locked | WebDAV: the resource is locked. (RFC 4918) |
| 424 | Failed Dependency | WebDAV: request failed because an operation it depended on failed. (RFC 4918) |
| 425 | Too Early | Server will not process a request that might be replayed (TLS early data). (RFC 8470) |
| 426 | Upgrade Required | Client must switch to a different protocol, named in the Upgrade header. (RFC 9110) |
| 428 | Precondition Required | Server requires the request to be conditional (to prevent lost updates). (RFC 6585) |
| 429 | Too Many Requests | Rate limit exceeded; may include Retry-After. (RFC 6585) |
| 431 | Request Header Fields Too Large | One header, or all headers together, are too large. (RFC 6585) |
| 451 | Unavailable For Legal Reasons | Access denied as a consequence of a legal demand. (RFC 7725) |
| 500 | Internal Server Error | Generic server error. (RFC 9110) |
| 501 | Not Implemented | Server does not support the functionality required (for example, an unknown method). (RFC 9110) |
| 502 | Bad Gateway | Invalid response from an upstream server. (RFC 9110) |
| 503 | Service Unavailable | Server temporarily unavailable (overload or maintenance); may include Retry-After. (RFC 9110) |
| 504 | Gateway Timeout | Upstream server did not respond in time. (RFC 9110) |
| 505 | HTTP Version Not Supported | Server does not support the HTTP version used. (RFC 9110) |
| 506 | Variant Also Negotiates | Server configuration error in transparent content negotiation. (RFC 2295) |
| 507 | Insufficient Storage | WebDAV: server cannot store the representation needed to complete the request. (RFC 4918) |
| 508 | Loop Detected | WebDAV: server found an infinite loop while processing the request. (RFC 5842) |
| 510 | Not Extended | Obsoleted. Further extensions to the request are required (HTTP Extension Framework). (RFC 2774) |
| 511 | Network Authentication Required | Client must authenticate to gain network access (captive portals). (RFC 6585) |
Get weekly dev tools and tips