Browse, search, and filter every standard HTTP status code with plain-English descriptions and real-world use cases.
No codes match your search.
Copied!
Summary
Browse, search, and filter every standard HTTP status code with plain-English descriptions and real-world use cases.
How it works
All status codes load instantly in the browser — no server request needed.
Type a code number or keyword in the search box to filter the list in real time.
Click a class badge (1xx, 2xx, 3xx, 4xx, 5xx) to show only that category.
Click any code row to expand it and read the full description and use cases.
Click the copy icon next to a code to copy the numeric code to your clipboard.
Use cases
Quickly look up an unfamiliar status code while debugging an API.
Choose the correct response code when building a REST or HTTP API.
Review which codes an HTTP client should retry automatically.
Explain status codes to teammates or clients in plain language.
Check whether a code is a client-side (4xx) or server-side (5xx) problem.
Find the right redirect code (301 vs 302 vs 307 vs 308) for your use case.
Reference standard codes during code reviews or documentation.
Learn HTTP semantics without leaving your browser.
Frequently Asked Questions
301 Moved Permanently tells clients and search engines the resource has moved forever; the new URL should replace the old one in bookmarks and indexes. 302 Found is a temporary redirect — the original URL remains canonical and should not be replaced.
400 Bad Request covers malformed syntax (e.g. broken JSON). 422 Unprocessable Entity is for well-formed requests that fail semantic validation (e.g. a valid JSON body where a required field contains an out-of-range value). Many REST APIs use 400 for both; 422 is preferred when the parsing succeeded but the data is logically invalid.
401 Unauthorized means the request lacks valid authentication credentials — the user should log in or provide a token. 403 Forbidden means the server understood the request and the user is authenticated, but they do not have permission to access the resource.
503 Service Unavailable and 429 Too Many Requests (technically 4xx) are the most common retryable codes; check the Retry-After header for backoff guidance. 502 Bad Gateway and 504 Gateway Timeout are also often transient. 500 Internal Server Error may or may not be retryable depending on whether it is caused by a temporary failure.
204 No Content is the conventional response for a successful DELETE when there is nothing meaningful to return in the body. 200 OK is also acceptable if you return the deleted resource or a confirmation message in the body.
418 I'm a Teapot is an April Fools' joke from RFC 2324 (1998). It was never intended for real use but has been preserved by IANA. Some developers return it as a humorous Easter egg.