HTTP Status Code Reference
Complete list of HTTP status codes with descriptions, use cases, and examples. 100% client-side.
62 status codes
📖 Most Commonly Used Codes
🔒 100% private: Reference data is bundled locally. Follows IANA registry and RFC 9110.
About HTTP Status Code Reference
HTTP status codes are three-digit numbers returned by servers in response to client requests. They indicate the outcome of the request: success (2xx), redirection (3xx), client error (4xx), or server error (5xx). Every REST API, website, and web service uses them. Knowing which code to return — and interpreting what a client receives — is fundamental to web development. This reference lists all standard HTTP status codes from the IANA registry and RFC 9110, with descriptions, common use cases, and best-practice guidance. Search by code, filter by category, and copy with one click.
How It Works
- Browse by category (1xx, 2xx, 3xx, 4xx, 5xx) or see all codes.
- Search by number (e.g., "404") or name (e.g., "not found").
- Click any row to copy the code number.
- Read the description and use cases for each code.
✨ Key Features
- ✓All 60+ standard HTTP status codes
- ✓Organized by category: 1xx, 2xx, 3xx, 4xx, 5xx
- ✓Search by number or name
- ✓Detailed descriptions
- ✓Common use cases for each code
- ✓Real-world examples
- ✓Categorized with icons (success, error, redirect, etc.)
- ✓One-click copy
- ✓Common codes flagged as "most used"
- ✓100% client-side — no data sent to any server
🎯 Common Use Cases
- →Choosing the right status code for an API endpoint
- →Debugging why a client received a specific error
- →Documenting API responses in OpenAPI/Swagger
- →Writing tests that assert status codes
- →Configuring nginx/Apache to return proper codes
- →Learning REST API best practices
- →Reviewing server logs to understand error patterns
- →Teaching HTTP fundamentals
💡 Advanced Tips & Pro Insights
- ▸2xx = success. Use 200 (OK) for successful GET/PUT, 201 (Created) for POST that creates, 204 (No Content) for DELETE or PUT without response body.
- ▸3xx = redirect. Use 301 (Moved Permanently) for permanent URL changes, 302 or 307 (Temporary) for temporary, and 304 (Not Modified) with ETag caching.
- ▸4xx = client error. 400 (Bad Request) for malformed requests, 401 (Unauthorized) when auth is missing, 403 (Forbidden) when auth is valid but permission denied, 404 (Not Found) for missing resources, 429 (Too Many Requests) for rate limits.
- ▸5xx = server error. 500 (Internal Server Error) is the generic fallback. Use more specific codes like 502 (Bad Gateway), 503 (Service Unavailable), and 504 (Gateway Timeout) when applicable.
- ▸Never return 200 with an error body — this breaks clients and monitoring. Always use the appropriate 4xx/5xx code.
- ▸401 vs 403: 401 means "you are not authenticated" (login required); 403 means "you are authenticated but not authorized" (permission denied).
Frequently Asked Questions
Is this HTTP status reference free?▾
Yes, this HTTP status code reference is completely free with no signup, email, or usage limits.
Is my data safe?▾
Yes, 100% safe. All lookups happen in your browser. Nothing is sent to any server.
What is an HTTP status code?▾
An HTTP status code is a three-digit number returned by a server in the HTTP response. It indicates the outcome of the request: 2xx for success, 3xx for redirects, 4xx for client errors, and 5xx for server errors.
What is the difference between 401 and 403?▾
401 Unauthorized means the client is not authenticated — credentials are missing or invalid. 403 Forbidden means the client is authenticated but does not have permission to access the resource.
What is the difference between 301 and 302?▾
301 Moved Permanently is a permanent redirect that clients and search engines should cache. 302 Found (and 307 Temporary Redirect) is a temporary redirect that should not be cached.
Should I return 200 or 201 for a POST that creates a resource?▾
Return 201 Created. Include a Location header with the URL of the new resource, and optionally the created resource in the body. Use 200 OK if the POST does not create a resource (e.g., a search that returns results).
What status code means rate limited?▾
429 Too Many Requests. Include a Retry-After header indicating how long the client should wait before retrying.
Can I use custom status codes?▾
The HTTP specification reserves codes for specific meanings. You can use non-standard codes in the 2xx–5xx range (like 599 for specific business logic), but this can break clients and proxies. Stick to standard codes when possible.