HTTP Status Codes Reference
A complete, searchable list of HTTP status codes with descriptions and detailed explanations.
Showing 55 of 55 status codes
About HTTP Status Codes
HTTP status codes are three-digit numbers returned by a web server in response to a client's request. They indicate whether the request was successful, redirected, resulted in an error, or requires further action. Understanding these codes is essential for web developers, API designers, and anyone working with HTTP-based services. This reference includes all standard and commonly used status codes organized by category.
How to Use
- Use the search bar to find a specific status code by number, name, or keyword.
- Filter by category using the buttons: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), or 5xx (Server Error).
- Click on any status code to expand it and view detailed information about its usage and meaning.
Frequently Asked Questions
What is the difference between 401 and 403?
A 401 Unauthorized response means the client has not authenticated (no credentials or invalid credentials were provided). A 403 Forbidden response means the client is authenticated but does not have permission to access the resource. Re-authenticating will not help with a 403.
When should I use 301 vs 302 redirect?
Use 301 Moved Permanently when a resource has permanently moved to a new URL and you want search engines to update their index. Use 302 Found for temporary redirects where the original URL should remain in search indexes. For method-preserving redirects, consider 307 and 308.
What does a 500 error mean?
A 500 Internal Server Error is a generic server-side error indicating that something unexpected happened on the server. It usually means there is a bug in the server code or an unhandled exception. Check server logs for the specific cause.
What is a 429 Too Many Requests error?
A 429 status code indicates the client has exceeded the rate limit set by the server. The response typically includes a Retry-After header telling you how long to wait before making another request. This is a common response from APIs to prevent abuse.
Is 418 I'm a Teapot a real status code?
It originated as an April Fools' joke in RFC 2324 (Hyper Text Coffee Pot Control Protocol) in 1998. While not intended for real use, it has become a beloved Easter egg in the developer community and is sometimes implemented by servers as a joke response.