1. Browse the codes grouped by class (1xx-5xx), or type in the search box to filter by code, name, or description.
2. Click any row to expand it and read the fuller explanation of what that status code means.
3. Use the color-coded badges to quickly distinguish success (green), redirection (amber), client errors (red), and server errors (purple).
4. Reference the code while debugging an API response, browser network tab, or server log.

• Quickly recall what a status code means while reading an API response or browser DevTools network tab.
• Decide which status code to return from a REST API endpoint you're building (e.g. 201 vs 200, 422 vs 400).
• Explain to a teammate or in documentation why a request returned a specific error code.
• Distinguish between similar codes like 401 vs 403, or 301 vs 302 vs 307, when debugging redirects or auth.
• Look up an unfamiliar code encountered in a server log or monitoring alert.

The full reference list is bundled with the page and searched locally in your browser — no network requests are made.

• Covers commonly used codes, not the complete IANA HTTP status code registry including rare vendor-specific extensions.
• Explanations are general references — actual server behavior for a given code can vary by API or framework.
• Does not make live requests or inspect your actual network traffic — it's a static reference only.