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.
| 100 | Continue | The initial part of the request has been received and the client should continue with the rest of the request. |
| 101 | Switching Protocols | The server is switching protocols as requested by the client, e.g. upgrading to WebSocket. |
| 102 | Processing | The server has accepted the full request but hasn't finished processing it yet (WebDAV). |
| 103 | Early Hints | Lets the client start preloading resources while the server is still preparing the final response. |
| 200 | OK | The request succeeded, and the response body contains the requested resource. |
| 201 | Created | The request succeeded and a new resource was created as a result. |
| 202 | Accepted | The request has been accepted for processing, but the processing hasn't completed yet. |
| 203 | Non-Authoritative Information | The returned metadata isn't from the origin server but a copy from a third party or local cache. |
| 204 | No Content | The request succeeded but there is no content to return. |
| 205 | Reset Content | The request succeeded; the client should reset the document view that sent the request. |
| 206 | Partial Content | Only part of the resource is being delivered, matching a byte-range request. |
| 207 | Multi-Status | Conveys information about multiple resources in situations where multiple status codes might be appropriate (WebDAV). |
| 208 | Already Reported | The members of a WebDAV binding have already been listed in a previous part of the response. |
| 226 | IM Used | The server has fulfilled a request using one or more instance manipulations. |
| 300 | Multiple Choices | The request has more than one possible response; the client should choose one. |
| 301 | Moved Permanently | The resource has been permanently moved to a new URL given in the response. |
| 302 | Found | The resource temporarily resides at a different URL; future requests should still use the original URL. |
| 303 | See Other | The response can be found at another URL using a GET request. |
| 304 | Not Modified | The resource hasn't changed since the version specified by the client's cache headers. |
| 307 | Temporary Redirect | The resource temporarily resides at a different URL; unlike 302, the original request method must be reused. |
| 308 | Permanent Redirect | The resource has permanently moved to a new URL; the original request method must be reused. |
| 400 | Bad Request | The server couldn't understand the request due to invalid syntax. |
| 401 | Unauthorized | Authentication is required and has either failed or not been provided. |
| 402 | Payment Required | Reserved for future use; originally intended for digital payment systems. |
| 403 | Forbidden | The client doesn't have access rights to the content, even though it's understood. |
| 404 | Not Found | The server can't find the requested resource. |
| 405 | Method Not Allowed | The request method is known but not supported by the target resource. |
| 406 | Not Acceptable | The server can't produce a response matching the client's Accept headers. |
| 407 | Proxy Authentication Required | Authentication with a proxy is required before the request can proceed. |
| 408 | Request Timeout | The server timed out waiting for the request from the client. |
| 409 | Conflict | The request conflicts with the current state of the target resource. |
| 410 | Gone | The requested resource is no longer available and has been permanently removed. |
| 411 | Length Required | The server requires a Content-Length header that was missing from the request. |
| 412 | Precondition Failed | A precondition in the request headers was not met by the server. |
| 413 | Payload Too Large | The request body is larger than the server is willing or able to process. |
| 414 | URI Too Long | The requested URI is longer than the server is willing to interpret. |
| 415 | Unsupported Media Type | The request's media format isn't supported by the server. |
| 416 | Range Not Satisfiable | The requested byte range can't be fulfilled given the size of the resource. |
| 417 | Expectation Failed | The server can't meet the expectation given in the request's Expect header. |
| 418 | I'm a Teapot | A playful status defined as an April Fools' joke in RFC 2324; servers shouldn't brew coffee. |
| 421 | Misdirected Request | The request was sent to a server that can't produce a response for the target URI. |
| 422 | Unprocessable Content | The request was well-formed but contains semantic errors that prevent processing. |
| 423 | Locked | The resource being accessed is locked (WebDAV). |
| 424 | Failed Dependency | The request failed because it depended on another request that failed (WebDAV). |
| 425 | Too Early | The server is unwilling to process a request that might be replayed. |
| 426 | Upgrade Required | The client should switch to a different protocol given in the Upgrade header. |
| 428 | Precondition Required | The origin server requires the request to be conditional. |
| 429 | Too Many Requests | The client has sent too many requests in a given amount of time (rate limiting). |
| 431 | Request Header Fields Too Large | The server won't process the request because its header fields are too large. |
| 451 | Unavailable For Legal Reasons | The resource is unavailable for legal reasons, such as government-mandated censorship. |
| 500 | Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Not Implemented | The server doesn't support the functionality required to fulfill the request. |
| 502 | Bad Gateway | The server, acting as a gateway, got an invalid response from an upstream server. |
| 503 | Service Unavailable | The server isn't ready to handle the request, often due to maintenance or overload. |
| 504 | Gateway Timeout | The server, acting as a gateway, didn't get a response in time from an upstream server. |
| 505 | HTTP Version Not Supported | The HTTP version used in the request isn't supported by the server. |
| 506 | Variant Also Negotiates | The server has an internal configuration error in content negotiation. |
| 507 | Insufficient Storage | The server can't store the representation needed to complete the request (WebDAV). |
| 508 | Loop Detected | The server detected an infinite loop while processing the request (WebDAV). |
| 510 | Not Extended | Further extensions to the request are required for the server to fulfill it. |
| 511 | Network Authentication Required | The 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.