HTTP Status Code Lookup
Search and explore every HTTP status code with explanations, examples, and categories
Quick Reference
HTTP Status Codes List & Reference
Complete HTTP status code reference. Look up any status code (200, 301, 404, 500) with explanations, examples, and troubleshooting tips. Free developer reference.
How It Works
Browse or search the complete list of HTTP status codes. Each code includes a clear description, common use cases, and suggestions for fixing issues related to error codes.
Common Use Cases
- Quickly looking up what an unfamiliar HTTP status code means
- Debugging API responses that return unexpected error codes
- Learning the difference between similar codes like 301 vs 302 redirects
- Training junior developers on proper HTTP response handling
Frequently Asked Questions
It is a three-digit number returned by a web server in response to a request. It tells the client (browser or API consumer) the outcome of the request (success, redirect, error, etc.).
HTTP 404 means 'Not Found'. The server could not find the requested resource. This usually means the URL is wrong or the page has been deleted.
401 (Unauthorized) means authentication is required but not provided or failed. 403 (Forbidden) means you're authenticated but don't have permission to access the resource.
1xx: Informational, 2xx: Success, 3xx: Redirection, 4xx: Client Error, 5xx: Server Error. Each range indicates a different type of response from the server.
301 is a permanent redirect — search engines transfer SEO value to the new URL. 302 is a temporary redirect — the original URL retains its SEO value.
403 means the server understood the request but refuses to authorize it. Unlike 401 (Unauthorized), authentication won't help — you don't have permission to access the resource.
Use 404 (Not Found) when a resource doesn't exist or may have never existed. Use 410 (Gone) when a resource was intentionally permanently removed — it tells search engines to stop checking.