HTTP Status Code Lookup
Look up what any HTTP status code means, with a searchable reference table. Runs entirely in your browser.
| Code | Name | Meaning |
|---|---|---|
| 100 | Continue | The initial part of a request has been received and the client should continue with the rest of it. |
| 101 | Switching Protocols | The server is switching protocols as requested by the client, e.g. to WebSocket. |
| 200 | OK | The request succeeded. The meaning depends on the HTTP method used. |
| 201 | Created | The request succeeded and a new resource was created as a result. |
| 202 | Accepted | The request has been received but not yet acted upon. |
| 204 | No Content | The request succeeded but there is no content to send in response. |
| 206 | Partial Content | Used for range requests when the client requested only part of a resource. |
| 301 | Moved Permanently | The resource has been permanently moved to a new URL, given in the Location header. |
| 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 | Tells the client the cached response is still valid; there is no need to retransmit the resource. |
| 307 | Temporary Redirect | Like 302, but guarantees the method and body will not change on the redirected request. |
| 308 | Permanent Redirect | Like 301, but guarantees the method and body will not change on the redirected request. |
| 400 | Bad Request | The server cannot process the request due to a client error, e.g. malformed syntax. |
| 401 | Unauthorized | The request lacks valid authentication credentials for the target resource. |
| 403 | Forbidden | The server understood the request but refuses to authorize it. |
| 404 | Not Found | The server cannot find the requested resource. |
| 405 | Method Not Allowed | The request method is known but not supported by the target resource. |
| 406 | Not Acceptable | No content matching the criteria given in the request’s Accept headers is available. |
| 408 | Request Timeout | The server timed out waiting for the request. |
| 409 | Conflict | The request conflicts with the current state of the target resource. |
| 410 | Gone | The requested resource is no longer available and will not be available again. |
| 411 | Length Required | The server refuses the request because the Content-Length header was not defined. |
| 413 | Payload Too Large | The request body is larger than the server is willing or able to process. |
| 414 | URI Too Long | The URI requested by the client is longer than the server is willing to interpret. |
| 415 | Unsupported Media Type | The media format of the requested data is not supported by the server. |
| 418 | I’m a Teapot | A well-known April Fools’ joke from RFC 2324; some servers use it as an easter egg. |
| 422 | Unprocessable Entity | The request was well-formed but contains semantic errors, e.g. failed validation. |
| 425 | Too Early | The server is unwilling to process a request that might be replayed. |
| 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 is unwilling to process the request because its header fields are too large. |
| 451 | Unavailable For Legal Reasons | The resource is unavailable due to a legal demand, e.g. government-mandated blocking. |
| 500 | Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | Not Implemented | The request method is not supported by the server and cannot be handled. |
| 502 | Bad Gateway | The server, acting as a gateway, received an invalid response from an upstream server. |
| 503 | Service Unavailable | The server is not ready to handle the request, often due to maintenance or overload. |
| 504 | Gateway Timeout | The server, acting as a gateway, did not get a response in time from an upstream server. |
| 505 | HTTP Version Not Supported | The HTTP version used in the request is not supported by the server. |
No status codes matched your search.
Link to this tool
Copy this HTML to cite this tool from your own site or article.
About HTTP Status Code Lookup
HTTP Status Code Lookup provides an interactive reference table explaining HTTP response status codes, causes, and standard client resolution steps.
How to use HTTP Status Code Lookup
- Type an HTTP status code (such as 404, 500, or 301) into search.
- Filter codes by category (1xx Info, 2xx Success, 3xx Redirect, 4xx Client Error, 5xx Server Error).
- Read standard HTTP specifications, common causes, and developer debugging advice.
Examples
Code: 404 Not Found Meaning: The requested server resource could not be found at the targeted URI.
FAQ
Are unofficial HTTP status codes included?
Yes. Common Cloudflare and AWS custom status codes (like 520 or 429 rate limit) are documented alongside IETF standards.
Can I filter codes by HTTP category?
Yes. You can filter by response status classes.
You might also want ...
HTTP & API
HTTP Headers Parser
Paste raw HTTP request or response headers to see them as a table with plain-language explanations.
HTTP & API
MIME Type Lookup
Look up the MIME type for any file extension, with a searchable reference table.
HTTP & API
cURL Code Converter
Convert cURL commands to Fetch, Axios, Python, PHP, or Go code entirely in your browser.