http
HTTP Status Code Checker
Look up and understand HTTP status codes and their meanings
http HTTP Status Code Checker
help_outline HTTP Status Code Categories
1xx Informational
Request received, continuing process.
- • 100 Continue
- • 101 Switching Protocols
- • 102 Processing
- • 103 Early Hints
2xx Success
Request successfully received, understood, and accepted.
- • 200 OK
- • 201 Created
- • 204 No Content
- • 206 Partial Content
3xx Redirection
Further action needed to complete the request.
- • 301 Moved Permanently
- • 302 Found
- • 304 Not Modified
- • 307 Temporary Redirect
4xx Client Error
Request contains bad syntax or cannot be fulfilled.
- • 400 Bad Request
- • 401 Unauthorized
- • 403 Forbidden
- • 404 Not Found
5xx Server Error
Server failed to fulfill a valid request.
- • 500 Internal Server Error
- • 502 Bad Gateway
- • 503 Service Unavailable
- • 504 Gateway Timeout
history Evolution of HTTP Status Codes
1.0
HTTP/1.0 (1996)
Introduced basic status codes including 200, 301, 302, 400, 401, 404, 500
1.1
HTTP/1.1 (1997)
Added 100 Continue, 203, 205, 206, 305, 307, and more
2.0
HTTP/2.0 (2015)
Introduced 102 Processing, 208, and 308 status codes
tips_and_updates
Best Practices:
- • Use appropriate status codes for different scenarios
- • Provide helpful error messages for client errors (4xx)
- • Log detailed information for server errors (5xx)
- • Implement proper redirect chains (301 vs 302)
- • Use 429 Too Many Requests for rate limiting