HTTP Status Code Lookup
Search and understand HTTP status codes with common use cases and troubleshooting tips
Continue
informationalThe server has received the request headers and the client should proceed to send the request body.
- Large file uploads
- HTTP/1.1 protocol
- Expect header handling
Switching Protocols
informationalThe server is switching protocols as requested by the client.
- WebSocket upgrades
- HTTP/2 upgrades
- Protocol switching
OK
successThe request has succeeded. The information returned with the response is dependent on the method used in the request.
- Successful GET requests
- API responses
- File downloads
Created
successThe request has succeeded and a new resource has been created as a result.
- Resource creation
- POST requests
- File uploads
No Content
successThe server successfully processed the request and is not returning any content.
- DELETE operations
- Updates without response body
- Form submissions
Moved Permanently
redirectionThe requested resource has been permanently moved to the URL given by the Location headers.
- URL redirects
- SEO redirects
- Domain changes
Found
redirectionThe requested resource has been temporarily moved to the URL given by the Location headers.
- Temporary redirects
- Login redirects
- Form submissions
Not Modified
redirectionThe client can use cached data. The response must not contain a message body.
- Caching
- Conditional requests
- ETag validation
Bad Request
client errorThe server cannot or will not process the request due to an apparent client error.
- Invalid syntax
- Malformed requests
- Missing parameters
Unauthorized
client errorAuthentication is required and has failed or has not been provided.
- Login required
- Invalid credentials
- Missing authentication
Forbidden
client errorThe server understood the request but refuses to authorize it.
- Insufficient permissions
- IP restrictions
- Content restrictions
Not Found
client errorThe requested resource could not be found on the server.
- Missing pages
- Invalid URLs
- Deleted resources
Conflict
client errorThe request could not be completed due to a conflict with the current state of the resource.
- Version conflicts
- Duplicate resources
- State conflicts
Unprocessable Entity
client errorThe server understands the content type and syntax but cannot process the contained instructions.
- Validation errors
- Business rule violations
- Semantic errors
Too Many Requests
client errorThe user has sent too many requests in a given amount of time.
- Rate limiting
- API throttling
- DDoS protection
Internal Server Error
server errorThe server encountered an unexpected condition that prevented it from fulfilling the request.
- Server crashes
- Unhandled exceptions
- Configuration errors
Bad Gateway
server errorThe server received an invalid response from an upstream server.
- Proxy errors
- Load balancer issues
- Upstream failures
Service Unavailable
server errorThe server is temporarily unable to handle the request due to maintenance or overload.
- Maintenance mode
- Server overload
- Temporary outages
Gateway Timeout
server errorThe server acting as a gateway did not receive a timely response from an upstream server.
- Proxy timeouts
- Upstream delays
- Network issues
Features
Search by Code, Name, or Description
Quickly find specific HTTP status codes using the search bar.
Filter by Category
Narrow down results to specific categories like 2xx Success or 4xx Client Error.
Common Use Cases and Troubleshooting
Get practical examples and troubleshooting tips for each status code.
Quick Reference
Common HTTP status code ranges to quickly reference.