HTTP Status Codes
All 1xx-5xx codes with instant keyword filtering
Status Code Lookup
| Code | Name | Description |
|---|
How to Use
An HTTP status code is the server three-digit verdict on every request, and the leading digit tells you the family: 1xx means received and still processing, 2xx success, 3xx redirection, 4xx something is wrong with the request, and 5xx the server failed on its own. The everyday offenders are 404 (not found), 401 (unauthenticated), 429 (too many requests), 500 (internal server error) and 502 (bad gateway) - knowing those five alone clears most debugging sessions.
This page lists over 50 status codes from 1xx through 5xx, each with its official English name and a one-line explanation. Type a number like 429 or a keyword such as redirect, timeout or cache in the search box and the table filters instantly, matching codes, names and both descriptions so you can find a code by meaning even when the number escapes you. The table renders locally with zero network requests and no sign-up - just look it up and go.
FAQ
What is the difference between 301 and 302?
Both mean the resource has moved; the difference is how search engines treat them. 301 is permanent and passes ranking to the new address, while 302 is temporary and keeps the original URL indexed. Browsers follow both identically, so a wrong choice mainly affects SEO, not functionality.
How do I tell 4xx and 5xx problems apart?
4xx points at the caller: bad parameters (400), missing authentication (401), insufficient permissions (403), wrong address (404) or excessive rate (429). 5xx points at the server side: code exceptions (500), upstream failures (502) or temporary overload (503). Check the request first on 4xx; check server logs first on 5xx.
Why are some status codes missing from the table?
This page covers the 50+ codes defined by RFC standards and mainstream implementations. Extension codes such as Nginx 444 or some CDN 52x codes are custom to specific software and not part of the standard list; for those, consult the documentation of the server or gateway that produced them.