📡
HTTP Status Codes
Complete reference of HTTP status codes from 1xx to 5xx. Searchable and filterable table with code names and descriptions.
| 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 has asked the server to switch protocols and the server has agreed. |
| 102 | Processing | The server is processing the request but no response is available yet (WebDAV). |
| 103 | Early Hints | Used to return some response headers before the final HTTP message (RFC 8297). |
| 200 | OK | The request has succeeded. The meaning depends on the HTTP method used. |
| 201 | Created | The request has been fulfilled and resulted in a new resource being created. |
| 202 | Accepted | The request has been accepted for processing, but the processing has not been completed. |
| 203 | Non-Authoritative Information | The server is a transforming proxy that received a 200 OK from its origin but is returning a modified version. |
| 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 user agent to reset the 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 | The message body is an XML message that can contain separate response codes for each sub-operation (WebDAV). |
| 208 | Already Reported | The members of a DAV binding have already been enumerated in a preceding part of the response. |
| 226 | IM Used | The server has fulfilled a GET request for the resource and the response is a representation of the result of one or more instance-manipulations. |
| 300 | Multiple Choices | Indicates multiple options for the resource from which the client may choose. |
| 301 | Moved Permanently | This and all future requests should be directed to the given URI. |
| 302 | Found | Tells the client to look at another URL. The resource temporarily resides at a different URI. |
| 303 | See Other | The response to the request can be found under another URI 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 is available only through a proxy. Deprecated in RFC 7231. |
| 306 | Switch Proxy | No longer used. Originally meant "subsequent requests should use the specified proxy". |
| 307 | Temporary Redirect | The request should be repeated with another URI but future requests should still use the original URI. |
| 308 | Permanent Redirect | The request and all future requests should be repeated using another URI. |
| 400 | Bad Request | The server cannot process the request due to something perceived to be a client error. |
| 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 payment systems. |
| 403 | Forbidden | The request was valid but the server is refusing action. The user might not have permission. |
| 404 | Not Found | The requested resource could not be found but may be available in the future. |
| 405 | Method Not Allowed | A request method is not supported for the requested resource. |
| 406 | Not Acceptable | The requested resource is capable of generating only content not acceptable according to the Accept headers sent. |
| 407 | Proxy Authentication Required | The client must first authenticate itself with the proxy (RFC 7235). |
| 408 | Request Timeout | The server timed out waiting for the request. |
| 409 | Conflict | Indicates that the request could not be processed because of conflict in the current state of the resource. |
| 410 | Gone | The requested resource 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 that the requester put on the request. |
| 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 | Any attempt to brew coffee with a teapot should result in this code (RFC 2324). |
| 421 | Misdirected Request | The request was directed at a server that is not able to produce a response (RFC 7540). |
| 422 | Unprocessable Entity | The request was well-formed but was unable to be followed due to semantic errors (WebDAV). |
| 423 | Locked | The resource that is being accessed is locked (WebDAV). |
| 424 | Failed Dependency | The request failed because it depended on another request and that request failed (WebDAV). |
| 425 | Too Early | The server is unwilling to risk processing a request that might be replayed (RFC 8470). |
| 426 | Upgrade Required | The client should switch to a different protocol such as TLS/1.0. |
| 428 | Precondition Required | The origin server requires the request to be conditional (RFC 6585). |
| 429 | Too Many Requests | The user has sent too many requests in a given amount of time (rate limiting). |
| 431 | Request Header Fields Too Large | The server is unwilling to process the request because either an individual header field or all header fields are too large. |
| 451 | Unavailable For Legal Reasons | A server operator has received a legal demand to deny access to a resource. |
| 500 | Internal Server Error | A generic error message when an unexpected condition was encountered. |
| 501 | Not Implemented | The server either does not recognize the request method or lacks the ability to fulfil it. |
| 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 cannot handle the request (overloaded or down for maintenance). |
| 504 | Gateway Timeout | The server was acting as a gateway or proxy and did not receive a timely response. |
| 505 | HTTP Version Not Supported | The server does not support the HTTP protocol version used in the request. |
| 506 | Variant Also Negotiates | The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself. |
| 507 | Insufficient Storage | The server is unable to store the representation needed to complete the request (WebDAV). |
| 508 | Loop Detected | The server detected an infinite loop while processing the request (WebDAV). |
| 510 | Not Extended | Further extensions to the request are required for the server to fulfil it. |
| 511 | Network Authentication Required | The client needs to authenticate to gain network access (RFC 6585). |
Showing 63 of 63 status codes
Frequently Asked Questions
What are HTTP status codes?
HTTP status codes are 3-digit numbers returned by a server in response to an HTTP request. They indicate whether the request was successful, redirected, or resulted in an error.
What do the categories mean?
1xx: Informational, 2xx: Success, 3xx: Redirection, 4xx: Client Error, 5xx: Server Error.
Which codes should I know?
The most common are: 200 OK, 201 Created, 301 Moved Permanently, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 500 Internal Server Error.
Related Tools
How to Use
- 1 Browse the complete list of HTTP status codes from 1xx to 5xx.
- 2 Use the search bar to filter by code number or description.
- 3 Click any code to see detailed information about its meaning and usage.
- 4 Reference codes for debugging API responses and server configurations.