An HTTP status code lookup answers one question fast: what does this three-digit number mean? Every HTTP response starts with a status code, and the code tells the browser, a search engine crawler or an API client whether the request worked, where to go next, or who made the mistake. Type a code such as 404 or a word such as redirect, and this page lists every matching code with its official name, a short explanation in plain words and the specification that defines it.
The list follows the IANA registry of HTTP status codes [2] and the status code section of RFC 9110, the current HTTP semantics standard [1]. It covers the codes that are assigned, from 100 Continue to 511 Network Authentication Required, including the WebDAV extensions and the two numbers the standard keeps as unused.
How to use the HTTP status code lookup
- Type a full code, such as 301, in the search box.
- Type the first digits, such as 40 or 4xx, to see a whole family of codes.
- Type a word, such as gateway, moved or limit, to search the names and the explanations. Several words must all match.
- Press a class button (1xx to 5xx) to narrow the list to one class, or All to remove the filter.
- Press Clear to see the full list again.
The five classes of status codes
The first digit of a code gives its class [1]. The class is often all you need to know when you are reading a log or debugging a request.
| Class | Name | Meaning | Example |
|---|---|---|---|
| 1xx | Informational | The request was received and the process continues. | 100 Continue |
| 2xx | Success | The request was received, understood and accepted. | 200 OK |
| 3xx | Redirection | The client must take another step, usually to another address. | 301 Moved Permanently |
| 4xx | Client error | The request looks wrong or cannot be allowed. | 404 Not Found |
| 5xx | Server error | The server failed on a request that looked valid. | 503 Service Unavailable |
Codes people look up most
404 Not Found means the server has nothing at that address, or does not want to say that it does. 410 Gone says more: the page existed and was removed on purpose, so crawlers can drop it sooner. 403 Forbidden means the server understood the request and refuses it, while 401 Unauthorized means valid credentials are missing, so the client may try again with a login.
301 Moved Permanently and 308 Permanent Redirect both announce a new permanent address. The difference is that 308 keeps the request method and body unchanged when the request is repeated, and so does 307 Temporary Redirect, while older clients may turn a POST into a GET after 301 or 302. Use 301 for normal page moves and a 307 or 308 when an API call must be repeated exactly.
500 Internal Server Error is the general server failure. 502 Bad Gateway and 504 Gateway Timeout come from a proxy or gateway that received a bad response, or none, from the server behind it. 503 Service Unavailable is the polite answer during maintenance or overload, and it can carry a Retry-After header. 429 Too Many Requests is how rate limits are reported.
Worked example: a failed form submission
Suppose a contact form returns 422. Search for 422 and you will find Unprocessable Content: the request was well formed, but the server could not process what was in it, for example because a field failed validation. A 400 would point to a malformed request, a 413 to a body that is too large and a 415 to a format the server does not accept. Reading the code first saves you from guessing in the wrong place.
Status codes and search engines
- A page that answers 200 is eligible to be crawled and indexed.
- A 301 or 308 tells crawlers to move the page to the new address; a 302 or 307 suggests the move is temporary.
- A 404 or 410 tells crawlers that the page is not there; 410 is the stronger signal that it was removed on purpose.
- A 5xx response signals a server problem; crawlers usually come back later and slow down if it lasts.
Reading status codes in practice
When a page misbehaves, open your browser’s developer tools, go to the network panel and look at the status column next to the request. A page that looks broken but shows 200 usually has a problem in the content or the script. A page that shows 301 or 302 followed by another request is being redirected, and a long chain of redirects slows the page down and is worth shortening to a single step.
For API work, the code decides what your program does next. A 201 after a POST tells you the new item exists, a 204 says the action worked and no data is returned, 409 reports a conflict with the current state and 429 asks you to slow down. Many APIs also add a body with details, so read both the code and the message.
- Log the status code with every failed request; it narrows a problem down faster than the message alone.
- Retry 502, 503 and 504 responses with a delay, because they are often short-lived.
- Do not retry 400, 401 or 403 responses without changing something, because the same request will fail again.
- Return the most specific code you can, so that clients and crawlers can react correctly.
Things to remember
Status codes are registered in a public registry, so the list can grow [2]. Some numbers are reserved or unused: 306 and 418 are marked unused in the standard [1], and 418 is remembered as a joke from an April Fools specification. A server may also send a code that is not on this list; a client that does not know it should treat it like the first code of the same class, for example any unknown 4xx as a 400.
- The reason phrase after the number, such as OK, is only a label. Clients act on the number.
- The same number can mean slightly different things in WebDAV or API contexts; the Defined in column shows the source.
- A browser shows its own error page for some codes, but the status code itself is still what the server sent.
What next
Use this often? Add HTTP Status to your Home screen.
Frequently asked questions
What does an HTTP status code lookup show?
It shows every assigned HTTP status code with its official name, a short plain-language meaning and the specification that defines it, such as RFC 9110.
What is the difference between 401 and 403?
401 means the request has no valid credentials, so logging in may help. 403 means the server understood the request and still refuses it, so different credentials may be needed or access is simply not allowed.
When should I use 301 and when 308?
301 and 308 both mean a permanent move. 308 keeps the request method and body unchanged on the repeated request, which matters for POST requests and API calls. For ordinary page moves 301 is the common choice.
Is 418 I am a teapot a real status code?
The number is reserved and listed as unused in the HTTP standard. It comes from a joke specification published on April Fools Day and should not be used for real responses.
Is anything I type sent to a server?
No. The list is part of the page and the search runs in your browser.
Sources
Was this tool helpful?
What went wrong?
We only receive the reason you pick, never what you typed into the tool.
Thanks for your feedback.