HTTP Status Code Reference

Look up what HTTP status codes like 404, 500, and 301 mean, free online with no installation required. Understand an API response code, choose the right redirect status, or tell 401 and 403 apart while debugging authentication.

1xx Informational
100ContinueThe initial part of the request has been received and the client should continue with the rest of the request.
101Switching ProtocolsThe server is switching protocols as requested by the client, e.g. upgrading to WebSocket.
102ProcessingThe server has accepted the full request but hasn't finished processing it yet (WebDAV).
103Early HintsLets the client start preloading resources while the server is still preparing the final response.
2xx Success
200OKThe request succeeded, and the response body contains the requested resource.
201CreatedThe request succeeded and a new resource was created as a result.
202AcceptedThe request has been accepted for processing, but the processing hasn't completed yet.
203Non-Authoritative InformationThe returned metadata isn't from the origin server but a copy from a third party or local cache.
204No ContentThe request succeeded but there is no content to return.
205Reset ContentThe request succeeded; the client should reset the document view that sent the request.
206Partial ContentOnly part of the resource is being delivered, matching a byte-range request.
207Multi-StatusConveys information about multiple resources in situations where multiple status codes might be appropriate (WebDAV).
208Already ReportedThe members of a WebDAV binding have already been listed in a previous part of the response.
226IM UsedThe server has fulfilled a request using one or more instance manipulations.
3xx Redirection
300Multiple ChoicesThe request has more than one possible response; the client should choose one.
301Moved PermanentlyThe resource has been permanently moved to a new URL given in the response.
302FoundThe resource temporarily resides at a different URL; future requests should still use the original URL.
303See OtherThe response can be found at another URL using a GET request.
304Not ModifiedThe resource hasn't changed since the version specified by the client's cache headers.
307Temporary RedirectThe resource temporarily resides at a different URL; unlike 302, the original request method must be reused.
308Permanent RedirectThe resource has permanently moved to a new URL; the original request method must be reused.
4xx Client Error
400Bad RequestThe server couldn't understand the request due to invalid syntax.
401UnauthorizedAuthentication is required and has either failed or not been provided.
402Payment RequiredReserved for future use; originally intended for digital payment systems.
403ForbiddenThe client doesn't have access rights to the content, even though it's understood.
404Not FoundThe server can't find the requested resource.
405Method Not AllowedThe request method is known but not supported by the target resource.
406Not AcceptableThe server can't produce a response matching the client's Accept headers.
407Proxy Authentication RequiredAuthentication with a proxy is required before the request can proceed.
408Request TimeoutThe server timed out waiting for the request from the client.
409ConflictThe request conflicts with the current state of the target resource.
410GoneThe requested resource is no longer available and has been permanently removed.
411Length RequiredThe server requires a Content-Length header that was missing from the request.
412Precondition FailedA precondition in the request headers was not met by the server.
413Payload Too LargeThe request body is larger than the server is willing or able to process.
414URI Too LongThe requested URI is longer than the server is willing to interpret.
415Unsupported Media TypeThe request's media format isn't supported by the server.
416Range Not SatisfiableThe requested byte range can't be fulfilled given the size of the resource.
417Expectation FailedThe server can't meet the expectation given in the request's Expect header.
418I'm a TeapotA playful status defined as an April Fools' joke in RFC 2324; servers shouldn't brew coffee.
421Misdirected RequestThe request was sent to a server that can't produce a response for the target URI.
422Unprocessable ContentThe request was well-formed but contains semantic errors that prevent processing.
423LockedThe resource being accessed is locked (WebDAV).
424Failed DependencyThe request failed because it depended on another request that failed (WebDAV).
425Too EarlyThe server is unwilling to process a request that might be replayed.
426Upgrade RequiredThe client should switch to a different protocol given in the Upgrade header.
428Precondition RequiredThe origin server requires the request to be conditional.
429Too Many RequestsThe client has sent too many requests in a given amount of time (rate limiting).
431Request Header Fields Too LargeThe server won't process the request because its header fields are too large.
451Unavailable For Legal ReasonsThe resource is unavailable for legal reasons, such as government-mandated censorship.
5xx Server Error
500Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
501Not ImplementedThe server doesn't support the functionality required to fulfill the request.
502Bad GatewayThe server, acting as a gateway, got an invalid response from an upstream server.
503Service UnavailableThe server isn't ready to handle the request, often due to maintenance or overload.
504Gateway TimeoutThe server, acting as a gateway, didn't get a response in time from an upstream server.
505HTTP Version Not SupportedThe HTTP version used in the request isn't supported by the server.
506Variant Also NegotiatesThe server has an internal configuration error in content negotiation.
507Insufficient StorageThe server can't store the representation needed to complete the request (WebDAV).
508Loop DetectedThe server detected an infinite loop while processing the request (WebDAV).
510Not ExtendedFurther extensions to the request are required for the server to fulfill it.
511Network Authentication RequiredThe client needs to authenticate to gain network access, often shown by captive portals.

Usage examples

Understanding what an API response status code means

Search for an unfamiliar code like 422 returned by a backend API to quickly see what it means and how to respond to it.

Choosing the right redirect code

Check the difference between 301 and 308, or 302 and 307, to decide which redirect status to use when moving a URL.

Looking up a code seen in the browser's network tab

Search for a status code you noticed in your browser's dev tools network tab to understand why a request failed.

Telling 401 and 403 apart while debugging auth

Search for '401' and '403' side by side to see the exact distinction: 401 means the request has no valid credentials, while 403 means the credentials are valid but the user isn't allowed to access the resource.

Deciding how to handle rate limiting in a client

Look up 429 to confirm it means too many requests in a given time, and check whether your API's response includes a Retry-After header you should respect before retrying.

Frequently asked questions

Are all the codes on this list actually standard?

Yes — this list only includes codes registered in IANA's official HTTP status code registry that are in common use. Non-standard or unofficial codes aren't included.

Why are codes like 305 and 306 missing?

305 (Use Proxy) is effectively deprecated for security reasons, and 306 is unused. Since you're very unlikely to encounter either in practice, the list focuses on codes you'll actually run into.

Do these descriptions replace the full spec or legal advice?

No — these are short summaries meant for quick lookup. If exact behavior matters, check the relevant RFC or the current HTTP specification directly.

What's the real difference between 401 and 403?

401 Unauthorized actually means "unauthenticated" — the server doesn't know who you are, usually because credentials are missing or invalid. 403 Forbidden means the server knows who you are but you don't have permission to access that resource, even with valid credentials.

Should I use 404 or 410 when a resource is gone?

Use 404 Not Found when a resource doesn't exist and you don't know (or don't want to say) whether it ever did. Use 410 Gone when you know for certain a resource used to exist but has been permanently removed — it signals clients and search engines to stop requesting it.

When should I use 301 vs 302 vs 307 vs 308 for a redirect?

301 and 308 are permanent redirects; 302 and 307 are temporary. The difference between the older pair (301/302) and newer pair (307/308) is that 307 and 308 guarantee the request method and body are preserved on the redirected request, while 301 and 302 historically allow clients to change a POST to a GET.

Why did my server return a 500 instead of a more specific code?

500 Internal Server Error is a generic catch-all for unexpected server-side failures, like an unhandled exception. It usually means the server's error handling didn't map the failure to a more specific 4xx or 5xx code — check your server logs for the actual cause.