HTTP Status Codes — Quick Reference

Every HTTP response starts with a three-digit code. Look up the common ones instantly, understand what the server is telling you, and learn the right way for a client to react. The tool lists about 40 frequently met codes, not every registered one.

The five classes

1xx Informational — the request was received, keep going (100 Continue, 101 Switching Protocols for WebSockets). 2xx Success — it worked (200 OK, 201 Created, 204 No Content). 3xx Redirection — look elsewhere (301/308 permanent, 302/307 temporary, 304 Not Modified for caching). 4xx Client Error — the request is wrong (400, 401, 403, 404, 409, 422, 429). 5xx Server Error — the server failed (500, 502, 503, 504).

The ones people mix up

401 Unauthorized really means unauthenticated: no valid credentials were supplied, and the client may retry with credentials. 403 Forbidden means the server knows who you are and still says no. 404 means the resource does not exist (or the server chooses not to reveal it). 301 and 308 are both permanent redirects, but only 308 guarantees the method and body are preserved — 301 may be changed to GET. Likewise 307 is the method-preserving twin of 302.

502 Bad Gateway means a proxy or load balancer got an invalid response from the upstream server; 503 Service Unavailable means the server is overloaded or down for maintenance (often with a Retry-After header); 504 Gateway Timeout means the upstream did not respond in time.

Designing good API responses

Return 201 with a Location header after creating a resource, 204 for successful deletes with no body, 409 Conflict for duplicate or version-mismatch writes, 422 Unprocessable Content for well-formed but semantically invalid input, and 429 Too Many Requests with Retry-After when rate limiting. Avoid returning 200 with an error inside the body — it defeats every HTTP client, cache and monitoring tool.

How to use it

  1. Type a code (e.g. 422) or a word (e.g. timeout) into the search box.
  2. Read the official name and a plain-language description, plus a hint about when it is typically returned.
  3. Use the class buttons to browse all 4xx or 5xx codes while designing an API, and click a card to copy the code number.

Quick lookup

The codes you will meet most often:

200 OK                 success, body contains the result
201 Created            resource created; see Location header
204 No Content         success, intentionally empty body
301 Moved Permanently  update bookmarks/links; may change POST to GET
304 Not Modified       cached copy is still valid
400 Bad Request        malformed syntax or invalid parameters
401 Unauthorized       authenticate and retry
403 Forbidden          authenticated but not allowed
404 Not Found          no such resource
429 Too Many Requests  back off; honour Retry-After
500 Internal Server Error  unhandled server exception
503 Service Unavailable    overloaded or in maintenance

Common use cases

Searching the list

The search box matches the code, the official name and the description text, and the buttons filter by class. Typing timeout returns 408 Request Timeout and 504 Gateway Timeout; redirect returns 302, 303, 307 and 308. Clicking a card copies the code number. The list contains about 40 of the most commonly met codes rather than every registered one: for example 418 is not included, so searching for it returns nothing.

A practical reading order for a failing request: first the class (4xx means fix the request, 5xx means the server or an upstream failed), then the exact code, then the "when" hint on the card. Pair a 401 or 403 with the JWT Decoder to inspect the token, and a 400 or 422 with the cURL Builder to recheck headers and body.

Frequently asked questions

What is the difference between 401 and 403?

401 means authentication is missing or invalid — try again with credentials. 403 means you are authenticated but not permitted; retrying with the same identity will not help.

Should I retry on a 500 error?

Sometimes. 502, 503 and 504 are usually transient and safe to retry with backoff. A 500 may indicate a bug that will fail every time; retry once with caution and alert if it persists.

What does 418 I'm a teapot mean?

It is an April Fools' joke from RFC 2324 (Hyper Text Coffee Pot Control Protocol). Some servers return it to block scrapers. It is not a real HTTP semantic, and it is not in this tool's list, so searching for it finds nothing.

What is the difference between 301 and 308?

Both are permanent redirects. 308 requires the client to repeat the same method and body; 301 historically allowed browsers to switch POST to GET.

Why can't I find 418 or 412?

The reference lists about 40 of the most common codes. Codes that are rare or joke codes, such as 418, are not included, so search for the nearest class instead.

Related tools

Explore all developer tools →