Account

What new tool do you want?

Developer Tools

HTTP Status Codes

Look up every HTTP status code — 200, 301, 404, 429, 502 and more — with what it means and when servers send it.

How to use

  1. 1Type a code or keyword, like 429 or 'redirect'.
  2. 2Read the meaning and typical cause.

Frequently asked questions

What's the difference between 301 and 302?

301 is permanent — search engines move ranking to the new URL. 302 is temporary and the original URL keeps its ranking.

What's the difference between 401 and 403?

401 means you're not authenticated (log in and retry). 403 means you're authenticated but not allowed to access the resource.

What causes a 502 Bad Gateway?

A proxy or load balancer couldn't get a valid response from the app server behind it — it crashed, timed out or returned garbage.

A worked example of a confusing pair

502 Bad Gateway and 504 Gateway Timeout look similar but point to different failures: 502 means a proxy or load balancer got a response from the upstream app server, but it was invalid or malformed (the app crashed mid-response, or returned something the proxy can't parse). 504 means the proxy got no response at all within its timeout window — the app might be alive but just too slow, stuck in a long database query, or genuinely hung. If you're debugging one of these in production, that distinction tells you where to look first: 502 points at application errors and crash logs, 504 points at slow queries, deadlocks, or an upstream that's unreachable.

Why the table groups codes by their first digit

The leading digit of every HTTP status code is itself meaningful under RFC 9110 — 1xx is informational, 2xx is success, 3xx is redirection, 4xx is a client error (you did something wrong — bad syntax, missing auth, a request for something that doesn't exist), and 5xx is a server error (the server is at fault, not you). That classification is why a well-behaved client can make reasonable decisions about an unfamiliar code it's never seen before — a client encountering an unknown 4xx code it doesn't specifically handle still knows not to retry the exact same request unmodified, while an unknown 5xx code is often safe to retry after a delay.

The codes that are commonly confused in practice

401 vs 403 trips up almost everyone building an API: 401 Unauthorized actually means "you're not authenticated at all — log in and retry," while 403 Forbidden means "we know who you are, and you're still not allowed." Similarly, 301 vs 302 matters for SEO specifically — a 301 tells search engines to transfer the old URL's ranking to the new one permanently, while a 302 keeps ranking on the original URL because the redirect is only supposed to be temporary. Using 302 for what's actually a permanent move is a common and costly SEO mistake.

Why 429 carries a header most client code ignores

429 Too Many Requests is one of the few status codes that's meant to come with instructions attached — servers are supposed to send a Retry-After header telling the client exactly how many seconds (or until what timestamp) to wait before trying again. A client that just retries immediately in a loop on any 4xx or 5xx is effectively attacking the API it's trying to use, and well-behaved rate-limited integrations parse that header and back off accordingly rather than guessing. This is also why 429 lives in the 4xx client-error range rather than 5xx: the server is working fine, the caller is the one that needs to slow down.

Why idempotent methods change how you should react to an error

Whether it's safe to automatically retry a failed request depends on the HTTP method, not just the status code: GET, PUT and DELETE are defined as idempotent — running them twice has the same effect as running them once, so retrying after a 502 or 504 is safe. POST is not idempotent, so blindly retrying a timed-out POST (say, a payment or an order submission) risks creating the resource twice if the first request actually succeeded server-side and only the response was lost in transit. That's why production retry logic almost always treats POST differently from GET/PUT/DELETE regardless of which 5xx code triggered the retry.

Related tools

More: Developer Tools