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

The request has succeeded

The request has been fulfilled and resulted in a new resource being created

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

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

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

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

The server cannot or will not process the request due to an apparent client error

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided

The request was valid, but the server is refusing action

The requested resource could not be found but may be available in the future

A request method is not supported for the requested resource

Indicates that the request could not be processed because of conflict in the request

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

A generic error message, given when an unexpected condition was encountered

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

The server was acting as a gateway or proxy and received an invalid response from the upstream server

The server is currently unavailable (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