HTTP Status Code Explorer

The request succeeded.

The request succeeded and a new resource was created.

The request succeeded but there's no content to return.

The resource has permanently moved to a new URL.

The resource temporarily lives at a different URL.

Cached version is still valid, no need to resend.

The server couldn't understand the request due to invalid syntax.

Authentication is required and has failed or not been provided.

The client doesn't have access rights to this content.

The server can't find the requested resource.

The request method isn't supported for this resource.

The server timed out waiting for the request.

The request conflicts with the current state of the resource.

An April Fools' joke from RFC 2324 — servers refusing to brew coffee.

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

The server encountered an unexpected condition.

The server doesn't support the functionality required.

The server got an invalid response from an upstream server.

The server isn't ready to handle the request, often overloaded.

The upstream server didn't respond in time.