Http Status Codes List
Search and reference all HTTP status codes (1xx-5xx). Meaning, use case, and common causes for each code.
Advertisement
About HTTP Status Codes
Complete interactive reference for all HTTP status codes (100-599). Search by code or keyword. Shows official meaning, common use cases, and debugging tips for 1xx (informational), 2xx (success), 3xx (redirect), 4xx (client error), and 5xx (server error).
HTTP status codes are the language that web servers use to communicate with browsers and API clients. Every web developer, QA engineer, and DevOps professional needs to quickly reference status code meanings during debugging. Understanding the difference between 301 and 302, or 401 and 403, can save hours of debugging time.
How to use
- Paste or type your input directly into the editor — output updates in real time as you work.
- Check the error/status indicator if your input is invalid; it points to the exact line or issue where relevant.
- Use the copy or download button to grab the processed output once it looks right.
- Chain into a related tool below if your workflow needs a second processing step.
- Processing happens entirely client-side in your browser — nothing you paste is uploaded to a server.
Tool details
⚡ Next step — complete your workflow
Frequently asked questions
404 vs 410 HTTP status?
404: resource not found (may return later). 410: resource permanently gone. Use 410 for deleted URLs to speed up Google deindexing.
301 vs 302 redirect?
301 = Permanent redirect (SEO juice transfers, Google updates indexed URL). 302 = Temporary redirect (SEO juice stays at original URL).
Advertisement