HTTP Status Code Lookup
Searchable dictionary of HTTP status codes, names, meanings, and RFC references.
Client-Side Execution & Privacy Guarantee
This utility executes 100% locally in your web browser. Your inputs, tokens, queries, and data payloads are never transmitted to any external server or backend.
HTTP status codes are three-digit integers returned by a server to indicate the result of a request. They are grouped into five classes: 1xx informational, 2xx success, 3xx redirection, 4xx client error and 5xx server error. The definitive list is maintained by IANA and defined primarily by RFC 9110.
This lookup lets you search by code number or by keyword, then displays the official reason phrase, a concise explanation of when the code is used, the class it belongs to, and the RFC section that registers it. Non-standard codes that appear frequently in nginx, Cloudflare and load-balancer logs are also included so you can interpret real-world responses.
The five classes
Codes 100-199 are informational and are rarely seen by end-user applications; 100 Continue and 101 Switching Protocols are the most common. Codes 200-299 signal that the request succeeded; 200 OK, 201 Created and 204 No Content cover the majority of successful API calls. Codes 300-399 indicate that the client must take further action, typically by following a Location header (301, 302, 307, 308).
Codes 400-499 mean the client sent something the server cannot or will not process. 400 Bad Request, 401 Unauthorized, 403 Forbidden and 404 Not Found are the ones developers encounter daily. Codes 500-599 indicate that the server failed while attempting to fulfill a valid request; 500 Internal Server Error and 503 Service Unavailable are the most frequent.
RFC 9110 and the IANA registry
RFC 9110 (HTTP Semantics) consolidates and replaces earlier documents and is the current authoritative source for the core status codes. Each registered code points to a specific section of that RFC or to an earlier extension RFC (for example 207 Multi-Status is defined in RFC 4918). The IANA HTTP Status Code Registry lists every assigned code together with its reference.
When you look up a code the tool shows the exact RFC citation so you can open the original text if you need the full semantics, including required headers or interaction with particular HTTP methods.
Non-standard codes in the wild
Production systems often emit codes that are not in the IANA registry. nginx uses 444 to close a connection without a response and 499 when the client closed the connection before the server finished. Cloudflare’s 520-530 range signals problems between the edge and the origin. Some AWS load balancers return 460 or 561.
The lookup includes these unofficial codes with a clear “non-standard” label and a short description of the product that emits them, so log analysis does not require a separate search.
When to use this tool
- Interpreting an unexpected status code in an API response or server log
- Choosing the most accurate code for a new endpoint you are implementing
- Writing documentation or error-handling logic that must cite the correct RFC
- Explaining a 4xx or 5xx failure to a colleague or customer
- Checking whether a code you see in production is official or vendor-specific
How to use the HTTP Status Code Lookup
- Type a three-digit code or a keyword such as “not found” or “redirect” into the search box.
- Matching codes appear instantly, grouped by class.
- Select a code to see its reason phrase, category, plain-language meaning and RFC reference.
- Use the class filters (1xx, 2xx, ...) to narrow the list when you are exploring rather than looking up a known number.
- Copy the reason phrase or the RFC citation if you need it for a comment or a ticket.
- For non-standard codes the entry is marked accordingly and names the software that commonly produces it.
Worked examples
Classic client error
404
404 Not Found Category: Client Error The server cannot find the requested resource. RFC 9110, Section 15.5.5
Returned when the URI does not map to any resource the server is willing to disclose.
Successful creation
201
201 Created Category: Success The request succeeded and a new resource was created. RFC 9110, Section 15.3.2
Typically accompanied by a Location header pointing to the new resource.
Common mistakes and tips
- Prefer the most specific code that accurately describes the outcome. Returning 200 with an error object in the body is a common anti-pattern that confuses clients and monitoring.
- 301 and 308 are permanent redirects and may be cached by clients; 302 and 307 are temporary. Choose carefully.
- 401 means “authentication required or failed”; 403 means “authenticated but not authorized.” Mixing them up leads to incorrect client behavior.
- When you see a non-standard code, check the vendor documentation; the meaning is not portable across servers.
- The Reason-Phrase is optional in HTTP/2 and HTTP/3; rely on the numeric code, not the text, for programmatic decisions.
Frequently asked questions
What is the difference between 301 and 302?
301 Moved Permanently tells clients and caches that the resource has a new permanent URI. 302 Found is a temporary redirect; clients should continue to use the original URI for future requests.
Is 418 I’m a teapot a real status code?
It was defined as an April Fools’ joke in RFC 2324 and is registered but marked unused in the current registry. Most production servers do not emit it.
Where can I find the official list?
The IANA HTTP Status Code Registry and RFC 9110 are the authoritative sources. This tool mirrors that data for quick reference.
Why do some codes appear in logs but not in the RFC?
Vendors such as nginx, Cloudflare and cloud load balancers define private codes for operational conditions. They are listed here with a non-standard flag.
Does looking up a code send any data?
No. The entire dictionary is loaded in the browser and searches are performed locally.