HTTP Status Code Checker

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.

The request has succeeded. The information returned depends on the method used.

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

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

The returned information is from a cached copy instead of the origin server.

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

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

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

The requested resource has multiple representations available.

The requested resource has been permanently moved to a new URL.

The requested resource temporarily resides under a different URL.

The response to the request can be found under a different URL.

The resource has not been modified since the last request.

The requested resource temporarily resides under a different URL.

The requested resource has been permanently moved to a new URL.

The server cannot 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 server understood the request but refuses to authorize it.

The requested resource could not be found on the server.

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

Authentication with the proxy is required 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 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.

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.

The server refuses to brew coffee because it is a teapot. (April Fools' joke from 1998)

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

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

The server encountered an unexpected condition that prevented it from fulfilling the request.

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 from the upstream server.

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

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

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

The client needs to authenticate to gain network access.