HTTP status codes
Look up HTTP status codes: what each one means and which RFC section defines it.
48 status codes. Names follow RFC 9110.
| Code | Name | Meaning | Defined in |
|---|---|---|---|
| 100 | Continue | The initial part of the request was received; the client should continue and send the body. | RFC 9110 §15.2.1 |
| 101 | Switching Protocols | The server agrees to switch to the protocol named in the Upgrade header, for example WebSocket. | RFC 9110 §15.2.2 |
| 103 | Early Hints | Provisional response with Link headers so the client can start preloading resources before the final response. | RFC 8297 §2 |
| 200 | OK | The request succeeded; the content depends on the method (the resource for GET, the result for POST). | RFC 9110 §15.3.1 |
| 201 | Created | The request succeeded and created a new resource, usually identified by a Location header. | RFC 9110 §15.3.2 |
| 202 | Accepted | The request was accepted for processing, but processing has not finished. | RFC 9110 §15.3.3 |
| 203 | Non-Authoritative Information | The request succeeded, but a transforming proxy changed the content from the origin's 200 response. | RFC 9110 §15.3.4 |
| 204 | No Content | The request succeeded and there is no content to send in the response body. | RFC 9110 §15.3.5 |
| 205 | Reset Content | The request succeeded; the client should reset the document view that sent the request, for example clear a form. | RFC 9110 §15.3.6 |
| 206 | Partial Content | The server is returning only the byte range requested with a Range header. | RFC 9110 §15.3.7 |
| 300 | Multiple Choices | The resource has several representations and the client may choose one. | RFC 9110 §15.4.1 |
| 301 | Moved Permanently | The resource has a new permanent URI; clients may change the method from POST to GET on the redirect. | RFC 9110 §15.4.2 |
| 302 | Found | The resource is temporarily at a different URI; keep using the original URI for future requests. | RFC 9110 §15.4.3 |
| 303 | See Other | The response to the request is at another URI, which should be fetched with GET. | RFC 9110 §15.4.4 |
| 304 | Not Modified | A conditional GET found the cached copy still valid, so no body is sent. | RFC 9110 §15.4.5 |
| 305 | Use Proxy | Deprecated: the resource was meant to be accessed through a proxy. Clients must not rely on it. | RFC 9110 §15.4.6 |
| 306 | (Unused) | Reserved; it was used in an earlier HTTP draft and has no meaning now. | RFC 9110 §15.4.7 |
| 307 | Temporary Redirect | Temporary redirect that must repeat the request with the same method and body. | RFC 9110 §15.4.8 |
| 308 | Permanent Redirect | Permanent redirect that must repeat the request with the same method and body. | RFC 9110 §15.4.9 |
| 400 | Bad Request | The server cannot process the request because of a client error such as malformed syntax. | RFC 9110 §15.5.1 |
| 401 | Unauthorized | The request lacks valid authentication credentials; the response carries a WWW-Authenticate challenge. | RFC 9110 §15.5.2 |
| 402 | Payment Required | Reserved for future use; some services use it to signal a payment or quota problem. | RFC 9110 §15.5.3 |
| 403 | Forbidden | The server understood the request but refuses to authorize it; authenticating again will not help. | RFC 9110 §15.5.4 |
| 404 | Not Found | The server has no current representation for the target resource, or will not say that it exists. | RFC 9110 §15.5.5 |
| 405 | Method Not Allowed | The method is known but not supported for this resource; the Allow header lists the supported ones. | RFC 9110 §15.5.6 |
| 406 | Not Acceptable | No representation matches the client's Accept headers. | RFC 9110 §15.5.7 |
| 407 | Proxy Authentication Required | Like 401, but the client must authenticate with the proxy first. | RFC 9110 §15.5.8 |
| 408 | Request Timeout | The server gave up waiting for the client to finish sending the request. | RFC 9110 §15.5.9 |
| 409 | Conflict | The request conflicts with the current state of the resource, for example an edit conflict. | RFC 9110 §15.5.10 |
| 410 | Gone | The resource used to exist and has been removed permanently, with no forwarding address. | RFC 9110 §15.5.11 |
| 411 | Length Required | The server requires a Content-Length header on the request. | RFC 9110 §15.5.12 |
| 412 | Precondition Failed | A condition in the request headers, such as If-Match, evaluated to false. | RFC 9110 §15.5.13 |
| 413 | Content Too Large | The request body is larger than the server is willing to process (formerly Payload Too Large). | RFC 9110 §15.5.14 |
| 414 | URI Too Long | The request target is longer than the server is willing to interpret. | RFC 9110 §15.5.15 |
| 415 | Unsupported Media Type | The request body is in a format or content coding the server does not support. | RFC 9110 §15.5.16 |
| 416 | Range Not Satisfiable | None of the ranges in the Range header overlap the resource's current extent. | RFC 9110 §15.5.17 |
| 417 | Expectation Failed | The server cannot meet the requirement of the Expect request header. | RFC 9110 §15.5.18 |
| 418 | (Unused) | Reserved. "I'm a teapot" comes from the April Fools RFC 2324 and is not part of HTTP semantics. | RFC 9110 §15.5.19 |
| 421 | Misdirected Request | The request was sent to a server that cannot produce a response for that scheme and authority. | RFC 9110 §15.5.20 |
| 422 | Unprocessable Content | The syntax and content type are fine, but the instructions in the content cannot be processed (formerly Unprocessable Entity). | RFC 9110 §15.5.21 |
| 426 | Upgrade Required | The server refuses the request with the current protocol and names the one the client must upgrade to. | RFC 9110 §15.5.22 |
| 429 | Too Many Requests | The client has sent too many requests in a given time; a Retry-After header may say when to retry. | RFC 6585 §4 |
| 500 | Internal Server Error | The server hit an unexpected condition that stopped it from fulfilling the request. | RFC 9110 §15.6.1 |
| 501 | Not Implemented | The server does not support the functionality required for this request or method. | RFC 9110 §15.6.2 |
| 502 | Bad Gateway | A gateway or proxy received an invalid response from the upstream server. | RFC 9110 §15.6.3 |
| 503 | Service Unavailable | The server is temporarily overloaded or down for maintenance; Retry-After may say when it returns. | RFC 9110 §15.6.4 |
| 504 | Gateway Timeout | A gateway or proxy did not get a timely response from the upstream server. | RFC 9110 §15.6.5 |
| 505 | HTTP Version Not Supported | The server does not support the HTTP version used in the request. | RFC 9110 §15.6.6 |
How it works
The list is built into the page and searched locally. Type a number or the start of one (40 shows 400–418), a class such as 4xx, or words from the name or meaning. Names and sections follow RFC 9110 (June 2022), which obsoletes RFC 7231; 103 is defined in RFC 8297 and 429 in RFC 6585, neither of which is part of RFC 9110. Codes registered elsewhere (for example 207, 226, 451 and 511) are not listed here.
Runs in your browser; nothing is uploaded.
FAQ
What is the difference between 401 and 403?
401 means the request has no valid credentials and the client may retry with proper ones. 403 means the server understood who you are, or does not care, and refuses anyway, so sending the same credentials again will not help.
Should I use 301 or 308 for a permanent redirect?
Both are permanent. 301 lets old clients change a POST into a GET when following the redirect; 308 requires the method and body to be repeated unchanged. Use 308 (or 307 for temporary) when the method must be preserved, and 301 for ordinary page moves.
Is 418 I'm a teapot a real status code?
It comes from the 1998 April Fools RFC 2324. RFC 9110 reserves 418 as unused, so it should not be sent as a real response, although some servers return it deliberately.
Related developer tools
Bookmark this page for next time, or copy its link. Shared links contain no working input.
Link to this tool: https://www.toolpick.dev/free-tools/http-status-codes