HTTP & WebLOCALRuns in your browser
HTTP Status Reference
Search common registered HTTP response status codes and their standard meanings.
This tool handles input and primary processing in your browser and is designed not to send the input to QuickKit’s server.
| Code | Reason phrase | Meaning | Class | Reference |
|---|---|---|---|---|
| 100 | Continue | Request can continue | Informational | RFC 9110 |
| 101 | Switching Protocols | Protocol switch | Informational | RFC 9110 |
| 102 | Processing | Request is being processed | Informational | RFC 2518 |
| 103 | Early Hints | Preliminary response hints | Informational | RFC 8297 |
| 104 | Upload Resumption Supported | Upload resumption supported | Informational | draft-ietf-httpbis-resumable-upload-05 (Temporary until 2026-11-13) |
| 200 | OK | Request succeeded | Success | RFC 9110 |
| 201 | Created | Resource created | Success | RFC 9110 |
| 202 | Accepted | Request accepted | Success | RFC 9110 |
| 203 | Non-Authoritative Information | Non-authoritative metadata | Success | RFC 9110 |
| 204 | No Content | No response content | Success | RFC 9110 |
| 205 | Reset Content | Reset the document view | Success | RFC 9110 |
| 206 | Partial Content | Partial representation | Success | RFC 9110 |
| 207 | Multi-Status | Multiple operation statuses | Success | RFC 4918 |
| 208 | Already Reported | Already reported | Success | RFC 5842 |
| 226 | IM Used | Instance manipulations applied | Success | RFC 3229 |
| 300 | Multiple Choices | Multiple representations | Redirection | RFC 9110 |
| 301 | Moved Permanently | Permanent new URL | Redirection | RFC 9110 |
| 302 | Found | Temporary different URL | Redirection | RFC 9110 |
| 303 | See Other | Another URL via GET | Redirection | RFC 9110 |
| 304 | Not Modified | Cached representation valid | Redirection | RFC 9110 |
| 305 | Use Proxy | Use a proxy | Redirection | RFC 9110 |
| 306 | (Unused) | Unused | Redirection | RFC 9110 |
| 307 | Temporary Redirect | Temporary new URL | Redirection | RFC 9110 |
| 308 | Permanent Redirect | Permanent new URL | Redirection | RFC 9110 |
| 400 | Bad Request | Invalid request | Client Error | RFC 9110 |
| 401 | Unauthorized | Authentication required | Client Error | RFC 9110 |
| 402 | Payment Required | Payment required | Client Error | RFC 9110 |
| 403 | Forbidden | Request refused | Client Error | RFC 9110 |
| 404 | Not Found | Target not found | Client Error | RFC 9110 |
| 405 | Method Not Allowed | Method not supported | Client Error | RFC 9110 |
| 406 | Not Acceptable | No acceptable representation | Client Error | RFC 9110 |
| 407 | Proxy Authentication Required | Proxy authentication required | Client Error | RFC 9110 |
| 408 | Request Timeout | Request timed out | Client Error | RFC 9110 |
| 409 | Conflict | Resource state conflict | Client Error | RFC 9110 |
| 410 | Gone | Target permanently unavailable | Client Error | RFC 9110 |
| 411 | Length Required | Content-Length required | Client Error | RFC 9110 |
| 412 | Precondition Failed | Request precondition false | Client Error | RFC 9110 |
| 413 | Content Too Large | Request content too large | Client Error | RFC 9110 |
| 414 | URI Too Long | Target URI too long | Client Error | RFC 9110 |
| 415 | Unsupported Media Type | Media type unsupported | Client Error | RFC 9110 |
| 416 | Range Not Satisfiable | Requested range unavailable | Client Error | RFC 9110 |
| 417 | Expectation Failed | Expectation not met | Client Error | RFC 9110 |
| 418 | (Unused) | Unused | Client Error | RFC 9110 |
| 421 | Misdirected Request | Wrong destination server | Client Error | RFC 9110 |
| 422 | Unprocessable Content | Instructions cannot be processed | Client Error | RFC 9110 |
| 423 | Locked | Resource locked | Client Error | RFC 4918 |
| 424 | Failed Dependency | Dependent action failed | Client Error | RFC 4918 |
| 425 | Too Early | Replay risk | Client Error | RFC 8470 |
| 426 | Upgrade Required | Protocol upgrade required | Client Error | RFC 9110 |
| 428 | Precondition Required | Conditional request required | Client Error | RFC 6585 |
| 429 | Too Many Requests | Request rate exceeded | Client Error | RFC 6585 |
| 431 | Request Header Fields Too Large | Request headers too large | Client Error | RFC 6585 |
| 451 | Unavailable For Legal Reasons | Unavailable for legal reasons | Client Error | RFC 7725 |
| 500 | Internal Server Error | Unexpected server condition | Server Error | RFC 9110 |
| 501 | Not Implemented | Functionality unsupported | Server Error | RFC 9110 |
| 502 | Bad Gateway | Invalid upstream response | Server Error | RFC 9110 |
| 503 | Service Unavailable | Temporarily unable to handle request | Server Error | RFC 9110 |
| 504 | Gateway Timeout | Upstream response timed out | Server Error | RFC 9110 |
| 505 | HTTP Version Not Supported | HTTP version unsupported | Server Error | RFC 9110 |
| 506 | Variant Also Negotiates | Negotiation configuration error | Server Error | RFC 2295 |
| 507 | Insufficient Storage | Unable to store representation | Server Error | RFC 4918 |
| 508 | Loop Detected | Infinite loop detected | Server Error | RFC 5842 |
| 510 | Not Extended | Policy not fulfilled | Server Error | RFC 2774 (Obsoleted) |
| 511 | Network Authentication Required | Network authentication required | Server Error | RFC 6585 |
Curated reference; consult the relevant specification for full semantics.
How it works
A searchable, curated reference of common HTTP status codes registered by IANA or defined by the HTTP specifications. A status code describes a response class; it does not by itself explain an application's outcome.