HTTP Status Codes
Search and look up HTTP status codes and their meanings.
The server received the request headers and the client should proceed to send the body.
The server is switching protocols as requested by the client.
The request succeeded. The meaning depends on the HTTP method used.
The request succeeded and a new resource was created as a result.
The request was received but not yet acted upon — processing is asynchronous.
The request succeeded but there is no content to send in the response body.
The server is delivering only part of the resource due to a range header.
The resource has permanently moved to a new URL; update your links.
The resource is temporarily at a different URL; keep using the original.
The cached version is still valid; no need to re-download.
Like 302 but the method must not change on the redirect.
Like 301 but the method must not change on the redirect.
The server cannot process the request due to a client error (malformed syntax).
Authentication is required and has failed or not been provided.
The server understood the request but refuses to authorize it.
The server cannot find the requested resource.
The request method is not supported for the target resource.
The server timed out waiting for the request.
The request conflicts with the current state of the resource.
The resource is permanently gone and no forwarding address is known.
An April Fools joke from RFC 2324 — the server refuses to brew coffee.
The request was well-formed but has semantic errors (often validation).
The user has sent too many requests in a given time (rate limiting).
A generic error — the server encountered an unexpected condition.
The server does not support the functionality required to fulfill the request.
A server acting as a gateway received an invalid response from upstream.
The server is not ready — overloaded or down for maintenance.
A gateway server did not get a timely response from the upstream server.
Related Tools
0 comments
How it works
Type a status code or a keyword and the tool filters a built-in list of HTTP response codes, showing each code's name, category (informational, success, redirection, client error, server error), and a short explanation of when it is used. Because the full list is bundled in the page, lookups are instant and work offline. It is a quick reference for debugging APIs and reading server responses. Nothing is sent anywhere.
Common use cases
- Looking up what a 422 or 418 response means while debugging.
- Checking the difference between 301 and 302 redirects.
- Finding the right status code to return from an API.
Frequently asked questions
What do the code categories mean?
1xx are informational, 2xx mean success, 3xx are redirects, 4xx are client errors (the request was wrong), and 5xx are server errors (the server failed). The first digit tells you the class.
What is the difference between 301 and 302?
301 is a permanent redirect — clients and search engines should update to the new URL. 302 is temporary, so the original URL should still be used in future. The tool explains both.
Does this need an internet connection?
No. The full list is bundled into the page, so lookups are instant and work offline.