HTTP Status Codes
Search or select an HTTP status code to review its standard meaning and when that response is appropriate.
How to Use HTTP Status Codes
- Enter or choose the status code you encountered.
- Read the definition and identify whether it is informational, successful, redirecting, a client error, or a server error.
- Confirm the response body and headers because the numeric code does not describe the complete outcome.
Choosing the Right Status Code
Status codes let an HTTP server communicate the outcome of a request before a client interprets the body. Correct codes help browsers, crawlers, caches, API clients, and monitoring systems respond consistently.
Select the most specific standard code that matches the actual outcome. Avoid returning 200 for missing resources, using temporary redirects for permanent moves, or exposing implementation details in 5xx responses.
HTTP Status Codes Example
Use `201 Created` after an API successfully creates a resource, `301 Moved Permanently` for a stable URL migration, and `404 Not Found` when no current resource exists at a URL.
Frequently Asked Questions About HTTP Status Codes
What is the difference between 301 and 302?
301 represents a permanent move. 302 represents a temporary redirect when the original URL may be used again.
When should a deleted page return 410 instead of 404?
410 explicitly states that a resource is gone and is useful when removal is intentional and expected to be permanent. 404 remains correct when absence is unknown or general.
Do clients treat every status code exactly the same?
No. Standards define semantics, but clients, caches, crawlers, and applications can apply additional behavior.