HTTP Status Codes Reference

Searchable list of every HTTP status code from 100 to 511 with plain-English explanations: 200, 301 vs 302 vs 307, 401 vs 403, 422, 429, 502 vs 504 and more.

Runs 100% in your browser. Nothing you paste is uploaded.

CodeStatusMeaning
100ContinueThe server received the request headers; the client should send the body.
101Switching ProtocolsThe server agrees to switch protocols, e.g. to WebSocket.
103Early HintsPreload hints sent before the final response.
200OKStandard success response.
201CreatedA new resource was created; Location header points to it.
202AcceptedRequest accepted for asynchronous processing.
203Non-Authoritative InformationPayload modified by a transforming proxy.
204No ContentSuccess with no response body.
205Reset ContentClient should reset the document view.
206Partial ContentRange request fulfilled (downloads, video streaming).
207Multi-StatusWebDAV: multiple status values in an XML body.
208Already ReportedWebDAV: members already enumerated.
226IM UsedDelta encoding applied.
300Multiple ChoicesSeveral representations available.
301Moved PermanentlyResource has a new permanent URL; SEO value transfers. Method may change to GET.
302FoundTemporary redirect; method may change to GET.
303See OtherRedirect to another resource using GET (Post/Redirect/Get pattern).
304Not ModifiedCached version is still valid (ETag / If-Modified-Since).
307Temporary RedirectTemporary redirect that preserves the HTTP method and body.
308Permanent RedirectPermanent redirect that preserves the HTTP method and body.
400Bad RequestMalformed syntax or invalid request parameters.
401UnauthorizedAuthentication required or failed (send WWW-Authenticate).
402Payment RequiredReserved; sometimes used for paywalls or quota.
403ForbiddenAuthenticated but not allowed to access the resource.
404Not FoundThe resource does not exist.
405Method Not AllowedHTTP method not supported for this resource (send Allow header).
406Not AcceptableNo representation matches the Accept headers.
407Proxy Authentication RequiredClient must authenticate with the proxy.
408Request TimeoutThe client took too long to send the request.
409ConflictRequest conflicts with the current state (e.g. version conflict, duplicate).
410GoneResource permanently removed; no forwarding address.
411Length RequiredContent-Length header is required.
412Precondition FailedIf-Match / If-Unmodified-Since precondition failed.
413Content Too LargeRequest body exceeds the server limit.
414URI Too LongThe request URL is too long.
415Unsupported Media TypeContent-Type not supported (e.g. sending XML to a JSON API).
416Range Not SatisfiableRequested byte range is outside the resource.
417Expectation FailedExpect header cannot be met.
418I'm a teapotApril Fools’ RFC 2324; some APIs use it for bot blocking.
421Misdirected RequestRequest sent to a server unable to produce a response (HTTP/2 connection reuse).
422Unprocessable ContentSyntax is fine but semantic validation failed.
423LockedWebDAV: resource is locked.
424Failed DependencyWebDAV: a dependent request failed.
425Too EarlyServer unwilling to process a request that might be replayed.
426Upgrade RequiredClient must switch to a different protocol (e.g. TLS).
428Precondition RequiredServer requires conditional requests to avoid lost updates.
429Too Many RequestsRate limit exceeded; see Retry-After.
431Request Header Fields Too LargeHeaders (often cookies) are too large.
451Unavailable For Legal ReasonsBlocked for legal reasons (censorship, court order).
500Internal Server ErrorGeneric unexpected server failure.
501Not ImplementedServer does not support the functionality.
502Bad GatewayUpstream server returned an invalid response (proxy/load balancer).
503Service UnavailableServer overloaded or down for maintenance; see Retry-After.
504Gateway TimeoutUpstream server did not respond in time.
505HTTP Version Not SupportedHTTP version not supported.
506Variant Also NegotiatesContent negotiation misconfiguration.
507Insufficient StorageWebDAV: server cannot store the representation.
508Loop DetectedWebDAV: infinite loop while processing.
510Not ExtendedFurther extensions required.
511Network Authentication RequiredCaptive portal: authenticate to gain network access.

About the HTTP Status Codes

A fast, searchable reference of HTTP response status codes as defined by RFC 9110 and related specifications. Filter by class or search by number or keyword to find the right code for your API — or to understand the one you just received.

Commonly confused codes

  • 401 vs 403 — 401 means “who are you?” (not authenticated); 403 means “I know who you are, and you can’t do this”.
  • 301/302 vs 307/308 — 307 and 308 guarantee the method and body are preserved on redirect; 301/302 may turn a POST into a GET.
  • 400 vs 422 — 400 for malformed requests, 422 for well-formed requests that fail validation.
  • 502 vs 503 vs 504 — bad upstream response, service unavailable, and upstream timeout respectively.

Features

  • All standard codes 1xx–5xx
  • Instant search by number or keyword
  • Filter by class
  • Clear explanations and REST guidance

How to use it

  1. Type a code or keyword.
  2. Filter by class to browse.

Frequently asked questions

Which status code should a REST API return on create?

201 Created with a Location header pointing to the new resource. Use 202 Accepted if creation happens asynchronously.

What does 429 mean?

The client sent too many requests and hit a rate limit. Respect the Retry-After header before retrying.

Esc