An HTTP status code is a three-digit response value that communicates the result of a request, such as success, redirection, client error, or server error. This tool is a searchable reference list, not a URL fetcher: it does not request a website or report a live response. It helps developers and content teams recall common code meanings while debugging routing or API behavior. Keep the distinction clear when investigating an outage, because finding `503 Service Unavailable` in this catalog does not mean that a particular server currently returns 503.
Type a code or description into Search by code or description. The visible list filters as you type, matching either the numeric code string or a case-insensitive substring in the description. Clear the search field to restore all entries. Each row displays the code and its standard short phrase, with a color associated with the broad status class. The component contains a fixed set of common codes rather than every registered or extension status, so use an authoritative protocol reference when the exact semantics of a less common code matter.
For example, type `404` to locate Not Found, or search for `redirect` to see listed redirection phrases such as Moved Permanently and Temporary Redirect. Searching `500` finds Internal Server Error. The search compares the code and description only; it does not interpret a URL, issue an HTTP request, follow redirects, or diagnose a server. To find the current response from your own site, use a browser network panel or an authorized request tool and then consult this list to understand the returned code.
The listed examples span informational 1xx, successful 2xx, redirection 3xx, client-error 4xx, and server-error 5xx values. Rows are colored blue, green, yellow, orange, and red according to numeric ranges. Some codes are omitted, and the text uses concise labels rather than detailed RFC explanations, headers, or response bodies. There is no method selector, request header editor, authentication input, endpoint field, latency measurement, or export control. The tool's role is lookup, not live monitoring or synthetic uptime testing.
Use the reference while implementing API error handling, reviewing redirect behavior, writing support documentation, or explaining why a request failed. SSL Checker links to an external certificate analysis, while this page explains status terminology; neither performs a live HTTP check in its current implementation. Regex Tester can help explore patterns for parsing log snippets, but structured parsing is safer for production logs. Slug Generator can help with URL path formatting, though it does not inspect the response from that path.
Filtering uses a local object imported into the client and the search text remains in page state. No URL or request data is sent because the component does not perform network probing. If a code is absent, the list may simply not include that less common value; the empty list does not mean the code is invalid. The maximum display area scrolls when results are long. Browser rendering is local, so this reference cannot tell whether a remote service is reachable or whether an intermediary changed the response.
When debugging, record the actual method, URL, response code, relevant headers, timestamp, and request identifier from an authorized client or server log. Interpret a status in context: a 404 may be expected for a missing resource, while a 302 may be part of a login flow. Avoid treating all 4xx or 5xx results identically. Use a live monitoring solution for uptime and an official protocol reference for uncommon codes, and confirm whether a status came from the origin, CDN, proxy, or application.
A status class communicates a broad category, while individual code semantics depend on the request and response. For example, 401 commonly indicates that authentication is required or failed, whereas 403 indicates that the server understood the request but refuses it. A 301 suggests a lasting redirect and a 302 is commonly temporary. The short descriptions in this page are reminders, not a full decision tree; examine response headers such as Location, Retry-After, and content type when diagnosing actual behavior.
The search is a simple substring match against the displayed code and phrase. It does not search protocol documentation, category names, headers, or code-specific guidance beyond the short description. If searching a phrase yields no row, try the numeric code or a shorter word. The catalog is shipped as a local object and is not automatically refreshed as standards evolve, so confirm uncommon or newly registered status codes in authoritative references before documenting them in a client contract.
In an API client, handle response classes deliberately: distinguish retryable conditions from permanent validation errors, honor rate limits, and avoid retrying non-idempotent operations without safeguards. A code reference can help interpret a result, but the client needs its own behavior policy. For operations support, pair the observed status with request IDs and server logs rather than repeatedly checking the reference page; this tool has no telemetry, uptime history, or endpoint-specific diagnostics.
Some listed status phrases are abbreviated, and implementations may return additional explanatory text in the body. Treat the phrase as a conventional label rather than a full description of what happened. When writing user-facing errors, translate a technical code into a clear next step instead of displaying only the number. For API consumers, preserve the code and relevant request identifier in diagnostics while avoiding logging secrets or personal data from the request and response.