How to Look Up an HTTP Status Code Fast

An API call comes back with a 422, or you’re staring at a 308 redirect you don’t fully understand, or debugging why a request returns 409 instead of the 200 you expected. Everyone knows 404 on sight, and most developers recognize 200 and 500, but the specific meaning of less common codes — 422, 308, 409, and the dozens of others in the HTTP spec — isn’t something most people have memorized, and looking each one up individually in scattered documentation is slower than it should be.

HTTP status codes are grouped by their first digit into broad categories (informational, success, redirection, client error, server error), but knowing the category doesn’t tell you the specific, actionable meaning of the exact code you’re looking at.

What HTTP status codes actually communicate

Every HTTP response includes a three-digit status code indicating the outcome of the request — the first digit sets the broad category (1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error), and the full three-digit code narrows that down to a specific meaning. A 404 means “not found,” a 403 means “forbidden” (the server understood the request but refuses to authorize it), and a 401 means “unauthorized” (authentication is required) — three codes that are easy to conflate but mean genuinely different things for how you should respond to them.

Codes outside the common handful — like 429 (too many requests), 503 (service unavailable), or 451 (unavailable for legal reasons) — come up specifically enough that knowing the exact meaning matters for correctly diagnosing what’s actually happening, rather than treating every non-200 response as an undifferentiated error.

Why people get stuck here

• Some codes are easy to confuse with each other. 401 versus 403, or 301 versus 308, have genuinely different meanings that matter for how you handle them, but their similarity makes them easy to mix up from memory.
• Less common codes aren’t memorized the way 404 and 500 are. Codes like 422 or 451 come up rarely enough that most people need to look them up every time, rather than having them memorized.
• Official documentation is dense and technically worded. The formal HTTP specification’s language isn’t written for a quick, practical lookup — it’s precise but not always immediately readable.
• Searching each code individually is slower than having one reference. Doing a web search for each unfamiliar status code you encounter is more friction than having a single, searchable reference available.

What a good HTTP status code reference looks like

Covers the full range, not just the common codes

From 1xx informational codes through 5xx server errors, a complete reference means you’re not stuck searching elsewhere for less common codes.

Explains each code in plain English

A quick, practical explanation of what a code actually means and implies is more immediately useful than dense official specification language.

Searchable by number or keyword

Being able to search either the exact code number or a related keyword (like “redirect” or “unauthorized”) makes it fast to find the right code even if you don’t remember the exact number.

Common mistakes to avoid

• Confusing 401 (unauthorized — authentication needed) with 403 (forbidden — authenticated but not permitted), which call for different handling in your code.
• Treating every 4xx or 5xx response as an undifferentiated “error” without checking the specific code for what it actually indicates about the failure.
• Assuming a 3xx redirect code always means the same thing — 301, 302, 307, and 308 have meaningfully different implications for whether the redirect is permanent and whether the request method should change.
• Not checking whether an API you’re integrating with uses status codes in a nonstandard way, which does happen despite the formal specification.
• Overlooking less common but meaningful codes (like 429 for rate limiting) that call for a specific response, like backing off and retrying later.

How to do it with HTTP Status Code Reference

Online Tool Store’s HTTP Status Code Reference covers 100 to 500-series codes with plain-English explanations, searchable by number or keyword, entirely in your browser.

1. Search by the specific code number, or a related keyword.
2. Get a plain-English explanation of what the code means.
3. Use it to correctly diagnose an API response or debug a redirect.
4. Look up as many codes as you need without leaving the page.

Because it’s searchable and explained in plain language, it’s faster than digging through formal specification documents for a quick, practical answer.

Frequently asked questions

What’s the difference between 401 and 403?

401 means the request lacks valid authentication credentials — you need to log in or provide a valid token. 403 means the server understood who you are but is refusing to authorize the specific action — being logged in doesn’t help if you don’t have permission for that particular resource.

Why are there so many different 3xx redirect codes?

Each communicates a different nuance — whether the redirect is temporary or permanent, and whether the client should preserve the original request method (like POST) when following the redirect — details that matter for how browsers and API clients should correctly handle the response.

Is a 5xx error always the server’s fault, and 4xx always the client’s?

Generally, yes — that’s the intended distinction, with 4xx codes indicating a problem with the request itself and 5xx codes indicating the server failed to fulfill an otherwise valid request. In practice, a 5xx can sometimes be triggered by an edge-case client input the server didn’t handle gracefully, so it’s not always a perfectly clean line.

Final thought

HTTP status codes are precise and well-specified, but nobody has the full list memorized beyond the handful that come up daily. Keep a fast, plain-English reference on hand for the rest instead of doing a fresh search every time one comes up.

Try the free HTTP Status Code Reference