How to use
- Type a code (
404), the first digits (40), a class (4xx), an English name (not found) or a Korean word into the search box. With an empty box you get the whole list, grouped by class. - Use the class buttons (1xx to 5xx) above to narrow the list.
- Click a code to open its meaning, when you see it, how to fix it (for visitors and for developers) and the RFC it comes from.
- Copy link copies an address such as
#404that opens that code directly, which is handy in team docs and issues.
Overview by class
| Class | Meaning | Codes in this tool |
|---|---|---|
| 1xx | Informational: interim response, the request was received and work continues | 4 |
| 2xx | Success: the request was received and handled | 10 |
| 3xx | Redirection: more action is needed to complete the request | 9 |
| 4xx | Client error: something is wrong with the request itself | 31 |
| 5xx | Server error: the server failed to handle a valid request | 18 |
The list covers the standard (IANA registry) codes plus a few unofficial ones you meet often (nginx 444 and 499, Cloudflare 520–526), and unofficial codes show their source. Names and meanings follow RFC 9110 (HTTP Semantics). Note that 413 was Payload Too Large and is now Content Too Large, and 422 changed from Unprocessable Entity to Unprocessable Content.
Codes that are easy to mix up
401 vs 403
| Code | Meaning | Does logging in change it? |
|---|---|---|
| 401 | Credentials missing or invalid (WWW-Authenticate required) |
It can |
| 403 | The server knows who you are, but you are not allowed | It does not |
301, 302, 307, 308
| Code | Move | Method |
|---|---|---|
| 301 | Permanent | A POST may become a GET |
| 302 | Temporary | A POST may become a GET |
| 307 | Temporary | Kept as is |
| 308 | Permanent | Kept as is |
After a form post, 303 (always a GET) is the code for sending users to a result page.
404 vs 410: 404 only says nothing is there now and does not say whether that is permanent. 410 says the resource was removed on purpose and for good.
502, 503, 504: 502 means the upstream server sent a bad response, 503 means the server is overloaded or in maintenance and cannot serve the request, and 504 means the upstream server did not answer in time. All three are common behind a proxy or gateway.
The SEO angle
- Use 301 or 308 when an address moves for good. If 302 or 307 stays in place for a long time, search engines may keep treating the old address as the main one.
- A soft 404 is a page that shows a “not found” screen but sends status 200. Search engines can mistake the empty page for a real one, so a page that truly does not exist should return 404 or 410.
- During maintenance send 503 with
Retry-Afterto say the outage is temporary. If 5xx errors go on for a long time, pages can drop out of the index.
Codes that are safe to retry
This tool marks 408, 425, 429, 502, 503 and 504 as “trying again later may succeed”. 429 and 503 can carry a Retry-After header with a wait time (seconds or a date): honour it when present, otherwise back off exponentially (1 s, 2 s, 4 s and so on). 4xx codes that need the request itself to change, such as 400, 401, 403, 404 and 422, give the same answer however often you repeat them.
Codes that are cacheable by default (RFC 9110) are 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414 and 501, and the tool labels them.
418 is a joke from the April Fools’ RFC 2324 (1998) and is not recommended for real services.
Related tools: User-Agent Parser, URL Encoder, JSON Formatter, IP Subnet Calculator.
This tool runs entirely in your browser and your search text is never sent to a server.