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 request succeeded. The meaning depends on the HTTP method used.

The request succeeded and a new resource was created as a result.

The request has been accepted for processing, but processing is not complete.

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

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

The resource has been permanently moved to a new URL given in the Location header.

The resource resides temporarily under a different URL.

The response can be found under another URL using a GET request.

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

The request should be repeated with another URL, but future requests should still use the original URL.

The request and all future requests should be repeated using another URL, keeping the method.

The server cannot process the request due to a client error such as malformed syntax.

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

Reserved for future use, sometimes used by APIs to signal a billing or quota issue.

The server understood the request but refuses to authorize it.

The server cannot find the requested resource. The URL is not recognized.

The request method is known by the server but is not supported by the target resource.

The resource cannot produce a response matching the Accept headers sent in the request.

The server timed out waiting for the request from the client.

The request conflicts with the current state of the target 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 the resource requires.

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

The URI requested by the client is longer than the server is willing to interpret.

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

The server refuses to brew coffee because it is, permanently, a teapot. An April Fools' joke code.

The request was well-formed but could not be followed due to semantic errors.

The user has sent too many requests in a given amount of time (rate limiting).

The resource is unavailable due to legal demands such as censorship or takedown.

A generic error message given when an unexpected condition was encountered by the server.

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

The server, acting as a gateway, received an invalid response from the upstream server.

The server is not ready to handle the request, often due to maintenance or overload.

The server, acting as a gateway, did not receive a timely response from the upstream server.

The server does not support the HTTP protocol version used in the request.

The server is unable to store the representation needed to complete the request.

The client needs to authenticate to gain network access, often used by captive portals.