| 100 | Continue | 1xx | The server has received the request headers and the client should proceed to send the request body. | |
| 101 | Switching Protocols | 1xx | The requester has asked the server to switch protocols and the server has agreed. | |
| 102 | Processing | 1xx | The server has received and is processing the request, but no response is available yet. | |
| 103 | Early Hints | 1xx | Used to return some response headers before final HTTP message. | |
| 200 | OK | 2xx | Standard success response. The request was successfully received, understood, and accepted. | |
| 201 | Created | 2xx | The request was fulfilled and a new resource was created. Common after POST. | |
| 202 | Accepted | 2xx | The request has been accepted but processing is not yet complete (async operations). | |
| 203 | Non-Authoritative Information | 2xx | The server successfully processed the request but is returning info from another source. | |
| 204 | No Content | 2xx | The server successfully processed the request and is not returning any content. | |
| 205 | Reset Content | 2xx | The server successfully processed the request, asks the requester to reset the document view. | |
| 206 | Partial Content | 2xx | The server is delivering only part of the resource due to a range header sent by the client. | |
| 207 | Multi-Status | 2xx | The message body contains multiple separate response codes (WebDAV). | |
| 208 | Already Reported | 2xx | Members of a DAV binding have already been enumerated in a previous reply. | |
| 226 | IM Used | 2xx | The server has fulfilled a GET request for the resource; response is a representation of the result. | |
| 300 | Multiple Choices | 3xx | Indicates multiple options for the resource from which the client may choose. | |
| 301 | Moved Permanently | 3xx | This and all future requests should be directed to the given URI. | |
| 302 | Found | 3xx | Tells the client to look at (browse to) another URL. Temporary redirect. | |
| 303 | See Other | 3xx | The response to the request can be found under another URI using the GET method. | |
| 304 | Not Modified | 3xx | Indicates that the resource has not been modified since the version specified by request headers. | |
| 305 | Use Proxy | 3xx | The requested resource is available only through a proxy, the address for which is provided. | |
| 307 | Temporary Redirect | 3xx | The request should be repeated with another URI; however, future requests should still use the original URI. | |
| 308 | Permanent Redirect | 3xx | All future requests should use another URI. Similar to 301 but the method must not change. | |
| 400 | Bad Request | 4xx | The server cannot or will not process the request due to an apparent client error. | |
| 401 | Unauthorized | 4xx | Authentication is required and has failed or has not yet been provided. | |
| 402 | Payment Required | 4xx | Reserved for future use, sometimes used for digital payment systems. | |
| 403 | Forbidden | 4xx | The request was valid, but the server is refusing action. Insufficient permissions. | |
| 404 | Not Found | 4xx | The requested resource could not be found. The most well-known HTTP status code. | |
| 405 | Method Not Allowed | 4xx | A request method is not supported for the requested resource (e.g. DELETE on a read-only endpoint). | |
| 406 | Not Acceptable | 4xx | The requested resource is capable of generating only content not acceptable by the Accept headers. | |
| 407 | Proxy Auth Required | 4xx | The client must first authenticate itself with the proxy. | |
| 408 | Request Timeout | 4xx | The server timed out waiting for the request. | |
| 409 | Conflict | 4xx | Indicates that the request could not be processed because of conflict in the current state of the resource. | |
| 410 | Gone | 4xx | Indicates that the resource requested was previously in use but is no longer available. | |
| 411 | Length Required | 4xx | The request did not specify the length of its content, which is required by the requested resource. | |
| 412 | Precondition Failed | 4xx | The server does not meet one of the preconditions specified in the request headers. | |
| 413 | Content Too Large | 4xx | The request is larger than the server is willing or able to process. | |
| 414 | URI Too Long | 4xx | The URI provided was too long for the server to process. | |
| 415 | Unsupported Media Type | 4xx | The request entity has a media type which the server or resource does not support. | |
| 416 | Range Not Satisfiable | 4xx | The client has asked for a portion of the file but the server cannot supply that portion. | |
| 417 | Expectation Failed | 4xx | The server cannot meet the requirements of the Expect request-header field. | |
| 418 | I'm a Teapot | 4xx | The server refuses to brew coffee because it is, permanently, a teapot. (RFC 2324 — April Fools') | |
| 421 | Misdirected Request | 4xx | The request was directed at a server that is not able to produce a response. | |
| 422 | Unprocessable Content | 4xx | The request was well-formed but was unable to be followed due to semantic errors. | |
| 423 | Locked | 4xx | The resource that is being accessed is locked. | |
| 424 | Failed Dependency | 4xx | The request failed because it depended on another request and that request failed. | |
| 425 | Too Early | 4xx | The server is unwilling to risk processing a request that might be replayed. | |
| 426 | Upgrade Required | 4xx | The client should switch to a different protocol such as TLS/1.3. | |
| 428 | Precondition Required | 4xx | The origin server requires the request to be conditional. | |
| 429 | Too Many Requests | 4xx | The user has sent too many requests in a given amount of time (rate limiting). | |
| 431 | Request Header Fields Too Large | 4xx | The server is unwilling to process the request because its header fields are too large. | |
| 451 | Unavailable For Legal Reasons | 4xx | A server operator has received a legal demand to deny access to a resource. | |
| 500 | Internal Server Error | 5xx | A generic error message when an unexpected condition was encountered on the server. | |
| 501 | Not Implemented | 5xx | The server either does not recognize the request method, or lacks the ability to fulfill the request. | |
| 502 | Bad Gateway | 5xx | The server was acting as a gateway or proxy and received an invalid response from the upstream server. | |
| 503 | Service Unavailable | 5xx | The server cannot handle the request (overloaded or down for maintenance). | |
| 504 | Gateway Timeout | 5xx | The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. | |
| 505 | HTTP Version Not Supported | 5xx | The server does not support the HTTP version used in the request. | |
| 506 | Variant Also Negotiates | 5xx | Transparent content negotiation for the request results in a circular reference. | |
| 507 | Insufficient Storage | 5xx | The server is unable to store the representation needed to complete the request. | |
| 508 | Loop Detected | 5xx | The server detected an infinite loop while processing a request. | |
| 510 | Not Extended | 5xx | Further extensions to the request are required for the server to fulfil it. | |
| 511 | Network Auth Required | 5xx | The client needs to authenticate to gain network access (captive portals). | |