HTTP Status Codes — Complete List
All HTTP status codes from the IANA HTTP Status Code Registry, grouped by class. Click any code for the full guide.
1xx Informational
Informational responses (100–199) indicate that the server has received the request and the client should continue. These are interim responses used primarily in protocol negotiation.
2xx Success
Success responses (200–299) indicate the request was received, understood, and accepted. The specific code tells the client how to interpret the response body and what action, if any, was taken.
3xx Redirect Codes
Redirection responses (300–399) indicate the client must take additional action to complete the request. The choice between permanent and temporary, and between method-preserving and non-preserving redirects, has real implications for SEO, caching, and client behavior.
4xx Client Errors
Client error responses (400–499) indicate the server cannot process the request due to a problem on the client side — malformed syntax, missing authentication, insufficient permissions, or missing resources.
| Code | Name | Guide |
|---|---|---|
| 400 | Bad Request | Guide |
| 401 | Unauthorized | Guide |
| 402 | Payment Required | Guide |
| 403 | Forbidden | Guide |
| 404 | Not Found | Guide |
| 405 | Method Not Allowed | Guide |
| 406 | Not Acceptable | Guide |
| 407 | Proxy Authentication Required | Guide |
| 408 | Request Timeout | Guide |
| 409 | Conflict | Guide |
| 410 | Gone | Guide |
| 411 | Length Required | Guide |
| 412 | Precondition Failed | Guide |
| 413 | Content Too Large | Guide |
| 414 | URI Too Long | Guide |
| 415 | Unsupported Media Type | Guide |
| 416 | Range Not Satisfiable | Guide |
| 417 | Expectation Failed | Guide |
| 418 | I'm a Teapot | Guide |
| 421 | Misdirected Request | Guide |
| 422 | Unprocessable Content | Guide |
| 423 | Locked | Guide |
| 424 | Failed Dependency | Guide |
| 425 | Too Early | Guide |
| 426 | Upgrade Required | Guide |
| 427 | Unassigned | Guide |
| 428 | Precondition Required | Guide |
| 429 | Too Many Requests | Guide |
| 430 | Unassigned | Guide |
| 431 | Request Header Fields Too Large | Guide |
| 451 | Unavailable For Legal Reasons | Guide |
5xx Server Errors
Server error responses (500–599) indicate the server failed to fulfill a valid request. These are almost always actionable on the server side and should be monitored in production.
| Code | Name | Guide |
|---|---|---|
| 500 | Internal Server Error | Guide |
| 501 | Not Implemented | Guide |
| 502 | Bad Gateway | Guide |
| 503 | Service Unavailable | Guide |
| 504 | Gateway Timeout | Guide |
| 505 | HTTP Version Not Supported | Guide |
| 506 | Variant Also Negotiates | Guide |
| 507 | Insufficient Storage | Guide |
| 508 | Loop Detected | Guide |
| 509 | Unassigned | Guide |
| 510 | Not Extended | Guide |
| 511 | Network Authentication Required | Guide |