HTTP Status Codes – Full List & Meanings

62 results

  • 1xx100ContinueThe server has received the request headers and the client should continue.
  • 1xx101Switching ProtocolsThe server is switching protocols as requested.
  • 1xx102ProcessingThe server is processing the request but no response is available yet.
  • 1xx103Early HintsLinks to be preloaded by the client before the final response.
  • 2xx200OKThe request succeeded.
  • 2xx201CreatedThe request succeeded and a new resource was created.
  • 2xx202AcceptedThe request has been accepted for processing, but is not yet complete.
  • 2xx203Non-Authoritative InformationThe response is from a transformed copy of the origin server.
  • 2xx204No ContentThe request succeeded but there is no content to return.
  • 2xx205Reset ContentThe request succeeded and the client should reset the document view.
  • 2xx206Partial ContentThe server is delivering only part of the resource due to a range header.
  • 2xx207Multi-StatusMultiple status codes for a WebDAV request.
  • 2xx208Already ReportedThe members of a DAV binding have already been enumerated.
  • 2xx226IM UsedThe server has fulfilled a GET request for the resource.
  • 3xx300Multiple ChoicesThe request has more than one possible response.
  • 3xx301Moved PermanentlyThe resource has permanently moved to a new URL.
  • 3xx302FoundThe resource is temporarily located at a different URL.
  • 3xx303See OtherThe response may be found at another URL with GET.
  • 3xx304Not ModifiedThe resource has not changed since the last request.
  • 3xx305Use ProxyThe requested resource must be accessed through a proxy.
  • 3xx307Temporary RedirectThe resource is temporarily at another URL; repeat with the same method.
  • 3xx308Permanent RedirectThe resource is permanently at another URL; repeat with the same method.
  • 4xx400Bad RequestThe server cannot process the request due to a client error.
  • 4xx401UnauthorizedAuthentication is required and has failed or not been provided.
  • 4xx402Payment RequiredReserved for future use as a payment requirement.
  • 4xx403ForbiddenThe server understood the request but refuses to authorize it.
  • 4xx404Not FoundThe requested resource could not be found.
  • 4xx405Method Not AllowedThe method is not allowed for the requested resource.
  • 4xx406Not AcceptableThe requested content does not match acceptable criteria.
  • 4xx407Proxy Authentication RequiredAuthentication is required by the proxy.
  • 4xx408Request TimeoutThe server timed out waiting for the request.
  • 4xx409ConflictThe request conflicts with the current state of the resource.
  • 4xx410GoneThe resource is no longer available and will not be again.
  • 4xx411Length RequiredThe request must declare a Content-Length.
  • 4xx412Precondition FailedA precondition given in the request headers failed.
  • 4xx413Payload Too LargeThe request body is larger than the server allows.
  • 4xx414URI Too LongThe request URI is longer than the server can handle.
  • 4xx415Unsupported Media TypeThe request body format is not supported.
  • 4xx416Range Not SatisfiableThe requested range cannot be delivered.
  • 4xx417Expectation FailedThe server cannot meet the Expect header requirements.
  • 4xx418I'm a TeapotThe server refuses to brew coffee because it is a teapot.
  • 4xx421Misdirected RequestThe request was sent to a server that cannot produce a response.
  • 4xx422Unprocessable EntityThe request is well-formed but contains semantic errors.
  • 4xx423LockedThe resource is locked and cannot be modified.
  • 4xx424Failed DependencyA dependency request failed.
  • 4xx425Too EarlyThe server is unwilling to process a request that might be replayed.
  • 4xx426Upgrade RequiredThe client must switch to a different protocol.
  • 4xx428Precondition RequiredThe request must be conditional.
  • 4xx429Too Many RequestsThe user has sent too many requests in a given time.
  • 4xx431Request Header Fields Too LargeThe request headers are too large.
  • 4xx451Unavailable For Legal ReasonsThe resource is unavailable for legal reasons.
  • 5xx500Internal Server ErrorA generic error occurred on the server.
  • 5xx501Not ImplementedThe server does not support the requested method.
  • 5xx502Bad GatewayThe gateway received an invalid response from the upstream server.
  • 5xx503Service UnavailableThe server is temporarily unable to handle the request.
  • 5xx504Gateway TimeoutThe gateway timed out waiting for the upstream server.
  • 5xx505HTTP Version Not SupportedThe server does not support the HTTP version used.
  • 5xx506Variant Also NegotiatesThe server has an internal configuration error.
  • 5xx507Insufficient StorageThe server is unable to store the representation needed to complete the request.
  • 5xx508Loop DetectedThe server detected an infinite loop.
  • 5xx510Not ExtendedThe server requires further extensions to fulfil the request.
  • 5xx511Network Authentication RequiredThe client needs to authenticate to gain network access.

About this tool

Browse 1xx, 2xx, 3xx, 4xx and 5xx HTTP status codes with their standard phrases and a one-line meaning. Search by code number or keyword, click a row to copy it, and use the reference to debug API responses, server errors and redirects. The list is built in and everything runs entirely in your browser.

How to use
  1. Type a status code (404) or a keyword (forbidden, timeout, redirect).
  2. Read the matching codes, phrases and short descriptions.
  3. Click a row to copy it as "code phrase".
Does this list come from a server?

No. The status code list is built into the page and runs entirely in your browser.

Does it include non-standard codes?

It covers the common official RFC status codes from 1xx to 5xx, including the well-known 418 and 429.