HTTP Status Codes
Complete, searchable HTTP status code reference. All 1xx–5xx codes with descriptions and use cases. Free, browser-based.
How to Use
Type a status code number, name keyword, or description into the search box to filter the list in real time. Leave the search empty to browse all codes by category.
Status Code Categories
- 1xx Informational: Provisional responses — request received, server is still processing.
- 2xx Success: The request was received, understood, and accepted.
- 3xx Redirection: Further action must be taken to complete the request.
- 4xx Client Error: The request contains bad syntax or cannot be fulfilled.
- 5xx Server Error: The server failed to fulfill a valid request.
Common Status Codes at a Glance
- 200 OK — Standard success response.
- 201 Created — New resource created (common in POST/PUT APIs).
- 204 No Content — Success, no response body (common in DELETE).
- 301 Moved Permanently — SEO-safe permanent redirect.
- 400 Bad Request — Client sent malformed data.
- 401 Unauthorized — Authentication required.
- 403 Forbidden — Authenticated but not permitted.
- 404 Not Found — Resource does not exist.
- 429 Too Many Requests — Rate limit exceeded.
- 500 Internal Server Error — Unexpected server failure.
- 503 Service Unavailable — Server down or overloaded.
FAQ
What do the different HTTP status code ranges mean?
1xx = Informational (request received, continuing). 2xx = Success (request completed). 3xx = Redirection (further action needed). 4xx = Client error (bad request, not found, unauthorized). 5xx = Server error (the server failed to handle a valid request).
What is the difference between 301 and 302?
301 Moved Permanently tells browsers and search engines to update their records — the resource has moved for good. 302 Found is a temporary redirect; clients should keep using the original URL for future requests.
When should I use 404 vs 410?
Use 404 Not Found when the resource doesn't exist and you're unsure if it will return. Use 410 Gone when you're certain the resource is permanently removed and will never return — this signals search engines to deindex it.
Why does 429 matter for APIs?
429 Too Many Requests is the standard response for rate limiting. Clients should respect Retry-After headers and implement exponential backoff to avoid hammering the server.