Continue
Initial part of a request was received and the client should continue with it.
HTTP Status Codes
Searchable reference for HTTP status codes with descriptions and RFC references.
62 shown
1xxInformational · 4
RFC 9110
Switching Protocols
Server agrees to switch protocols based on the Upgrade header.
Processing
Server has accepted the request but is still processing it (WebDAV).
Early Hints
Send preliminary headers (Link, etc.) before the final response.
2xxSuccess · 10
OK
Request succeeded.
Created
Request succeeded and a new resource was created.
Accepted
Request was accepted for processing but has not yet completed.
Non-Authoritative Information
Returned metainformation differs from the origin server's response.
No Content
Request succeeded; no body to return.
Reset Content
Request succeeded; the client should reset the document view.
Partial Content
Range request succeeded.
Multi-Status
Body is an XML message with status for multiple resources (WebDAV).
Already Reported
Members of a WebDAV binding were already enumerated.
IM Used
Server fulfilled a GET request and the response is a representation of one or more instance manipulations.
3xxRedirection · 8
Multiple Choices
Multiple representations are available; the client may choose.
Moved Permanently
Resource has a new permanent URI.
Found
Resource is temporarily under a different URI.
See Other
Response is found under a different URI; client should GET it.
Not Modified
Conditional GET: the cached representation is still fresh.
Use Proxy
Deprecated. Resource must be accessed through a proxy.
Temporary Redirect
Resource is temporarily under a different URI; method must not change.
Permanent Redirect
Resource has a new permanent URI; method must not change.
4xxClient error · 29
Bad Request
Server cannot or will not process the request due to a client error.
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use.
Forbidden
Server understood the request but refuses to authorize it.
Not Found
Server can't find the requested resource.
Method Not Allowed
Method is known but not supported by the target resource.
Not Acceptable
Resource cannot generate content matching the Accept headers.
Proxy Authentication Required
Client must authenticate with a proxy first.
Request Timeout
Server timed out waiting for the client.
Conflict
Request conflicts with the current state of the resource.
Gone
Resource is permanently unavailable.
Length Required
Server requires the Content-Length header.
Precondition Failed
Precondition in request headers failed.
Content Too Large
Request body is larger than the server is willing to process.
URI Too Long
Request URI is longer than the server is willing to interpret.
Unsupported Media Type
Request body is in a format the server doesn't support.
Range Not Satisfiable
None of the ranges in the Range header overlap the resource.
Expectation Failed
Expectation in the Expect header could not be met.
I'm a teapot
Server is a teapot. April Fools' joke from RFC 2324; widely implemented as an Easter egg.
Misdirected Request
Request was directed to a server unable to produce a response.
Unprocessable Content
Request is well-formed but semantically invalid.
Locked
Resource is locked (WebDAV).
Failed Dependency
Request failed because of a previous request (WebDAV).
Too Early
Server is unwilling to risk processing a request that might be replayed.
Upgrade Required
Client must switch to a different protocol.
Precondition Required
Server requires the request to be conditional.
Too Many Requests
Client has sent too many requests in a given time (rate limited).
Request Header Fields Too Large
One or more request headers (or all of them) are too large.
Unavailable For Legal Reasons
Resource is unavailable due to legal demands.
5xxServer error · 11
Internal Server Error
Server encountered an unexpected condition.
Not Implemented
Server does not support the functionality required.
Bad Gateway
Server, while acting as a gateway, got an invalid response from upstream.
Service Unavailable
Server is currently unable to handle the request (overloaded or down).
Gateway Timeout
Server, while acting as a gateway, didn't get a response in time.
HTTP Version Not Supported
Server doesn't support the HTTP version in the request.
Variant Also Negotiates
Transparent content negotiation results in a circular reference.
Insufficient Storage
Server cannot store the representation needed to complete the request (WebDAV).
Loop Detected
Server detected an infinite loop while processing (WebDAV).
Not Extended
Further extensions to the request are required.
Network Authentication Required
Client needs to authenticate to gain network access (captive portal).
Inputs stay on this device. Every developer tool on TaskKit runs entirely in your browser. Tokens, payloads, and pasted text are not transmitted to TaskKit servers or third parties.
What this tool does
A searchable reference for every standard HTTP status code, organized by class (1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error). Search by number, by name, or by description. Each entry includes the canonical reason phrase and the RFC where it's defined.
When you'd use it
- Deciding between
401 Unauthorizedand403 Forbiddenfor a denied request. - Confirming whether a redirect should be
302,303,307, or308. - Looking up an unfamiliar code that just appeared in a log line.
- Checking which RFC introduced a code (e.g.
451 Unavailable For Legal Reasonsis RFC 7725).
How it works
The dataset is static and ships in the page bundle. There's no API call — search runs against an in-memory index, so it's instant even on slow connections. Each code's metadata comes directly from the IANA HTTP Status Code Registry and the relevant RFCs (mostly 9110, with older codes still pointing at 7231 and earlier).
Notes
401 vs. 403? 401 means "you didn't prove who you are — try again with credentials." 403 means "I know who you are and you can't have this." If the user logging in would change the answer, return 401; if not, return 403.
302 vs. 307? 302 was originally meant to preserve the request method on redirect, but most browsers historically rewrote POST to GET. 303 and 307 were added to make the intent explicit: 303 See Other always GETs the new URL, 307 Temporary Redirect always preserves the method. Use 303 after a successful POST, 307 for a method-preserving temporary redirect.
Is 418 I'm a teapot real? Yes, and it's still in RFC 2324 (April 1, 1998) and acknowledged in RFC 9110 §15.5.19. Use sparingly.
Related tools
- cURL ↔ fetch — replay requests to see codes live
- JSON Formatter — for inspecting response bodies