HTTP Status Codes
betaThis free HTTP status code lookup explains every response code — search by number (e.g. 422), by class (e.g. 4xx) or by name (e.g. "gateway"). Each result shows the reason phrase, its category and a short developer-friendly description. Everything runs in your browser.
Look up any HTTP status code — search by number (e.g. 422), class (e.g. 4xx) or name (e.g. "gateway"). Everything runs in your browser.
100ContinueInformationalThe client should continue the request or ignore this response if already finished.
101Switching ProtocolsInformationalThe server is switching protocols as requested by the client (e.g. to WebSocket).
102ProcessingInformationalThe server has received and is processing the request, but no response is available yet (WebDAV).
103Early HintsInformationalUsed to return some response headers (e.g. preload links) before the final response.
200OKSuccessThe request succeeded. The meaning depends on the HTTP method used.
201CreatedSuccessThe request succeeded and a new resource was created as a result.
202AcceptedSuccessThe request has been received but not yet acted upon — processing is asynchronous.
203Non-Authoritative InformationSuccessThe returned metadata is from a copy or a third party, not the origin server.
204No ContentSuccessThe request succeeded but there is no content to send in the response body.
205Reset ContentSuccessTells the client to reset the document that sent the request (e.g. clear a form).
206Partial ContentSuccessThe server is delivering only part of the resource in response to a Range header.
207Multi-StatusSuccessConveys information about multiple resources for WebDAV requests.
208Already ReportedSuccessMembers of a WebDAV binding have already been enumerated and are not included again.
226IM UsedSuccessThe server fulfilled a GET request; the response represents one or more instance-manipulations.
300Multiple ChoicesRedirectionThe request has more than one possible response; the client should choose one.
301Moved PermanentlyRedirectionThe resource has a new permanent URL, given by the Location header.
302FoundRedirectionThe resource is temporarily at a different URL; keep using the original URL for future requests.
303See OtherRedirectionThe client should GET the resource at another URL, typically after a POST.
304Not ModifiedRedirectionThe cached version is still valid; the client can reuse it (conditional GET).
307Temporary RedirectRedirectionLike 302, but the method and body must not change when redirecting.
308Permanent RedirectRedirectionLike 301, but the method and body must not change when redirecting.
400Bad RequestClient ErrorThe server cannot process the request due to a client error (malformed syntax, invalid framing).
401UnauthorizedClient ErrorAuthentication is required and has failed or not yet been provided.
402Payment RequiredClient ErrorReserved for future use; sometimes used by APIs for billing/quota limits.
403ForbiddenClient ErrorThe server understood the request but refuses to authorize it.
404Not FoundClient ErrorThe server cannot find the requested resource. The URL is unrecognised.
405Method Not AllowedClient ErrorThe request method is known but not supported by the target resource.
406Not AcceptableClient ErrorThe resource cannot produce a response matching the Accept headers.
407Proxy Authentication RequiredClient ErrorAuthentication with a proxy is required before the request can proceed.
408Request TimeoutClient ErrorThe server timed out waiting for the request. The client may repeat it.
409ConflictClient ErrorThe request conflicts with the current state of the resource (e.g. edit conflict).
410GoneClient ErrorThe resource is permanently gone with no forwarding address.
411Length RequiredClient ErrorThe server requires a Content-Length header, which was not provided.
412Precondition FailedClient ErrorA precondition in the request headers (e.g. If-Match) was not met.
413Payload Too LargeClient ErrorThe request body is larger than the server is willing or able to process.
414URI Too LongClient ErrorThe request URI is longer than the server is willing to interpret.
415Unsupported Media TypeClient ErrorThe request body is in a format the server does not support.
416Range Not SatisfiableClient ErrorThe Range specified cannot be fulfilled — it may lie outside the resource size.
417Expectation FailedClient ErrorThe expectation in the Expect request header could not be met.
418I'm a teapotClient ErrorAn April Fools joke from RFC 2324 — the server refuses to brew coffee in a teapot.
421Misdirected RequestClient ErrorThe request was directed at a server unable to produce a response for it.
422Unprocessable EntityClient ErrorThe request was well-formed but has semantic errors and cannot be processed (common for validation).
423LockedClient ErrorThe resource being accessed is locked (WebDAV).
424Failed DependencyClient ErrorThe request failed because it depended on another request that failed (WebDAV).
425Too EarlyClient ErrorThe server is unwilling to process a request that might be replayed.
426Upgrade RequiredClient ErrorThe client should switch to a different protocol given in the Upgrade header.
428Precondition RequiredClient ErrorThe origin server requires the request to be conditional to avoid lost updates.
429Too Many RequestsClient ErrorThe client has sent too many requests in a given time (rate limiting).
431Request Header Fields Too LargeClient ErrorThe header fields are too large for the server to process.
451Unavailable For Legal ReasonsClient ErrorThe resource is unavailable due to legal demands (e.g. censorship).
500Internal Server ErrorServer ErrorThe server hit an unexpected condition that prevented it from fulfilling the request.
501Not ImplementedServer ErrorThe server does not support the functionality required to fulfil the request.
502Bad GatewayServer ErrorThe server, acting as a gateway, got an invalid response from the upstream server.
503Service UnavailableServer ErrorThe server is not ready — it may be overloaded or down for maintenance.
504Gateway TimeoutServer ErrorThe server, acting as a gateway, did not get a timely response from the upstream server.
505HTTP Version Not SupportedServer ErrorThe HTTP version used in the request is not supported by the server.
506Variant Also NegotiatesServer ErrorA content-negotiation configuration error on the server.
507Insufficient StorageServer ErrorThe server cannot store the representation needed to complete the request (WebDAV).
508Loop DetectedServer ErrorThe server detected an infinite loop while processing the request (WebDAV).
510Not ExtendedServer ErrorFurther extensions to the request are required for the server to fulfil it.
511Network Authentication RequiredServer ErrorThe client needs to authenticate to gain network access (e.g. a captive portal).
How to use HTTP Status Codes
- 1 Type a status code, class or keyword in the search box.
- 2 Try a number like 404, a class like 5xx, or a word like "timeout".
- 3 Read the name, category and meaning for each matching code.
Frequently asked questions
What does HTTP 422 mean?
422 Unprocessable Entity means the request was well-formed but has semantic errors — commonly returned by APIs when validation fails.
What are the HTTP status code classes?
1xx informational, 2xx success, 3xx redirection, 4xx client errors, and 5xx server errors. You can search a whole class like "4xx".
Is this the official list?
It covers the standard IANA-registered codes plus a few well-known extensions (like 418) with plain-language descriptions.
Does it work offline?
Yes. As a PWA it keeps working with no connection once loaded.