HTTP Status Code Lookup
Search or browse every standard HTTP status code, from the familiar 404 to obscure 5xx variants, with plain-language descriptions and the category each code belongs to.
Using the HTTP Status Code Lookup: step by step
- Type a code number or keyword into the search box.
- Matching codes and their meanings appear as you type.
- Browse by category: informational, success, redirect, client error, and server error.
- Click a code to expand its full description and typical causes.
What people use the HTTP Status Code Lookup for
- Diagnosing why a page or API request failed during development.
- Writing accurate error documentation or API references.
- Learning what less common codes like 418 or 507 actually mean.
- Deciding which status code your own API should return for a case.
Inside the HTTP Status Code Lookup
The reference covers the standard 1xx through 5xx families defined by the HTTP specification, including well-known extensions in common use. Each entry summarizes what the code signals, who is responsible for the outcome, and typical scenarios that produce it. The entire lookup is a static reference that runs offline in your browser, which makes it handy for on-call shifts or studying.
Limitations worth knowing
Meanings can vary slightly between APIs, since services sometimes repurpose codes for their own semantics; treat the general meaning as a baseline.
HTTP Status Code Lookup FAQ
What is the difference between 401 and 403?
401 means unauthenticated, credentials are missing or invalid; 403 means authenticated but not permitted to access the resource.
Which codes matter for SEO?
200, 301, 302, 404, and 410 are the ones most often discussed for crawling and indexing behavior.
Does 418 exist as a real code?
Yes, it began as an April Fools joke in an old specification but appears in some real systems as an easter egg.
Last reviewed: October 2026.