HTTP Status Code Reference

Every web response carries a three-digit status code. A 200 means success, 404 means gone, 500 means the server crashed. HTTP Status Code Reference is the bundled lookup table for all 57 standard codes spread across five families. Type part of a code, name or keyword and the list filters live. Expand any row for a plain-English explanation and copy the code with one click.

The tool bundles codes from four RFCs: RFC 7231 (core HTTP), RFC 4918 (WebDAV), RFC 6585 (additional client/server errors) and RFC 2324 (the April Fools' joke that standardised 418 I'm a Teapot). All 57 fit in 13 KB of static JSON — no API calls.

Each row shows the code number, name and a one-line summary. Codes tagged cacheable can be cached by browsers or proxies without further instruction. Expand a row to read the detail paragraph, which explains common use cases, typical causes, and pairings with HTTP methods and headers.

Running a Lookup by Code, Name or Keyword

1. Type into the search box at the top. A search updates live on every keystroke. Typing 404 shows only 404 Not Found. Typingredirect shows 301, 302, 303, 307 and 308 because all five mention redirect in their name, summary or detail.
2. Use the range-filter pills below the search to narrow by family: 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error. Clicking a pill filters to that family. The active pill is orange. Click again to clear the filter.
3. Combine search text and a range filter together: select 4xx Client Error, then type auth. The result set shows 401 Unauthorized and 407 Proxy Authentication Required, both in the 4xx range and both mentioning auth in their text.
4. Press × Clear filter to reset both search text and range filter at once and return to the full five-category view.
5. Click any row to expand its detail paragraph. Click again to collapse. The small Copy button beside each row copies the three-digit code as a plain string ready to paste into a response builder or a status-check condition.

Format Notes: Cacheability, RFCs and the 418 Exception

• Codes tagged cacheable (200, 204, 206, 301, 304, 307, 308, 410) may be cached without explicit Cache-Control headers, per RFC 7231. Browsers often cache 200 and 301 aggressively; use 302/303 or add Cache-Control: no-store to prevent it.
• Some codes are nearly extinct. 203 Non-Authoritative Information, 226 IM Used, 300 Multiple Choices, 402 Payment Required and 506–510 are rarely seen in practice. They are included for completeness since clients may still encounter them on legacy systems.
• 418 I'm a Teapot was defined in RFC 2324 as an April Fools' joke in 1998. Several major websites return 418 to deter automated scrapers. It is the only non-serious code that survived into production use.
• WebDAV codes (102 Processing, 207 Multi-Status, 208 Already Reported, 422 Unprocessable Content, 423 Locked, 424 Failed Dependency, 507 Insufficient Storage, 508 Loop Detected) appear only on servers implementing RFC 4918. REST APIs commonly use 422 but rarely use the others.
• The bundled data covers all codes standardised as of 2024. Unofficial vendor-specific codes (e.g., Cloudflare 520–527, AWS 561) are not included — check platform docs for those.