HTTP Status Codes
Searchable reference for every HTTP status code, grouped by category (1xx–5xx). Filter by code, name, or meaning. Free, private, browser-only.
62 of 62 codes
1xxInformational
4 entries| Code | Name | Description |
|---|---|---|
| 100 | Continue | The server has received the request headers and the client should proceed to send the request body. |
| 101 | Switching Protocols | The requester asked the server to switch protocols and the server agreed. |
| 102 | Processing | WebDAV. The server has received and is processing the request, but no response is available yet. |
| 103 | Early Hints | Used to return some response headers before the final HTTP message, useful for preloading. |
2xxSuccess
10 entries| Code | Name | Description |
|---|---|---|
| 200 | OK | Standard response for successful HTTP requests. |
| 201 | Created | The request has been fulfilled and a new resource has been created. |
| 202 | Accepted | The request has been accepted for processing, but processing is not complete. |
| 203 | Non-Authoritative Information | The returned metadata is not exactly the same as on the origin server but collected from a local or third-party copy. |
| 204 | No Content | The server successfully processed the request and is not returning any content. |
| 205 | Reset Content | The server successfully processed the request and asks the client to reset its document view. |
| 206 | Partial Content | The server is delivering only part of the resource due to a range header sent by the client. |
| 207 | Multi-Status | WebDAV. The message body that follows is an XML message with multiple separate response codes. |
| 208 | Already Reported | WebDAV. Members of a DAV binding have already been enumerated in a previous reply and are not being included again. |
| 226 | IM Used | The server has fulfilled a GET request and the response represents the result of one or more instance manipulations. |
3xxRedirection
8 entries| Code | Name | Description |
|---|---|---|
| 300 | Multiple Choices | The request has more than one possible response and the user-agent or user should choose one. |
| 301 | Moved Permanently | The URL of the requested resource has been changed permanently. The new URL is given in the response. |
| 302 | Found | The resource is temporarily located at a different URL; the client should continue to use the original URL for future requests. |
| 303 | See Other | The response to the request can be found at another URL using the GET method. |
| 304 | Not Modified | Indicates that the resource has not been modified since the version specified by the request headers. |
| 305 | Use Proxy | The requested resource must be accessed through the proxy given in the Location header. Deprecated. |
| 307 | Temporary Redirect | The request should be repeated with another URL, but future requests should still use the original URL. Method must not change. |
| 308 | Permanent Redirect | The request and all future requests should be repeated using another URL. Method and body must not change. |
4xxClient Error
29 entries| Code | Name | Description |
|---|---|---|
| 400 | Bad Request | The server cannot or will not process the request due to a client error (e.g., malformed syntax). |
| 401 | Unauthorized | Authentication is required and has failed or has not yet been provided. |
| 402 | Payment Required | Reserved for future use. Originally intended for digital cash or micropayment schemes. |
| 403 | Forbidden | The client is authenticated but does not have permission to access the requested resource. |
| 404 | Not Found | The requested resource could not be found but may be available again in the future. |
| 405 | Method Not Allowed | A request method is not supported for the requested resource. |
| 406 | Not Acceptable | The server cannot produce a response matching the list of acceptable values defined in the request headers. |
| 407 | Proxy Authentication Required | The client must first authenticate itself with the proxy. |
| 408 | Request Timeout | The server timed out waiting for the request. |
| 409 | Conflict | The request could not be processed because of conflict in the current state of the resource. |
| 410 | Gone | The resource requested is no longer available and will not be available again. |
| 411 | Length Required | The request did not specify the length of its content, which is required by the requested resource. |
| 412 | Precondition Failed | The server does not meet one of the preconditions specified by the requester. |
| 413 | Payload Too Large | The request is larger than the server is willing or able to process. |
| 414 | URI Too Long | The URI provided was too long for the server to process. |
| 415 | Unsupported Media Type | The request entity has a media type which the server or resource does not support. |
| 416 | Range Not Satisfiable | The client has asked for a portion of the file but the server cannot supply that portion. |
| 417 | Expectation Failed | The server cannot meet the requirements of the Expect request-header field. |
| 418 | I'm a teapot | Defined in 1998 as one of the traditional IETF April Fools jokes (RFC 2324). Returned by teapots requested to brew coffee. |
| 421 | Misdirected Request | The request was directed at a server that is not able to produce a response. |
| 422 | Unprocessable Content | The request was well-formed but was unable to be followed due to semantic errors. |
| 423 | Locked | WebDAV. The resource that is being accessed is locked. |
| 424 | Failed Dependency | WebDAV. The request failed because it depended on another request and that request failed. |
| 425 | Too Early | The server is unwilling to risk processing a request that might be replayed. |
| 426 | Upgrade Required | The client should switch to a different protocol given in the Upgrade header. |
| 428 | Precondition Required | The origin server requires the request to be conditional. |
| 429 | Too Many Requests | The user has sent too many requests in a given amount of time. Used for rate limiting. |
| 431 | Request Header Fields Too Large | The server is unwilling to process the request because either an individual header field or all the header fields collectively are too large. |
| 451 | Unavailable For Legal Reasons | The resource is unavailable due to legal demands, such as a censorship order. |
5xxServer Error
11 entries| Code | Name | Description |
|---|---|---|
| 500 | Internal Server Error | A generic error message when an unexpected condition was encountered and no more specific message is suitable. |
| 501 | Not Implemented | The server either does not recognize the request method, or it lacks the ability to fulfill the request. |
| 502 | Bad Gateway | The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
| 503 | Service Unavailable | The server is currently unavailable, generally because it is overloaded or down for maintenance. |
| 504 | Gateway Timeout | 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 | The server does not support the HTTP protocol version used in the request. |
| 506 | Variant Also Negotiates | Transparent content negotiation for the request results in a circular reference. |
| 507 | Insufficient Storage | WebDAV. The server is unable to store the representation needed to complete the request. |
| 508 | Loop Detected | WebDAV. The server detected an infinite loop while processing the request. |
| 510 | Not Extended | Further extensions to the request are required for the server to fulfill it. |
| 511 | Network Authentication Required | The client needs to authenticate to gain network access. |
About status codes
HTTP response status codes indicate whether a specific HTTP request has been successfully completed. They are grouped into five classes:
- 1xx — Informational. Request received, continuing process.
- 2xx — Success. The action was successfully received, understood, and accepted.
- 3xx — Redirection. Further action must be taken to complete the request.
- 4xx — Client Error. The request contains bad syntax or cannot be fulfilled.
- 5xx — Server Error. The server failed to fulfill an apparently valid request.