HTTP Status Code Reference
Searchable reference of all HTTP status codes with descriptions and category filters.
The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols and the server has agreed to do so.
A WebDAV request may contain many sub-requests; this indicates the server has received and is processing the request.
Used to return some response headers before the final HTTP message.
Standard response for successful HTTP requests.
The request has been fulfilled, resulting in the creation of a new resource.
The request has been accepted for processing, but the processing has not been completed.
The server is a transforming proxy that received a 200 OK from its origin but is returning a modified version.
The server successfully processed the request and is not returning any content.
The server tells the client to reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
The message body that follows is by default an XML message and can contain a number of separate response codes.
The members of a DAV binding have already been enumerated in a preceding part of the response.
The server has fulfilled a request for the resource using one or more instance-manipulations.
Indicates multiple options for the resource from which the client may choose.
This and all future requests should be directed to the given URI.
Tells the client to look at another URL — temporary redirect.
The response to the request can be found under another URI using the GET method.
Indicates that the resource has not been modified since the version specified by the request headers.
The request should be repeated with another URI; the original request method must not change.
Future requests should use the given URI; the request method must not change.
The server cannot or will not process the request due to a client error (malformed syntax, invalid framing, etc.).
Authentication is required and has failed or has not yet been provided.
Reserved for future use. Currently used for digital payment systems.
The request was valid but the server is refusing action — the client lacks necessary permissions.
The requested resource could not be found but may be available in the future.
A request method is not supported for the requested resource.
The requested resource is capable of generating only content not acceptable according to the Accept headers.
The client must first authenticate itself with the proxy.
The server timed out waiting for the request.
The request could not be processed because of conflict in the current state of the resource.
The resource requested is no longer available and will not be available again.
The request did not specify the length of its content, which is required by the requested resource.
The server does not meet one of the preconditions that the requester put on the request.
The request is larger than the server is willing or able to process.
The URI provided was too long for the server to process.
The request entity has a media type which the server or resource does not support.
The client has asked for a portion of the file but the server cannot supply that portion.
The server cannot meet the requirements of the Expect request-header field.
Any attempt to brew coffee with a teapot should result in this error. (RFC 2324, an April Fools joke.)
The request was directed at a server that is not able to produce a response.
The request was well-formed but was unable to be followed due to semantic errors.
The resource that is being accessed is locked.
The request failed because it depended on another request which itself failed.
Indicates that the server is unwilling to risk processing a request that might be replayed.
The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header.
The origin server requires the request to be conditional.
The user has sent too many requests in a given amount of time (rate limiting).
The server is unwilling to process the request because its header fields are too large.
A server operator has received a legal demand to deny access to a resource.
A generic error message — the server encountered an unexpected condition.
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
The server cannot handle the request (because it is overloaded or down for maintenance).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used in the request.
Transparent content negotiation for the request results in a circular reference.
The server is unable to store the representation needed to complete the request.
The server detected an infinite loop while processing the request.
Further extensions to the request are required for the server to fulfill it.
The client needs to authenticate to gain network access.
About HTTP Status Code Reference
A complete reference of HTTP status codes (1xx–5xx). Search by code, name, or description, and filter by category to find what you need fast.
All processing happens entirely in your browser using modern web APIs. Nothing is uploaded to our servers — your data stays local. Free forever for everyone, with a Pro plan for power users who want an ad-free experience and API access.