მთავარი მიღებული
- 01Covers every HTTP status code from 100 to 511, sourced from RFC 9110 and the IANA registry.
- 02Search by code number, name, or a phrase from the description — the list filters instantly.
- 03Filter by class (1xx, 2xx, 3xx, 4xx, 5xx) to narrow focus while debugging.
- 04Free, instant, no sign-up — runs entirely in your browser.
Why a Dedicated HTTP Status Code Reference?
Every web developer hits a status code they haven't seen in a while. You know 404 and 500, but what exactly is the difference between 401 and 403? When should you return 422 instead of 400? Is 418 actually in the spec? A quick reference that explains codes in plain English — rather than quoting RFC legalese — answers these questions in seconds.
Handytool's lookup is sourced from RFC 9110 (the current HTTP semantics specification) and the IANA HTTP status registry, including WebDAV extensions (207, 423, 424) and less-common codes you'll encounter in real API responses. Each entry has a one-sentence plain-English summary aimed at developers, not standardization committees.
How to Look Up an HTTP Status Code
- 01
Search by code, name, or keyword
Type a code (404), a name fragment (Not Found), or a descriptive phrase (teapot, redirect, authentication). The list filters in real time.
- 02
Filter by class
Use the class buttons to show only 1xx informational, 2xx success, 3xx redirect, 4xx client error, or 5xx server error codes. Useful when you're debugging a redirect chain or a server error and want to see all codes in that family.
- 03
Read the plain-English explanation
Each entry includes the official name, the code number, and a concise developer-focused description of what the code means and when it applies.
Status Codes Worth Memorizing
- 01200 OK — standard success for GET, POST, and PUT responses.
- 02201 Created — resource was created; typically returned after a successful POST.
- 03204 No Content — success with no response body; common after DELETE.
- 04301 Moved Permanently — canonical redirect; search engines transfer link equity.
- 05400 Bad Request — malformed syntax, missing fields, or unparseable payload.
- 06422 Unprocessable Entity — syntactically valid request that fails business logic.
Instant Lookup, No Server Calls
The entire status code database is bundled in the page. Searching, filtering, and reading descriptions all happen locally in your browser — no query is sent to any server, and the page works offline once loaded.
The reference includes vendor-specific codes you'll encounter in the wild, such as Cloudflare's 52x range for upstream errors. Those are noted as vendor extensions rather than standard HTTP, so you can distinguish between a spec-defined code and a platform-specific one.
HTTP Status Code Lookup FAQ
What's the difference between 400 and 422?
400 Bad Request is for requests the server can't parse at all — broken JSON, invalid query syntax. 422 Unprocessable Entity is for requests that parse correctly but fail semantic validation, like a duplicate email or an age value below the minimum.
What's the difference between 401 and 403?
401 means unauthenticated — provide credentials and retry. 403 means authenticated but forbidden — you don't have the required permission, and different credentials might help but the same ones won't.
Is 418 I'm a Teapot a real HTTP status code?
Yes — it was defined in the April Fools' RFC 2324 (1998), reaffirmed in RFC 7168, and included in the IANA registry. It's not used by HTTP itself but a handful of services return it as an Easter egg.
What RFC covers modern HTTP status codes?
RFC 9110, published in June 2022, is the current HTTP semantics specification. It supersedes RFC 7231 and consolidates core HTTP status code definitions.
Why do I see status codes above 511?
Codes above 511 are unassigned in the IANA registry. Some platforms (like Cloudflare) use custom 5xx codes for their own error conditions, but those are vendor extensions rather than standard HTTP.