HTTP Status Reference
Enter a numeric code in the Status code field—404 is the default sample—then click Lookup. A hit shows code and name like 404 — Not Found; unknown codes return an error naming the value you typed.
200 OK 201 Created 204 No Content 301 Moved Permanently 302 Found 304 Not Modified 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 405 Method Not Allowed 429 Too Many Requests 500 Internal Server Error 502 Bad Gateway 503 Service Unavailable
About this tool
The tool ships a curated map of common HTTP statuses from 200 through 503, including redirects (301, 302, 304), client errors (400–429), and server failures (500–503). Below the result div, a muted pre block lists every supported code and phrase for quick scanning.
How to use
- Open the reference: Load the page with the Status code input, Lookup button, result div, and code list pre.
- Enter a code: Type a three-digit status such as 404, 500, or 301.
- Click Lookup: Press Lookup to match the code against the built-in map.
- Read the answer: Copy the formatted code — name line from the result div or pick from the list below.
Common use cases
- Decode a status from browser DevTools Network tab during API debugging.
- Teach students the difference between 401 Unauthorized and 403 Forbidden.
- Confirm whether 204 No Content is in the supported list before writing docs.
- Refresh memory on 429 Too Many Requests while tuning rate limits.
Tips
- Only listed codes resolve; anything else shows Unknown or unsupported code with your input echoed.
- Scroll the reference pre block under the result to compare similar codes like 301 vs 302.
FAQ
Which codes are supported?
200, 201, 204, 301, 302, 304, 400, 401, 403, 404, 405, 429, 500, 502, and 503.
What if I enter an empty code?
Lookup shows Enter a status code until you provide a value.
Why does 418 not work?
Only the predefined map entries resolve; unlisted codes trigger Unknown or unsupported code.
Does Lookup call the internet?
No. Matching happens locally against the embedded code table.