What do the HTTP status code classes mean?

1xx are informational, 2xx mean success, 3xx are redirects, 4xx are client errors (the request was wrong), and 5xx are server errors (the server failed to fulfil a valid request).

What is the difference between 401 and 403?

401 Unauthorized means authentication is missing or failed, so logging in may fix it. 403 Forbidden means the server understood who you are but still refuses access, so credentials will not help.

What is the difference between 301 and 302?

301 Moved Permanently tells clients and search engines the resource has a new permanent URL, so they update bookmarks and links. 302 Found is a temporary redirect — the original URL should still be used in future.

What does a 429 status code mean?

429 Too Many Requests means you have been rate-limited. Slow down and check the Retry-After response header, which says how long to wait before retrying.

When should an API return 404 versus 410?

404 Not Found means the resource is not here (and may exist later). 410 Gone means it existed but has been permanently removed, signalling clients to stop requesting it.

Is anything I search sent to a server?

No. The entire reference and search runs entirely in your browser — nothing you type is uploaded anywhere.

What is the HTTP Status Codes Reference?

A searchable HTTP status code reference covering 1xx through 5xx — 200 OK, 301, 404, 429, 500 and more, each with a plain-English meaning. Runs entirely in your browser, nothing is uploaded. It runs free in your browser on Gera Tools, with nothing uploaded.

HTTP Status Codes Reference

Name: HTTP Status Codes Reference
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

HTTP status codes — searchable reference

A complete, searchable list of the HTTP status codes you hit while building and debugging APIs and websites, each grouped by class with a plain-English meaning. It is the fastest way to answer “what does this code mean?” without leaving your editor.

How it works

Every response carries a three-digit status code, and the first digit gives its class: 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error. This reference lists the codes you actually encounter, organised into those five groups, each with its official name and a short description. Typing in the search box filters the whole table at once, matching the number, the name, or words in the meaning — so a search for redirect, 404, or rate all find the relevant rows.

The codes you meet most often

Code	Name	What it means in practice
200	OK	Request succeeded; body contains the result
201	Created	Resource created; `Location` header points to it
204	No Content	Success with no body (DELETE, no-echo updates)
301	Moved Permanently	Permanent redirect; update bookmarks and links
302	Found	Temporary redirect; keep using the original URL
304	Not Modified	Conditional GET — use your cached copy
400	Bad Request	Malformed request the server cannot parse
401	Unauthorized	Authentication missing or failed
403	Forbidden	Authenticated but permission denied
404	Not Found	No resource at this URL
409	Conflict	State conflict — duplicate, version mismatch
422	Unprocessable Content	Valid syntax but business-rule validation failed
429	Too Many Requests	Rate limited; check `Retry-After` header
500	Internal Server Error	The server failed unexpectedly
502	Bad Gateway	Upstream returned an invalid response
503	Service Unavailable	Temporarily down or overloaded
504	Gateway Timeout	Upstream did not respond in time

How the classes map to error handling

1xx — Informational: Rarely handled explicitly by application code. 100 Continue tells a client to proceed with a request body; 101 Switching Protocols confirms a WebSocket handshake.

2xx — Success: Pick the most specific one. 201 over 200 for creation, 204 over 200 when you have nothing to return. Clients branch on these codes; using 200 everywhere discards machine-readable signal.

3xx — Redirects: 301 is permanent (clients update bookmarks, search engines transfer PageRank). 302 and 307 are temporary. 304 is a caching response — the body is empty and the client reuses its stored copy.

4xx — Client errors: The request was wrong. Fix it before retrying. Exceptions: 408 Request Timeout and 429 Too Many Requests may be retried after waiting.

5xx — Server errors: The request may have been valid; the server failed. Clients should retry idempotent requests (GET, PUT, DELETE) after a delay. For POST, use an Idempotency-Key header to avoid duplicate effects on retry.

Finding confusing status codes

301 vs 302: Permanent vs temporary. Wrong permanent redirect is hard to undo because clients cache it.
401 vs 403: Authentication (401) vs authorization (403). Re-authenticating fixes a 401; it will not fix a 403.
404 vs 410: Not found (404) vs permanently gone (410). Use 410 when you intentionally retire a URL.
502 vs 503: Bad gateway response from upstream (502) vs your own service down/throttled (503).

Search by number, name, or meaning to find the right code instantly. Everything runs in your browser; nothing is uploaded.