HTTP Status Code Lookup — Reference Table
Search 50+ HTTP status codes with names, meanings, and category groupings. Click any card to copy the code.
53 of 53 codes shown
1xx Informational
(4)2xx Success
(7)3xx Redirection
(7)4xx Client Error
(26)5xx Server Error
(9)A searchable reference for HTTP status codes. Filter by code or name, read a one-sentence description, and click any card to copy the number. Codes are grouped into 1xx, 2xx, 3xx, 4xx, and 5xx tiers with color-coded borders so you can spot the category at a glance.
HTTP status codes are the vocabulary your API speaks. Knowing when to send a 400 versus a 422, or a 301 versus a 308, makes the difference between a client that recovers gracefully and one that retries forever. This reference lists the 50 or so codes you will actually encounter in real work, grouped by tier, with descriptions written to answer the question a developer is actually asking when they look one up.
The categories follow the RFC structure. 1xx informational codes like 100 Continue and 101 Switching Protocols show up in protocol negotiation. 2xx success codes cover everything from plain 200 OK to 204 No Content (often used on DELETE) and 206 Partial Content (for Range requests). 3xx redirection includes the permanent/temporary split (301/302) and the method-preserving variants (307/308). 4xx client errors are where most API bugs live: 400, 401, 403, 404, 409, 422, and the widely used 429 Too Many Requests. 5xx is server errors, with 500 as the generic catchall and 502/503/504 as the gateway/availability trio. Click any card to copy just the code number.
- 1
Search by code or name
Type a code fragment like 40 to narrow to the 4xx block, or a word like timeout to jump to 408 and 504.
- 2
Scan by category
Codes are grouped into informational, success, redirection, client error, and server error tiers with color-coded borders (sky, emerald, violet, amber, red).
- 3
Copy the code
Click any card to copy just the status number to your clipboard — useful when writing tests, switch statements, or docs.
API design decisions
Pick the right code for a new endpoint: 201 for create, 204 for delete, 409 for conflict, 422 for validation failure.
Debugging production errors
Look up an unfamiliar code from logs or a status page to understand what your upstream is reporting.
Writing tests
Copy codes into assertions without context-switching to an external tab.
Teaching HTTP
Point someone new to a concise, grouped reference instead of a long MDN article.
Is 422 the same as 400?
They overlap in practice. 400 means the request itself is malformed (broken JSON, wrong types). 422 means the syntax is valid but the content failed business-rule validation. Many frameworks use 422 for form validation errors.
When should I use 301 versus 308?
Both are permanent redirects. 301 historically allowed clients to change POST to GET on the redirect. 308 strictly preserves the method and body, which is what you usually want for API redirects.
Is 418 a real status?
418 I'm a teapot was defined as an April Fools' joke in RFC 2324 but is registered and widely implemented. Some APIs use it humorously; most production code does not return it.
Why do I not see every code from the IANA registry?
This reference focuses on codes you actually encounter in web and API work. Rare codes from WebDAV extensions and specialized protocols are omitted to keep the list scannable.
Is anything tracked when I search?
No. The list is embedded in the page and filtered in your browser. Searches never leave your device.