HTTP Status Code Lookup
Search and learn every HTTP status code from 100 to 599.
Server received request headers, client should proceed to send body.
Server is switching protocols as requested.
Request succeeded. The standard success response.
Request succeeded and a new resource was created.
Request accepted for processing but not yet completed.
Request succeeded but there is no content to return.
Server is delivering only part of the resource (range request).
Resource has moved permanently to a new URL.
Resource is temporarily at a different URL.
Cached version is still valid; client can use it.
Redirect to a temporary URL, keep the HTTP method.
Permanent redirect, keep the HTTP method.
Server cannot process the request due to client error.
Authentication is required and has failed or not been provided.
Server refuses to authorize the request.
Resource was not found on the server.
Request method is not allowed for the resource.
Server timed out waiting for the request.
Request conflicts with the current state of the resource.
Resource is no longer available and will not be available again.
Request body is larger than the server is willing to process.
Media type of the request is not supported.
April Fools joke from RFC 2324. Servers may return this when refusing to brew coffee.
Request is well-formed but contains semantic errors.
Client has sent too many requests in a given time (rate limited).
Generic server error message.
Server does not support the functionality required.
Server acting as a gateway received an invalid response upstream.
Server cannot handle the request (overloaded or maintenance).
Upstream server failed to respond in time.
Server does not support the HTTP version used in the request.