Look up any HTTP status code

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.

The server has received and is processing the request, but no response is available yet.

Used to return some response headers before final HTTP message.

The request has succeeded.

The request has been fulfilled and a new resource has been created.

The request has been accepted for processing, but processing has not been completed.

The request was successful but the information may have been modified by a transforming proxy.

The server successfully processed the request but is not returning any content.

The server successfully processed the request and asks 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.

Provides status for multiple independent operations.

The members of a DAV binding have already been enumerated in a previous reply.

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 applied to the current instance.

The request has more than one possible response. The user agent should choose one of them.

The URL of the requested resource has been changed permanently.

The URL of the requested resource has been changed temporarily.

The server sent this response to direct the client to get the requested resource at another URI with a GET request.

Indicates that the resource has not been modified since the version specified by the request headers.

The requested resource must be accessed through the proxy given by the Location field.

This response code is no longer used. It was used in a previous version of the HTTP/1.1 specification.

The server is redirecting the user agent to a different resource.

The resource is now permanently located at another URL.

The server cannot or will not process the request due to a client error.

Authentication is required and has failed or has not been provided.

Reserved for future use. Originally intended for digital payment systems.

The client does not have access rights to the content.

The server cannot find the requested resource.

The request method is not supported for the requested resource.

The server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers.

Authentication is required with the proxy before the request can proceed.

The server timed out waiting for the request.

The request could not be completed due to a conflict with the current state of the resource.

The requested resource is no longer available.

The server refuses to accept the request without a defined Content-Length header.

The server does not meet one of the preconditions that the requester put on the request.

The request entity is larger than limits defined by the server.

The URI provided was too long for the server to process.

The media format of the requested data is not supported by the server.

The range specified in the Range header field cannot be fulfilled.

The expectation given in the Expect request-header field could not be met by this server.

The server refuses to brew coffee because it is, permanently, a teapot. (RFC 2324)

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 and that request failed.

The server is unwilling to risk processing a request that might be replayed.

The server refuses to perform the request using the current protocol.

The origin server requires the request to be conditional.

The user has sent too many requests in a given amount of time.

The server is unwilling to process the request because its header fields are too large.

The server is denying access to the resource as a consequence of a legal demand.

The server encountered an unexpected condition.

The server does not support the functionality required to fulfill the request.

The server, while acting as a gateway or proxy, received an invalid response.

The server is currently unable to handle the request.

The server, while acting as a gateway or proxy, did not receive a timely response.

The HTTP version used in the request is not supported by the server.

The server has an internal configuration error.

The method could not be performed on the resource because the server is unable to store the representation needed to successfully 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.