HTTP Status Codes

How to use it

1. Type a code ("418"), a keyword ("redirect", "rate limit") or a class ("5xx") into the search box.
2. Results filter instantly across the code, name and description columns.
3. Codes are grouped and color-coded by class: 1xx informational, 2xx success, 3xx redirect, 4xx client error, 5xx server error.
4. Click a row to copy the code.
5. The full table is embedded — no network request, works offline once loaded.

Common use cases

• Reading logs and monitoring alerts — a reminder of what 422 means versus 400, or why a 502 differs from a 504.
• Designing an API — pick the most accurate status for each failure mode instead of defaulting everything to 400.
• Debugging CORS and caching — check what 304, 307 and 308 actually promise browsers.
• Writing docs — copy the correct code and name into error-code tables.

Why it stays private

The whole reference ships with the page and filtering is plain string matching. Nothing to send, nothing logged.

FAQ

Q: Does it cover unofficial codes? A: The table focuses on the standards plus widely deployed ones (like 429 and 418). Vendor-specific codes are not included.

Q: 404 vs 410 — which should I use? A: 404 means "not found, maybe temporary"; 410 means "gone, permanently". The descriptions spell out the difference so crawlers can act on it.

Q: Why does my client see a different code than my server sent? A: Proxies and gateways can replace codes (502/504 from gateways are common). The status on the wire may not be the one your application produced.