HTTP Status Code Cheat Sheet
A searchable reference of 22 common HTTP status codes with bilingual explanations, grouped from 1xx to 5xx and color coded by category, filterable by number or by keyword.
FreeOnline Tool
Loading…
How to Use
- The page lists all of the built-in common HTTP status codes with their explanations by default
- Type a status number (such as 404), an English phrase (such as not found) or a Chinese description into the search box to filter the list in real time
Features
- 22 common HTTP status codes covering all five groups: 1xx informational, 2xx success, 3xx redirection, 4xx client errors and 5xx server errors
- Every code comes with an English and Chinese explanation, and a category tag color coded gray, green, blue, yellow or red
- Live search filtering by status number, English phrase or Chinese description
Use Cases
Checking a status code returned by an API
When an endpoint returns a code you cannot quite remember, look up its exact meaning in seconds.
Triaging page or API failures
When a browser or packet capture shows an HTTP status code, use the color grouping to tell immediately whether the fault is on the client or the server side.
Learning the HTTP status code system
Browse the 1xx to 5xx groups in one place to build an overall picture of how HTTP status codes are organized.
Writing API documentation
Look up the official English wording of a standard status code so your interface documentation stays accurate and consistent.
FAQ
What do the tag colors mean?
Gray marks 1xx informational responses, green 2xx success, blue 3xx redirection, yellow 4xx client errors and red 5xx server errors, matching the standard grouping in the HTTP specification.
What is status code 418 and why is it unusual?
418 I'm a Teapot comes from RFC 2324, an April Fools' joke published in 1998. It is non-standard and virtually never used in production; it is included here purely as a curiosity.
What can I search by?
You can search by the status number (such as 404), the standard English phrase (such as not found, case-insensitive) or the Chinese description. A match on any of them brings up the entry.
Does the list cover every HTTP status code?
No. It contains the 22 codes you meet most often in day-to-day development, not the complete IANA registry, so the list stays practical for debugging.