HTTP Status Code Reference
NewComplete reference of all HTTP status codes with explanations, when to use them, and common causes. Searchable and categorized.
Related Tools
Embed this tool
Add this tool to your website or blog with a single iframe snippet.
<iframe src="https://www.dukotools.com/tools/http-status-codes?embed=1" width="100%" height="600" frameborder="0" allow="clipboard-write" loading="lazy" title="http-status-codes tool"></iframe>
About HTTP Status Code Reference
HTTP Status Code Reference is a searchable lookup of every standard HTTP response code (1xx through 5xx), covering informational, success, redirection, client error, and server error ranges. Each entry explains what the code means, when a server should return it, what commonly causes it, and a realistic example scenario so you can quickly tell codes with overlapping use cases apart (like 401 vs 403, or 301 vs 308). Filter by category, search by code or keyword, switch between a detailed card view and a compact table, and copy individual codes or the full filtered JSON list for documentation, API design, or debugging notes.
Key Features
Full 1xx-5xx coverage
Includes standard, WebDAV, and commonly seen unofficial codes (like 418 and 420), not just the common ones.
Category filters
Narrow the list to 1xx, 2xx, 3xx, 4xx, or 5xx with one tap.
Search by code, name, or meaning
Type "429", "redirect", or "auth" to jump straight to relevant codes.
Card and table views
Switch between a detailed explanation view and a scannable table for quick reference.
When-to-use and common-causes guidance
Each code lists a practical scenario so you know which code to return, not just what it means.
Copy code or JSON
Copy a single status code or export the current filtered list as JSON for docs or tests.
How to Use
- 1
Search or filter
Type a code, name, or keyword, or tap a category (1xx-5xx) to narrow the list.
- 2
Switch views
Use table view for a quick scan or card view for full detail on each code.
- 3
Read the details
Check the meaning, when to use it, common causes, and an example scenario for each code.
- 4
Copy what you need
Copy a single code or the whole filtered set as JSON.
- 5
Share a filtered view
The search term and category are saved in the URL so you can share a direct link.
Real-World Use Cases
API design review
A backend developer double-checks whether 409 Conflict or 422 Unprocessable Content is the more appropriate response for a duplicate-resource error before finalizing an endpoint spec.
Debugging a production incident
An engineer sees repeated 502s in logs and uses the tool to confirm the code points to a bad upstream response rather than a timeout, narrowing the investigation to the origin server.
Onboarding and documentation
A team lead links a filtered view of 3xx codes when writing internal docs about the company's redirect strategy for a domain migration.
Frequently Asked Questions
Related Free Tools
Explore these tools that work great alongside HTTP Status Code Reference: