Converter · SOTA RFC 9110 (2022) + http.cat + curl

HTTP Status Code Reference

Searchable HTTP status code reference per RFC 9110 (2022). All codes 1xx through 5xx with category filters, usage examples, fetch/cURL snippets, and optional http.cat visual thumbnails.

Show http.cat images

How to Use HTTP Status Code Reference in 3 Steps

Configure. Search by code (404, 422) or name (Not Found, Unprocessable Entity), or filter by category (1xx informational, 2xx success, 3xx redirect, 4xx client error, 5xx server).
Process. Each code shows: official name, RFC 9110 reference, typical use cases, common headers, and code examples in fetch and cURL.
Export. Copy a fetch snippet ready for testing, or a cURL command to replay. Toggle http.cat thumbnails for a quick mental association.

Why HTTP Status Code Reference on Pixlane

HTTP status codes signal request outcomes — 200 OK, 404 Not Found, 500 Internal Server Error. But nuances matter: when to use 401 vs 403, 409 vs 422, or the newer 428 Precondition Required. Pixlane ships the complete RFC 9110 (2022) reference with searchable filters, usage examples (when to return each code), fetch + cURL snippets for testing, and optional http.cat visual thumbnails.

RFC 9110 (2022) — The current HTTP Semantics RFC replaces 7230-7235 (2014). Clarifies edge cases around 418 (removed, then re-added), 103 Early Hints, 425 Too Early — all reflected in the reference.
Usage Examples — Beyond definitions: when should you return 409 Conflict vs 422 Unprocessable Entity? When is 410 Gone better than 404? Each code includes best-practice guidance.
fetch + cURL Snippets — Each entry has a ready fetch(`url`).then(r => r.status === 404) and cURL example with `-w '%{http_code}'`. Paste and test.
http.cat Integration — Optional fun mode — shows http.cat images next to each code. Instant visual memory for the 70+ codes in the spec.

Frequently Asked Questions

Is 418 I'm a Teapot real?

Yes. Originally an April Fools' joke in RFC 2324 (1998), it was formally removed from the IANA registry in 2015, then petitioned back to 'save the teapot' in 2018. Now officially defined as a humorous reserved code — most frameworks implement it.

When should I return 401 vs 403?

401 Unauthorized means 'you're not authenticated — log in'. 403 Forbidden means 'you ARE authenticated but lack permission'. A common bug is returning 403 without first checking authentication (always 401 first if there's no valid token).

What's the difference between 409 and 422?

409 Conflict is resource-level — the current state conflicts with your request (e.g., version mismatch, duplicate key). 422 Unprocessable Entity is validation-level — your request shape is understood but semantically invalid (e.g., email format wrong).

Is this tool free?

Yes. HTTP Status Reference on Pixlane is completely free with no signup required.