A comprehensive, searchable reference guide for all HTTP status codes with descriptions, causes, and solutions.
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The server is switching protocols as requested by the client.
Processing
The server has received and is processing the request, but no response is available yet.
Early Hints
Used to return some response headers before final HTTP message.
OK
The request has succeeded.
Created
The request has been fulfilled and resulted in a new resource being created.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The request was successful but the enclosed payload has been modified by a transforming proxy.
No Content
The request has succeeded but there is no content to send back.
Reset Content
The server tells the client to reset the document view.
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Multi-Status
Provides status for multiple independent operations (WebDAV).
Need Help Building Robust Web Applications?
Our development team can help you design and implement RESTful APIs with proper error handling, build scalable web applications, and optimize your infrastructure.
Understanding HTTP Status Code Categories
1xx Informational
The request was received and is being processed. These are interim responses. Examples: 100 Continue, 101 Switching Protocols, 103 Early Hints.
2xx Success
The request was successfully received, understood, and accepted. Examples: 200 OK, 201 Created, 204 No Content, 206 Partial Content.
3xx Redirection
Further action is needed to complete the request. Examples: 301 Moved Permanently, 302 Found, 304 Not Modified, 307 Temporary Redirect.
4xx Client Error
The request contains bad syntax or cannot be fulfilled. Examples: 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 429 Too Many Requests.
5xx Server Error
The server failed to fulfill a valid request. Examples: 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout.
Custom Codes
Some platforms use non-standard codes (e.g., Cloudflare 52x errors, IIS 440 Login Timeout). Use standard codes when possible for better compatibility.
Common Status Codes Explained
Standard success response. The request was successful and the server returned the requested data.
A new resource was successfully created (typically in response to POST or PUT requests).
The server cannot process the request due to client error (malformed syntax, invalid parameters, etc.).
The requested resource could not be found on the server. This is the most common error status code.
A generic server error occurred. The server encountered an unexpected condition that prevented it from fulfilling the request.
Best Practices for API Design
- •Use semantic codes: Choose status codes that accurately describe the result (200 for success, 404 for not found, 500 for server errors)
- •Be consistent: Use the same status codes for similar situations across your API
- •Provide error details: Include helpful error messages in the response body along with appropriate status codes
- •Use 201 for resource creation: Return 201 Created with a Location header pointing to the new resource
- •Distinguish authentication vs authorization: Use 401 for missing/invalid auth, 403 for insufficient permissions
- •Implement rate limiting: Return 429 Too Many Requests with Retry-After header when rate limits are exceeded
Frequently Asked Questions
Common questions about the HTTP Status Codes
HTTP status codes are three-digit numbers returned by web servers in response to HTTP requests. They indicate whether a specific request has been successfully completed and provide information about the status of the request. Status codes are grouped into five categories: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).
Explore More Tools
Continue with these related tools
Terraform Plan Explainer
Analyze Terraform plans for security risks, blast radius, and dependencies. Reduce production incidents by understanding infrastructure changes before applying them.
HTTP Request Builder
Interactive developer tool for constructing, sending, and analyzing HTTP requests directly from the browser
CSV to JSON Converter
Convert CSV files to JSON format instantly with browser-based processing
Excel to JSON Converter
Convert Excel spreadsheets to JSON with multi-sheet support and custom formatting options
YAML to JSON Converter
Convert YAML to JSON or JSON to YAML with full support for comments and anchors
Diff Checker
Compare text, code, or configuration files side by side
ℹ️ Disclaimer
This tool is provided for informational and educational purposes only. All processing happens entirely in your browser - no data is sent to or stored on our servers. While we strive for accuracy, we make no warranties about the completeness or reliability of results. Use at your own discretion.