← all tools
HTTP status codes
WebSearchable reference for every HTTP status code in the IANA registry.
What this tool helps with
Searchable reference for every HTTP status code in the IANA registry. The HTTP status codes tool covers http, status, code, and 200 workflows and is grouped with the rest of the web utilities on often.cloud. Everything runs locally in your browser — there is no upload step, so values you paste in for http work stay on your machine.
| Code | Phrase | Class | Description | |
|---|---|---|---|---|
| 100 | Continue | 1xx Info | Initial part received; client should send the rest. | |
| 101 | Switching Protocols | 1xx Info | Server agrees to switch protocols per Upgrade header. | |
| 102 | Processing | 1xx Info | WebDAV — request received, processing continues. | |
| 103 | Early Hints | 1xx Info | Hint headers (e.g. Link preload) before the final response. | |
| 200 | OK | 2xx Success | Standard success. | |
| 201 | Created | 2xx Success | Resource successfully created; Location header points to it. | |
| 202 | Accepted | 2xx Success | Request accepted but not yet processed. | |
| 203 | Non-Authoritative Information | 2xx Success | Returned metadata may be from a copy or third party. | |
| 204 | No Content | 2xx Success | Success, but no body. | |
| 205 | Reset Content | 2xx Success | Client should reset the document view. | |
| 206 | Partial Content | 2xx Success | Range request fulfilled. | |
| 207 | Multi-Status | 2xx Success | WebDAV — multiple statuses for sub-requests. | |
| 208 | Already Reported | 2xx Success | WebDAV — members already enumerated. | |
| 226 | IM Used | 2xx Success | Delta encoding instance manipulations applied. | |
| 300 | Multiple Choices | 3xx Redirect | Multiple options for the resource. | |
| 301 | Moved Permanently | 3xx Redirect | Resource permanently moved. | |
| 302 | Found | 3xx Redirect | Temporary redirect (legacy method-changing). | |
| 303 | See Other | 3xx Redirect | GET the URL in Location header. | |
| 304 | Not Modified | 3xx Redirect | Conditional GET — cached copy still valid. | |
| 305 | Use Proxy | 3xx Redirect | Deprecated; access through proxy in Location. | |
| 307 | Temporary Redirect | 3xx Redirect | Like 302 but preserves method. | |
| 308 | Permanent Redirect | 3xx Redirect | Like 301 but preserves method. | |
| 400 | Bad Request | 4xx Client | Malformed request. | |
| 401 | Unauthorized | 4xx Client | Authentication required. | |
| 402 | Payment Required | 4xx Client | Reserved for future use. | |
| 403 | Forbidden | 4xx Client | Authenticated, but not authorized. | |
| 404 | Not Found | 4xx Client | No resource at that URL. | |
| 405 | Method Not Allowed | 4xx Client | HTTP method unsupported here. | |
| 406 | Not Acceptable | 4xx Client | Cannot satisfy Accept-* headers. | |
| 407 | Proxy Authentication Required | 4xx Client | Auth needed for proxy. | |
| 408 | Request Timeout | 4xx Client | Client took too long to send request. | |
| 409 | Conflict | 4xx Client | Conflict with current resource state. | |
| 410 | Gone | 4xx Client | Permanently removed. | |
| 411 | Length Required | 4xx Client | Content-Length header required. | |
| 412 | Precondition Failed | 4xx Client | Precondition (If-*) header evaluation failed. | |
| 413 | Content Too Large | 4xx Client | Payload exceeds server limits. | |
| 414 | URI Too Long | 4xx Client | Request URI too long. | |
| 415 | Unsupported Media Type | 4xx Client | Body media type not supported. | |
| 416 | Range Not Satisfiable | 4xx Client | Range request out of bounds. | |
| 417 | Expectation Failed | 4xx Client | Expect header could not be met. | |
| 418 | I'm a teapot | 4xx Client | April Fools' code. | |
| 421 | Misdirected Request | 4xx Client | Server cannot produce response for this URI. | |
| 422 | Unprocessable Content | 4xx Client | Semantic errors prevent processing. | |
| 423 | Locked | 4xx Client | WebDAV — resource is locked. | |
| 424 | Failed Dependency | 4xx Client | WebDAV — dependent request failed. | |
| 425 | Too Early | 4xx Client | Refuses to process replayable request. | |
| 426 | Upgrade Required | 4xx Client | Client must upgrade protocol. | |
| 428 | Precondition Required | 4xx Client | Origin requires conditional request. | |
| 429 | Too Many Requests | 4xx Client | Rate limit exceeded. | |
| 431 | Request Header Fields Too Large | 4xx Client | Headers exceed server limits. | |
| 451 | Unavailable For Legal Reasons | 4xx Client | Resource blocked for legal reasons. | |
| 500 | Internal Server Error | 5xx Server | Generic server failure. | |
| 501 | Not Implemented | 5xx Server | Server doesn't support the functionality. | |
| 502 | Bad Gateway | 5xx Server | Invalid upstream response. | |
| 503 | Service Unavailable | 5xx Server | Overloaded or down for maintenance. | |
| 504 | Gateway Timeout | 5xx Server | Upstream timed out. | |
| 505 | HTTP Version Not Supported | 5xx Server | Protocol version not supported. | |
| 506 | Variant Also Negotiates | 5xx Server | Transparent content negotiation loop. | |
| 507 | Insufficient Storage | 5xx Server | WebDAV — not enough storage. | |
| 508 | Loop Detected | 5xx Server | WebDAV — infinite loop in processing. | |
| 510 | Not Extended | 5xx Server | Further extensions required. | |
| 511 | Network Authentication Required | 5xx Server | Captive portal — auth needed for network. |
How to use HTTP status codes
- Open the HTTP status codes page and paste, type, or generate the http input you want to work with.
- Pick the options you need so the tool can searchable reference for every HTTP status code in the IANA registry
- Copy the status result with one click and use it in your next step — terminal, editor, ticket, or anywhere else you need it.
Common uses
- Reach for HTTP status codes when you need to searchable reference for every HTTP status code in the IANA registry during debugging, code review, or content preparation.
- Skip installing a desktop http app — open this web utility on a shared machine, an iPad, or a colleague's laptop and it just works.
- Bookmark or share the page when you and your team keep coming back to the same http, status, code, and 200 workflow.
FAQ
What does the HTTP status codes tool do?
Searchable reference for every HTTP status code in the IANA registry. It is part of the web utilities on often.cloud and is designed for quick http, status, and code workflows.
Who is the HTTP status codes tool for?
The HTTP status codes tool is useful for developers, operators, support teams, and anyone who needs a fast browser-based way to work with http, status, and code.
Why use the HTTP status codes tool on often.cloud?
often.cloud keeps this workflow focused on speed and convenience, with a dedicated page, direct linking, and a lightweight browser experience for http status codes.