# HTTP status code explainer

> Paste status codes (404, 301 302 307) or families (5xx) and get each one decoded: family, registered name, documented meaning, and the operational notes - including the protocol's own fallback rule for codes it has never met.

- Tool: https://ronutz.com/en/tools/http-status-code-explainer
- Family: Networking

---

# HTTP status code explainer

Paste status codes - bare (`404`), several at once (`301 302 307`), or whole families (`5xx`) - and get each one decoded: the family it belongs to, its registered name, its documented meaning, and the operational notes that matter when the code shows up in a log at 3 a.m.

## What it explains

The registry behind the tool is grounded in RFC 9110's status catalogue plus the registered extensions (RFC 6585's 428/429/431/511, RFC 7725's 451, RFC 8297's 103). The notes carry the distinctions this site's [companion article](https://ronutz.com/en/learn/http-status-codes-the-five-families) teaches: which redirects preserve the method (307/308) and which historically did not (301/302), why 304 is a cache handshake rather than a redirect, why 401 must arrive with `WWW-Authenticate` while 403 refuses regardless, and the incident-triage reading of the proxy trio - 502 blames the backend conversation, 503 the service's capacity, 504 the clock.

## The fallback rule, as a feature

Paste a valid code the registry has never met - a `599` from some middlebox - and the tool does not error. It answers with the protocol's own forward-compatibility rule: a client that does not recognize a code must treat it as the `x00` of its family, so the first digit alone defines the required behavior. That rule is why the status registry could grow for thirty years without breaking a single old client, and the tool considers it an answer worth rendering, not a gap worth apologizing for.

## Input grammar

Tokens separated by spaces, commas, or newlines. Each token is either three digits in 100-599 or a family in the form `1xx` through `5xx`. Duplicates deduplicate preserving order; twenty tokens per run is the cap. Everything runs locally in your browser.

## Sources

- RFC 9110: HTTP Semantics - the core catalogue, family rules, and the x00 fallback
- RFC 6585: Additional HTTP Status Codes - 428, 429, 431, 511
- RFC 7725: 451 Unavailable For Legal Reasons
- RFC 8297: 103 Early Hints

## Standards and references

- [RFC 9110: HTTP Semantics - the status code catalogue and family rules](https://www.rfc-editor.org/rfc/rfc9110) - the core status registry (1xx-5xx families, forward-compatibility fallback to x00, the redirect method-preservation semantics, 401's WWW-Authenticate requirement, 422's promotion into the core catalogue)
- [RFC 6585: Additional HTTP Status Codes](https://www.rfc-editor.org/rfc/rfc6585) - 428 Precondition Required, 429 Too Many Requests, 431 Request Header Fields Too Large, 511 Network Authentication Required
- [RFC 7725: An HTTP Status Code to Report Legal Obstacles](https://www.rfc-editor.org/rfc/rfc7725) - 451 Unavailable For Legal Reasons
- [RFC 8297: An HTTP Status Code for Indicating Hints](https://www.rfc-editor.org/rfc/rfc8297) - 103 Early Hints

## Related reading

- [HTTP Status Codes: The Five Families](https://ronutz.com/en/learn/http-status-codes-the-five-families.md): Three digits, and the first one does most of the work: 1xx continues, 2xx succeeds, 3xx redirects, 4xx blames the client, 5xx confesses for the server. The family logic, the codes an operator actually meets (200, 204, 301 vs 302 vs 307, 304's cache dance, 401 vs 403, 404 vs 410, 429, 500 vs 502 vs 503 vs 504), the famous curiosities, and why an unknown code's first digit is always enough to act on.