📡 Dev

HTTP Status Codes

Look up all HTTP status codes with names and descriptions. Search by code or keyword. Quick reference for developers.

How to use?

You can search by the number (404, say) or by a keyword ("not found"). To narrow things down to a single class, use the category filters, which show only the codes from that group.

Every HTTP status code

A 404 everyone recognises. But a 422, a 451 or a 502? That's where it gets murky. HTTP status codes are how the server tells you what happened to a request, and knowing them saves hours of debugging. This reference pulls them all together, with name and description.

Search by code or by keyword and the meaning shows up right away, organised by the protocol's families: 2xx for success, 3xx for redirection, 4xx for client errors, 5xx for server errors. It's the lookup for anyone building APIs, debugging integrations or just trying to make sense of the response that turned up.

Everything runs in the browser, so there's no spec to open and no numbers to memorise. A straightforward reference for the daily work of anyone who deals with the web.

Frequently asked questions

Does this check my URL and show the status it returns?

No. It works as a lookup table: all 61 codes live inside the page and no request ever leaves your browser. To find out what a URL returns, use the Network tab in DevTools, curl -I or a header-checking service. This page covers the opposite direction. You arrive with the number already in hand, the 422 an API threw back or the 502 sitting in your logs, and find out what it means.

I looked for 305 and could not find it. Are codes missing?

305 and 306 were left out on purpose: Use Proxy was deprecated over security concerns and 306 was never actually put to use. Everything else is here, with 4 codes in the 1xx family, 10 in 2xx, 7 redirects, 29 client errors and 11 server errors, oddities like 418 I'm a teapot and 451 for legal takedowns included. When a search matches nothing, a no-codes-found line shows up below the list.

Does the search only work with the code number?

It scans three fields at once: the number, the name and the description. Type cache and 304 comes up; type proxy and you get both 203 and 407. The family filter stays active alongside the text, so picking 4xx and typing timeout narrows the list to 408 and leaves 504 out. One quirk to watch: the number is matched as text rather than as a value, so searching for 0 pulls in every code containing a zero and floods the list.

Related Tools

📡

HTTP Status Code Lookup

Type any HTTP status code from 100 to 511 and read its official reason phrase, across the informational, success, redirect, client and server error ranges.

🔑

Basic Auth Generator

Generate the HTTP `Authorization: Basic <base64>` header from username and password. Useful to test APIs with basic auth via curl, Postman or fetch. Everything in your browser.

⏱️

Retry-After Header Parser (HTTP 429 and 503)

Paste a Retry-After value in delay seconds or HTTP-date form to get the wait in seconds and minutes, or the exact instant to try again.

📊

Range Header Parser

Decompose a Range header (bytes=0-499, bytes=-100, etc.) into individual ranges with start, end and size.

🍪

HTTP Cookie Parser

Paste a Set-Cookie header and inspect name, value, Domain, Path, Expires, Max-Age, HttpOnly, Secure and SameSite separately. Browser-only.

🛡️

Hamming Code (7,4) Generator

Encode 4 data bits into 7 Hamming bits with parity, capable of correcting 1 wrong bit. Also demonstrates error detection.