HTTP Status Code Reference
Search every standard HTTP status code.
62 statuses
| Code | Name | Category | Description |
|---|---|---|---|
| 100 | Continue | Informational | The server has received the request headers and the client should proceed to send the request body. |
| 101 | Switching Protocols | Informational | The requester has asked the server to switch protocols and the server has agreed to do so. |
| 102 | Processing | Informational | WebDAV: the server has received and is processing the request, but no response is available yet. |
| 103 | Early Hints | Informational | Used to return some response headers before final HTTP message, often to preload resources. |
| 200 | OK | Success | The request succeeded. The meaning depends on the HTTP method used. |
| 201 | Created | Success | The request succeeded and a new resource was created as a result. |
| 202 | Accepted | Success | The request has been received but not yet acted upon; processing is asynchronous. |
| 203 | Non-Authoritative Information | Success | The returned metadata is from a local or third-party copy, not the origin server. |
| 204 | No Content | Success | The request succeeded but there is no content to send in the response body. |
| 205 | Reset Content | Success | Tells the user agent to reset the document that sent the request. |
| 206 | Partial Content | Success | The server is delivering only part of the resource due to a range header sent by the client. |
| 207 | Multi-Status | Success | WebDAV: conveys information about multiple resources where several status codes might be appropriate. |
| 208 | Already Reported | Success | WebDAV: the members of a binding have already been enumerated and are not included again. |
| 226 | IM Used | Success | The server fulfilled a GET request and the response is the result of instance manipulations. |
| 300 | Multiple Choices | Redirection | The request has more than one possible response; the user or agent should choose one. |
| 301 | Moved Permanently | Redirection | The URL of the requested resource has been changed permanently. |
| 302 | Found | Redirection | The resource resides temporarily under a different URL. |
| 303 | See Other | Redirection | Directs the client to get the requested resource at another URL with a GET request. |
| 304 | Not Modified | Redirection | The response has not been modified, so the client can use its cached copy. |
| 305 | Use Proxy | Redirection | The requested resource must be accessed through the proxy given in the Location header. Deprecated. |
| 307 | Temporary Redirect | Redirection | The resource is temporarily at another URL and the method must not change. |
| 308 | Permanent Redirect | Redirection | The resource is permanently at another URL and the method must not change. |
| 400 | Bad Request | Client error | The server cannot process the request due to a client error such as malformed syntax. |
| 401 | Unauthorized | Client error | Authentication is required and has failed or has not been provided. |
| 402 | Payment Required | Client error | Reserved for future use; sometimes used by APIs to signal a payment is required. |
| 403 | Forbidden | Client error | The client is authenticated but does not have permission to access the resource. |
| 404 | Not Found | Client error | The server cannot find the requested resource. |
| 405 | Method Not Allowed | Client error | The request method is known but not supported by the target resource. |
| 406 | Not Acceptable | Client error | The resource cannot produce a response matching the Accept headers sent in the request. |
| 407 | Proxy Authentication Required | Client error | The client must first authenticate itself with the proxy. |
| 408 | Request Timeout | Client error | The server timed out waiting for the request. |
| 409 | Conflict | Client error | The request conflicts with the current state of the target resource. |
| 410 | Gone | Client error | The resource is no longer available and will not be available again. |
| 411 | Length Required | Client error | The server requires a Content-Length header that the request did not provide. |
| 412 | Precondition Failed | Client error | A precondition given in the request headers evaluated to false on the server. |
| 413 | Payload Too Large | Client error | The request entity is larger than limits defined by the server. |
| 414 | URI Too Long | Client error | The URI requested by the client is longer than the server is willing to interpret. |
| 415 | Unsupported Media Type | Client error | The media format of the requested data is not supported by the server. |
| 416 | Range Not Satisfiable | Client error | The range specified by the Range header cannot be fulfilled. |
| 417 | Expectation Failed | Client error | The expectation given in the Expect request header could not be met. |
| 418 | I'm a Teapot | Client error | The server refuses to brew coffee because it is, permanently, a teapot. |
| 421 | Misdirected Request | Client error | The request was directed at a server that is not able to produce a response. |
| 422 | Unprocessable Entity | Client error | The request was well-formed but could not be followed due to semantic errors. |
| 423 | Locked | Client error | WebDAV: the resource being accessed is locked. |
| 424 | Failed Dependency | Client error | WebDAV: the request failed because it depended on another request that failed. |
| 425 | Too Early | Client error | The server is unwilling to risk processing a request that might be replayed. |
| 426 | Upgrade Required | Client error | The client should switch to a different protocol given in the Upgrade header. |
| 428 | Precondition Required | Client error | The origin server requires the request to be conditional. |
| 429 | Too Many Requests | Client error | The user has sent too many requests in a given amount of time (rate limiting). |
| 431 | Request Header Fields Too Large | Client error | The server is unwilling to process the request because its header fields are too large. |
| 451 | Unavailable For Legal Reasons | Client error | The resource is unavailable due to legal demands such as censorship or a takedown. |
| 500 | Internal Server Error | Server error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Not Implemented | Server error | The server does not support the functionality required to fulfil the request. |
| 502 | Bad Gateway | Server error | The server, acting as a gateway, received an invalid response from the upstream server. |
| 503 | Service Unavailable | Server error | The server is not ready to handle the request, often due to maintenance or overload. |
| 504 | Gateway Timeout | Server error | The server, acting as a gateway, did not get a response from the upstream server in time. |
| 505 | HTTP Version Not Supported | Server error | The HTTP version used in the request is not supported by the server. |
| 506 | Variant Also Negotiates | Server error | Transparent content negotiation for the request results in a circular reference. |
| 507 | Insufficient Storage | Server error | WebDAV: the server is unable to store the representation needed to complete the request. |
| 508 | Loop Detected | Server error | WebDAV: the server detected an infinite loop while processing the request. |
| 510 | Not Extended | Server error | Further extensions to the request are required for the server to fulfil it. |
| 511 | Network Authentication Required | Server error | The client needs to authenticate to gain network access. |
How to use
- 1 Type a status code, such as 404, into the search box.
- 2 Or type part of a name, such as “gateway” or “rate”.
- 3 Read the matching codes, categories and descriptions.
- 4 Clear the box to browse the full list of codes again.
About HTTP Status Code Reference
The HTTP Status Code Reference is a searchable list of every standard response code, from the informational 1xx range through 2xx success, 3xx redirects, 4xx client errors and 5xx server errors.
Each entry shows the numeric code, its canonical name and a plain-English description of what it means in practice, so you can stop guessing whether a 422 is your fault or the server’s.
Working with HTTP all day means you eventually meet the obscure codes — 418, 429, 451, 511 — and remembering exactly what each one signals is harder than it should be.
Type a number to jump straight to a code, or type a word like “timeout” or “forbidden” to find it by name.
The list filters instantly as you type, with no round trip to a server.
This is handy when you are debugging an API, writing a client that needs to branch on the response, or documenting the error contract for an endpoint.
Knowing the difference between 401 and 403, or 301 and 308, often decides how your code should react.
Everything runs locally in your browser; nothing you type is sent anywhere, and the reference works even when you are offline.
FAQ
Which codes are included?
All standard registered codes from 100 to 511, including WebDAV (102, 207, 423) and rarer ones like 418, 429 and 451.
Does it call an external API?
No. The whole table ships with the page and filtering happens in your browser, so it works offline.