What Is the HTTP Status Codes Reference?
Browse all HTTP status codes with descriptions, use cases, and examples. Quickly find what any status code means and when to use it.
Why Use This Tool?
HTTP status codes are the language servers use to communicate with clients. This reference covers every standard code from 100 to 599, organized by category with practical descriptions and common scenarios.
How to Use This HTTP Status Codes
- Browse by category — Status codes are organized by their first digit: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).
- Search for a specific code — Type a status code number or keyword to find its meaning instantly. For example, search '404' or 'not found.'
- Read the description — Each code includes its official name, a plain-English explanation, and common scenarios where you'll encounter it.
- Use the reference in debugging — When your API returns an unexpected code or your browser shows an error, look it up here to understand what went wrong and how to fix it.
Tips and Best Practices
- → Return the most specific status code. Don't default to 200 for success and 500 for errors. Use 201 for created, 204 for no content, 400 for bad request, 401 for unauthorized, 403 for forbidden, and 404 for not found.
- → Use 301 for permanent redirects, 302 for temporary. 301 tells search engines to transfer ranking to the new URL. 302 keeps the original URL in the index. Using the wrong redirect can hurt SEO.
- → Never return 200 with an error body. Some APIs return HTTP 200 with an error message in the JSON body. This breaks caching, monitoring, and client error handling. Use proper 4xx/5xx status codes.
- → 429 means you're being rate-limited. When you see 429 (Too Many Requests), check the
Retry-Afterheader for when you can try again.
Frequently Asked Questions
Built by Derek Giordano · Part of Ultimate Design Tools