🌐HTTP Status Code Reference
Search the meaning of HTTP response codes 100–599. RFC standard codes plus common non-standard ones (418, 429, etc.). Useful for API debugging, error screen analysis, backend response design, interview prep, and web dev study.
How to use
- 1Search by code number or keyword.
- 2Each code's meaning and usage example are displayed.
FAQ
Which codes are included?+
RFC 9110 standard codes plus common non-standard ones (418 I'm a teapot, 429 Too Many Requests, etc.).
2xx vs 3xx vs 4xx vs 5xx?+
2xx success, 3xx redirect, 4xx client error, 5xx server error. Generally, 4xx is the user/request, 5xx is the server itself.
401 vs 403?+
401 (Unauthorized) means no authentication (login required); 403 (Forbidden) means authenticated but no permission. Don't confuse them.
Is 404 the most common?+
404 is the most user-visible error, but 502/503/504 gateway errors are more painful operationally.
Why is 418 Teapot a thing?+
Originally an April Fools' RFC from 1998, it stuck around as a standard. Rarely used in practice, but some services use it as a joke.
Is an empty 200 response okay?+
Fine from HTTP's perspective, but business logic may treat empty as a problem. Check the body too, not just the code.