How it works
The page is one list of 78 status codes — 63 official ones and 15 unofficial — and every entry carries the same parts: the code and its name, a one-sentence meaning, a paragraph on when to send it and what usually causes it, the RFC section or the vendor it comes from, the headers that belong with it, whether a cache may store it by default, and the codes it is often confused with. All of it is in the HTML as served, so a search can land on /api/http-status-codes#404 directly, and the search box and the class buttons hide entries with CSS rather than removing them.
Searching reads the query as words. A word made of digits matches every code that starts with it, so 30 shows the nine redirects and 42 the 420s; any other word has to appear somewhere in the entry — its name, summary, detail, source or headers — and several words all have to match, which is how rate limit finds 429 and 420 and retry-after finds every code whose entry names that header. Pressing Enter on an exact code jumps to it, as does following a #code link, which clears a filter that was hiding the entry and highlights it for a moment.
The entries are written as answers rather than definitions: 401 says it means unauthenticated despite its name, 404 says when 410 is the better choice, 503 says to send Retry-After. The See also links join the pairs people search for — 401 and 403, 400 and 422, 502 and 504 — and the table beneath the list puts each pair’s difference in one line. The unofficial section covers what appears in logs without being in any RFC: nginx’s 499 and 444, Cloudflare’s 520 to 526, Laravel’s 419 and Twitter’s 420, each marked with who sends it.