What this tool calculates
This is a deterministic reference lookup rather than a numerical calculator. Enter a status number, description fragment, or category and the page filters its built-in table to matching HTTP response codes. Each result shows the three-digit code, its short description, and its response class.
An HTTP status is sent by a server after it receives a request. It describes the outcome at the protocol level; it does not expose every application detail. A code can be technically correct while the user experience is still poor, and the same visible failure can arise from a browser, proxy, cache, gateway, origin server, or application.
Inputs
The search field accepts text. A number such as 404 targets a specific code. A phrase such as not found searches descriptions. A category term can narrow the table to a family. Search is case-insensitive and does not make a network request to the URL you are debugging.
For incident notes, capture more than the code: request method, target URL, response headers, timestamp, redirect chain, and the component that generated the response. Do not paste authorization headers, session cookies, private tokens, or personal data into a shared report.
Method and formula
HTTP codes have three digits. The first digit identifies the broad class:
- 1xx: informational progress.
- 2xx: the request was received and processed successfully at the HTTP layer.
- 3xx: the client needs redirection or another action to complete retrieval.
- 4xx: the request cannot be fulfilled as sent, often because of syntax, authorization, state, or target availability.
- 5xx: the server or an upstream component failed while attempting a valid-looking request.
The lookup performs normalized substring matching over the code, phrase, and class fields. It does not guess a cause, query an external registry at runtime, or treat unregistered numbers as standardized meanings.
Worked example
Search for 404. The matching row is 404 Not Found, a 4xx client-error response. In HTTP semantics, this says the origin server did not find a current representation for the requested target, or is unwilling to disclose that one exists.
The next debugging step depends on context. Check the exact path and method, route deployment, case sensitivity, rewrite rules, and whether a reverse proxy changed the request. A 404 from a CDN-branded error page may have a different source than a JSON 404 generated by the application.
As a contrasting example, 500 Internal Server Error belongs to 5xx. It signals an unexpected server-side failure, but it does not identify the failed function. Logs and a request correlation identifier are still needed.
How to interpret the result
Use the class to triage, then use the exact definition and response headers to choose the next observation. A 401 typically calls for authentication information; a 403 says the server understood the request but refuses it; a 429 points to rate limiting and may include Retry-After. Those distinctions affect the correct client behavior.
Do not make application logic depend on the English reason phrase. Protocol behavior is defined by the numeric code, and reason phrases can be customized or omitted. Also distinguish the final response from intermediate redirects and cached responses when diagnosing a browser trace.
Accuracy and limitations
The table is an educational snapshot of commonly standardized codes. HTTP extensions can register additional values, vendors sometimes emit non-standard codes, and specifications can be updated. The lookup cannot confirm which component produced a response, whether a retry is safe, or whether the body contains useful problem details.
Security controls may intentionally return a less revealing status. A missing-looking resource could be hidden for authorization reasons, and a gateway can replace an origin response. Verify production behavior with appropriate logs and observability while protecting secrets and user data.
Sources
- RFC 9110: HTTP Semantics defines status-code classes and the semantics of core response codes.
- IANA HTTP Status Code Registry is the maintained registry for standardized code assignments and their specification references.
Editorial record
Author: SoupCalc Editorial Team
Last reviewed: August 14, 2026
Review scope: Code-class explanations, lookup behavior, the 404 Not Found example, diagnostic boundaries, and links to the HTTP specification and registry were checked.