100Informational101Informational102Informational103Informational104TemporaryInformational200Success201Success202Success203Success204Success205Success206Success207Success208Success226Success300Redirect301Redirect302Redirect303Redirect304Redirect305Redirect306UnusedRedirect307Redirect308Redirect400Client error401Client error402Client error403Client error404Client error405Client error406Client error407Client error408Client error409Client error410Client error411Client error412Client error413Client error414Client error415Client error416Client error417Client error418UnusedClient error421Client error422Client error423Client error424Client error425Client error426Client error428Client error429Client error431Client error451Client error500Server error501Server error502Server error503Server error504Server error505Server error506Server error507Server error508Server error510ObsoleteServer error511Server error419frameworkClient error444nginxClient error449msClient error494nginxClient error495nginxClient error496nginxClient error497nginxClient error499nginxClient error509otherServer error520cloudflareServer error521cloudflareServer error522cloudflareServer error523cloudflareServer error524cloudflareServer error525cloudflareServer error526cloudflareServer errorAbout HTTP Status Codes
HTTP status codes are the three-digit results a server returns for each request, grouped by their first digit into five classes: 1xx informational, 2xx success, 3xx redirection, 4xx client error, and 5xx server error. This tool ships a complete code dictionary: enter codes like 404, 301, or 429 to find the standard name, meaning, class, and common use cases, or search by keyword such as "redirect" or "unauthorized".The tables are bundled in the page and queried entirely in your browser, with no network requests. The first digit sets the response class, and understanding that is more practical than memorising numbers. Informational means the request was received but not finished, success that it was handled correctly, redirection that the client must request elsewhere, client error that the request itself is at fault, and server error that the request was fine but handling failed. For an unfamiliar code, the first digit says who fixes it. Returning errors inside a success code is the most common misuse and breaks every upstream that depends on the status. Some interfaces return success on a business failure and put an error flag in the body, defeating monitoring, caching and retry policy, which read only the status. Use a code matching the semantics and put details in the body. Choosing temporary versus permanent redirects affects clients and search engines, and confusing them causes lasting problems. A permanent redirect is cached long term, so a misconfiguration persists in clients even after it is corrected, while a temporary one leaves no such cache. Use the temporary code when the intent is a temporary adjustment. Gateway-related codes quickly localise a fault, valuable when troubleshooting production. They appear when a request passed the gateway but the upstream responded late or abnormally, so seeing one places the problem after the gateway rather than at the client, while a client error code means the request never reached business logic. That halves the search space immediately. Cache-related codes differ strictly in meaning and misusing them shows users stale content. One requires the client to revalidate conditionally on later requests, another merely reports the content as unchanged without retransmission, and a third signals a resource permanently removed. Configure caching and retirement by semantics rather than one code for everything. Finally, keep the status code and the response body consistent so a client can handle both with one logic. If some interfaces return structured fields on error and others plain text, the client writes per-interface parsing and misses cases. Agree one error shape paired with the codes — a low-cost convention in interface design with clear returns.
How It Works Internally
Status codes fall into five classes by leading digit, each saying how far the request got: informational, success, redirection, client error, server error. The crucial split is transport versus business — returning a success code for a business failure forces clients to parse the body and deprives monitoring of a reliable signal. Permanent and temporary redirects are also not interchangeable, since the former is cached long term.
Returning 200 with {ok:false} for a missing resourceMonitoring sees no error rate, caches may store the failure and clients must parse the body — 404 is correctMeasured on This Page
| Entries | 80 = 64 IANA-registered + 16 vendor extensions |
|---|---|
| Name accuracy | All 64 IANA entries match the 2026-10-27 registry; 422 was officially renamed from Unprocessable Entity to Unprocessable Content |
| Registry status | 2 unused (306, 418) · 1 obsolete (510) · 1 temporary (104) |
| Vendor split | nginx 6 / Cloudflare 7 / IIS 1 / Laravel 1 / cPanel 1 |
IANA lists 418 under the official name (Unused): RFC 9110 §15.5.19 reserves the number without defining any behaviour. The teapot joke comes from the April Fools RFC 2324 and was never a real registration. Separately, 104 (upload resumption) is a temporary registration that expires on 2026-11-13 and will fall back into the unassigned range.
How to Use
- Open "HTTP Status Codes"
- Type a code or keyword to filter the list
- Read the meaning, common causes and remediation
- Toggle "vendor-specific" to separate non-standard codes
- Check the 2xx to 5xx grouping for the right handling strategy
Use Cases
- Debug API responses — Quickly confirm semantics of 422 or 409 to tell a data problem from a conflict.
- Configure redirects — Distinguish 301 permanent from 302 temporary to avoid hurting SEO link equity.
- Rate-limit design — Pick 429 Too Many Requests and pair it with a Retry-After header.
- Error handling — Decide on the frontend whether to retry or prompt based on 4xx vs 5xx classes.
- Learning & interviews — Systematically memorize standard definitions and applicable boundaries.
- Proxy config — Check 502 vs 504 semantics to configure gateway timeout and retry logic correctly.
- Cache tuning — Review 304 and 200 semantics to validate ETag-based caching and conditional requests.
FAQ
Difference between 301 and 308?
Both are permanent redirects, but with 301 a browser may switch POST to GET, while 308 strictly preserves the original method and body. Prefer 308 when form submissions are involved.
How to tell 401 from 403?
401 Unauthorized means not authenticated (missing or invalid credentials, go log in); 403 Forbidden means authenticated but lacking permission, where providing credentials again will not help.
When should I return 404 instead of 200?
Missing resources should return 404 so search engines and clients handle them correctly. Serving a "not found" page with 200 creates a soft 404 that harms indexing.
Is status code 418 real?
418 I'm a teapot comes from the April Fools' RFC 2324 joke and is not an official standard, though many frameworks keep it. Do not rely on it for business semantics in production.
What do 502, 503, and 504 mean?
502 means the gateway got an invalid upstream response, 503 means the service is temporarily unavailable (overload or maintenance), and 504 means the gateway timed out waiting upstream. Check the upstream service and timeout settings accordingly.
An API returns 200 for a business failure. Is that a misuse?
Yes, it conflates transport success with business outcome. A missing resource should be 404, invalid input 400 or 422, and unauthenticated versus unauthorized map to 401 and 403. Returning 200 for everything forces clients to parse the body to branch, and leaves monitoring and alerting without a reliable signal, which raises maintenance cost noticeably over time.
What goes wrong if 302 and 301 are mixed up?
301 means permanent, so browsers and intermediaries cache the redirect long term and may keep following it even after you restore the original address, while 302 means temporary and is not cached that way. Writing a temporary redirect as 301 is a common operational incident, especially during canary switches and domain migrations. Use a temporary code for anything likely to change, and upgrade to permanent only once it is settled.
What is the SEO difference between 301 and 302?
301 tells search engines the move is permanent and passes ranking to the new URL; 302 means temporary, so the old URL stays indexed. Writing a permanent redirect as 302 is a classic mistake that delays indexing of the new page.