HTTP Status Code Lookup

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.

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.

Standard response for successful HTTP requests. The actual response will depend on the request method used.

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 but is returning a modified version.

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

The server successfully processed the request, but is not returning any content. Requires requester to reset document view.

The server is delivering only part of the resource due to a range header sent by the client.

Indicates multiple options for the resource from which the client may choose.

This and all future requests should be directed to the given URI.

The resource was found but at a different URI. Client should continue to use the original URI.

The response to the request can be found under another URI using a GET method.

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

The request should be repeated with another URI but future requests should use the original URI.

The request and all future requests should be repeated using another URI.

The server cannot or will not process the request due to client error (e.g., malformed syntax).

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

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

The server understood the request but refuses to authorize it.

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 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 resource.

The server does not meet one of the preconditions specified in the request headers.

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 code. (April Fools' joke from 1998)

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

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

The client should switch to a different protocol.

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 header fields are too large.

The resource is unavailable for legal reasons (e.g., censorship).

A generic error message when the server encounters an unexpected condition.

The server either does not recognize the request method or lacks the ability to fulfill it.

The server received an invalid response from the upstream server.

The server is currently unavailable (overloaded or down for maintenance).

The server 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.