HTTP Status Codes
Complete reference of all HTTP status codes with descriptions.
| Code | Name | Category | Description |
|---|---|---|---|
| 100 | Continue | Informational | Initial request received; continue |
| 101 | Switching Protocols | Informational | Server switching protocols per upgrade header |
| 102 | Processing | Informational | Server processing request (WebDAV) |
| 103 | Early Hints | Informational | Hints for early response |
| 200 | OK | Success | Request succeeded |
| 201 | Created | Success | Resource successfully created |
| 202 | Accepted | Success | Request accepted for processing |
| 203 | Non-Authoritative Information | Success | Returned by proxy server |
| 204 | No Content | Success | Request succeeded; no content to return |
| 205 | Reset Content | Success | Browser should clear the form |
| 206 | Partial Content | Success | Server returning partial content (range) |
| 207 | Multi-Status | Success | WebDAV: multiple status codes |
| 208 | Already Reported | Success | WebDAV: duplicates previously given |
| 226 | IM Used | Success | Server fulfilled GET with instance-manipulation |
| 300 | Multiple Choices | Redirection | Multiple options for the resource |
| 301 | Moved Permanently | Redirection | Resource permanently moved to new URL |
| 302 | Found | Redirection | Resource temporarily moved (old location) |
| 303 | See Other | Redirection | Look at another URL with GET |
| 304 | Not Modified | Redirection | Cached version is still valid |
| 305 | Use Proxy | Redirection | Access via proxy (deprecated) |
| 307 | Temporary Redirect | Redirection | Temporarily moved; repeat with same method |
| 308 | Permanent Redirect | Redirection | Permanently moved; repeat with same method |
| 400 | Bad Request | Client Error | Malformed request syntax |
| 401 | Unauthorized | Client Error | Authentication required |
| 402 | Payment Required | Client Error | Reserved for future use |
| 403 | Forbidden | Client Error | Server refuses to authorize request |
| 404 | Not Found | Client Error | Resource not found |
| 405 | Method Not Allowed | Client Error | HTTP method not supported |
| 406 | Not Acceptable | Client Error | Server cannot produce accepted response |
| 407 | Proxy Authentication Required | Client Error | Proxy auth needed |
| 408 | Request Timeout | Client Error | Server timed out waiting for request |
| 409 | Conflict | Client Error | Request conflicts with current state |
| 410 | Gone | Client Error | Resource permanently removed |
| 411 | Length Required | Client Error | Content-Length header required |
| 412 | Precondition Failed | Client Error | Precondition in request headers failed |
| 413 | Payload Too Large | Client Error | Request entity too large |
| 414 | URI Too Long | Client Error | Request URI too long |
| 415 | Unsupported Media Type | Client Error | Request format not supported |
| 416 | Range Not Satisfiable | Client Error | Requested range not available |
| 417 | Expectation Failed | Client Error | Expect header not met |
| 418 | I'm a Teapot | Client Error | RFC 2324 Easter egg (HTHPC) |
| 421 | Misdirected Request | Client Error | Request sent to wrong server |
| 422 | Unprocessable Entity | Client Error | WebDAV: valid syntax but semantic error |
| 423 | Locked | Client Error | WebDAV: resource is locked |
| 424 | Failed Dependency | Client Error | WebDAV: dependent method failed |
| 425 | Too Early | Client Error | Server unwilling to risk HTTP downgrade attack |
| 426 | Upgrade Required | Client Error | Client should switch to different protocol |
| 428 | Precondition Required | Client Error | Server requires precondition header |
| 429 | Too Many Requests | Client Error | Rate limit exceeded |
| 431 | Request Header Fields Too Large | Client Error | Headers too large |
| 451 | Unavailable For Legal Reasons | Client Error | Content blocked by legal request |
| 500 | Internal Server Error | Server Error | Generic server error |
| 501 | Not Implemented | Server Error | Server does not support the method |
| 502 | Bad Gateway | Server Error | Invalid response from upstream server |
| 503 | Service Unavailable | Server Error | Server temporarily unavailable (overload/maintenance) |
| 504 | Gateway Timeout | Server Error | Upstream server did not respond in time |
| 505 | HTTP Version Not Supported | Server Error | HTTP version not supported |
| 506 | Variant Also Negotiates | Server Error | Server has internal configuration error |
| 507 | Insufficient Storage | Server Error | WebDAV: server cannot store representation |
| 508 | Loop Detected | Server Error | WebDAV: infinite loop detected |
| 510 | Not Extended | Server Error | Further extensions needed to fulfill request |
| 511 | Network Authentication Required | Server Error | Authentication needed for network access |
Showing 62 of 62 status codes
Report a Problem
Found a bug or have a suggestion? Help us improve this tool.
What is this tool?
HTTP status codes reference tool provides a complete lookup of all HTTP response status codes with explanations. Covers 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error) categories. Includes code number, name, description, and common troubleshooting tips. Essential for web developers and API debugging.
How to use
- 1
Search or browse
Search by code number or browse by category.
- 2
View details
Read description and troubleshooting tips for each code.
- 3
View results
Review the output.
Frequently Asked Questions
What are the most common HTTP error codes?
404 Not Found (page missing), 500 Internal Server Error (server crash), 403 Forbidden (no permission), 401 Unauthorized (not authenticated), 502 Bad Gateway (upstream server error), 503 Service Unavailable (overloaded). 4xx errors are client-side issues; 5xx are server-side problems.
What is the difference between 301 and 302 redirects?
301 Moved Permanently means the resource has permanently moved to a new URL (browsers cache this). 302 Found means the redirect is temporary (browsers keep using the original URL). For SEO, use 301 for permanent moves and 302 for temporary redirects. 301 passes link equity to the new URL.
Is my data processed locally?
Yes, all processing happens in your browser. No data is sent to any server.