HTTP Status Codes
Searchable reference of HTTP response codes.
1xx Informational
| 100 | Continue | Client should continue with its request. |
| 101 | Switching Protocols | Server is switching protocols (e.g. WebSocket upgrade). |
| 102 | Processing | Server has received the request and is processing. |
| 103 | Early Hints | Preliminary headers before the final response. |
2xx Success
| 200 | OK | The request succeeded. |
| 201 | Created | Resource created; Location header has its URL. |
| 202 | Accepted | Request accepted but not yet processed. |
| 203 | Non-Authoritative Information | Response from a cache or proxy, not the origin. |
| 204 | No Content | Success with no response body. |
| 205 | Reset Content | Client should reset the document view. |
| 206 | Partial Content | Partial response to a Range request. |
3xx Redirection
| 300 | Multiple Choices | Several options for the requested resource. |
| 301 | Moved Permanently | Resource permanently moved to a new URL. |
| 302 | Found | Temporary redirect; keep using the original URL. |
| 303 | See Other | Fetch the resource with GET at another URL. |
| 304 | Not Modified | Cached version is still valid. |
| 307 | Temporary Redirect | Temporary redirect preserving the method. |
| 308 | Permanent Redirect | Permanent redirect preserving the method. |
4xx Client Error
| 400 | Bad Request | Malformed request the server cannot process. |
| 401 | Unauthorized | Authentication required or failed. |
| 402 | Payment Required | Reserved for future use. |
| 403 | Forbidden | Authenticated but not allowed to access. |
| 404 | Not Found | Resource does not exist. |
| 405 | Method Not Allowed | HTTP method not supported for this resource. |
| 406 | Not Acceptable | No content matching the Accept headers. |
| 407 | Proxy Authentication Required | Authenticate with the proxy first. |
| 408 | Request Timeout | Client took too long to send the request. |
| 409 | Conflict | Request conflicts with current resource state. |
| 410 | Gone | Resource permanently removed. |
| 411 | Length Required | Content-Length header is required. |
| 412 | Precondition Failed | If-Match / If-Unmodified-Since failed. |
| 413 | Payload Too Large | Request body exceeds server limits. |
| 414 | URI Too Long | Requested URL is too long. |
| 415 | Unsupported Media Type | Content type not supported. |
| 416 | Range Not Satisfiable | Requested range outside the resource size. |
| 417 | Expectation Failed | Expect header requirement cannot be met. |
| 418 | I'm a Teapot | RFC 2324 โ short and stout. |
| 422 | Unprocessable Entity | Syntactically valid but semantically wrong. |
| 425 | Too Early | Server unwilling to process a replayed request. |
| 426 | Upgrade Required | Client must switch to another protocol. |
| 428 | Precondition Required | Request must be conditional. |
| 429 | Too Many Requests | Rate limit exceeded. |
| 431 | Request Header Fields Too Large | Headers exceed the server limit. |
| 451 | Unavailable For Legal Reasons | Blocked for legal reasons. |
5xx Server Error
| 500 | Internal Server Error | Unexpected server-side error. |
| 501 | Not Implemented | Server does not support the functionality. |
| 502 | Bad Gateway | Upstream server returned an invalid response. |
| 503 | Service Unavailable | Server overloaded or down for maintenance. |
| 504 | Gateway Timeout | Upstream server did not respond in time. |
| 505 | HTTP Version Not Supported | Protocol version unsupported. |
| 507 | Insufficient Storage | Server out of storage to complete the request. |
| 508 | Loop Detected | Infinite loop while processing the request. |
| 511 | Network Authentication Required | Network login required (captive portal). |
About the HTTP Status Codes
A searchable reference of around 60 HTTP response codes organized into the five classes from 1xx informational through 5xx server errors. Each entry gives the official name and a one-line explanation of when it occurs, from 201 Created to 451 Unavailable For Legal Reasons โ including a certain RFC 2324 teapot.
How to use the HTTP Status Codes
- Type a number, name fragment or keyword in the filter box, for example 404 or redirect.
- Scroll through the matching section, color-coded by response class.
- Read the description column for the situation each code signals.
- Clear the filter to browse the full list grouped from 1xx to 5xx.
HTTP Status Codes FAQ
How is the list organized?
Codes are grouped into 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error and 5xx Server Error, each class with its own heading and color.
Can I search by keyword?
Yes. The filter matches code numbers, official names and description text, so typing cache surfaces 304 Not Modified and related entries.
Is this the complete RFC set?
It covers roughly 60 of the most practically relevant codes, including modern additions like 103 Early Hints, 425 Too Early and 451, omitting obscure or unassigned numbers.