Skip to content
helpyself

HTTP Status Codes

Local only — nothing is uploaded unless you save or share it.

Every HTTP status code, what it means and when to send it — with the RFC that defines it.

  1. Type the code, such as 404, or a word like "redirect" into the search box.
  2. Read what the code means, when to send it and which RFC defines it.
  3. Pick a class such as 4xx, or clear the box to see every code grouped by class.

4xx · Client error

404

Not Found

The server has nothing at this address, or will not say whether it does.

When to use it: The answer for a broken link or a mistyped URL. Also used instead of 403 to hide that a private resource exists. If it is gone for good, 410 says so.

Defined in RFC 9110 §15.5.5

Save this tool

Keep HTTP Status Codes handy

Bookmark it
Embed

Put HTTP Status Codes on your website

Paste this into your page. It shows the tool, free, with a link back to it.

About this tool

Every HTTP status code in the official IANA registry, from 100 Continue to 511 Network Authentication Required, each with a plain explanation of what it means, when a server should send it, and a link to the section of the RFC that defines it. Type a number, the first digit of a class ("4" or "4xx"), or a word such as "redirect" or "rate limit", and the list narrows as you type. The differences that matter are spelled out rather than left to the name. 401 Unauthorized means the request was not authenticated — log in and try again — while 403 Forbidden means the server understood the request and still says no. 301 and 302 let an old client turn a POST into a GET on the way to the new address; 308 and 307 are the same two redirects with the method guaranteed to survive. 422 Unprocessable Content is no longer a WebDAV extra: RFC 9110 made it part of HTTP itself in 2022, which is why it is the usual answer to a validation error. The names are kept exactly as the specification writes them, because that is what appears on the status line, in your logs and in every library. Where a code has been renamed — 413 used to be Payload Too Large, 422 Unprocessable Entity — the old name is shown too, and finds it. 418 I'm a teapot is here as well, marked for what it is: an April Fools' joke from RFC 2324 that RFC 9110 now reserves so nobody can give the number a real job. Unofficial codes such as nginx's 499 or Cloudflare's 520 to 526 are not in the registry and are not listed as if they were. It all runs in your browser and works offline once the page has loaded.

Frequently asked questions

What is the difference between 401 and 403?

401 Unauthorized means the request has no valid credentials: the server does not know who you are, and it must say how to authenticate in a WWW-Authenticate header. Logging in may fix it. 403 Forbidden means the server understood the request and refuses it anyway: repeating it with the same credentials will not help, only an account with the right permission would. Despite its name, 401 is about authentication and 403 about permission.

Should I use 301 or 308 for a permanent redirect?

For a web page either works, and 301 is the one every crawler and browser has handled for decades; search engines treat the two the same. The difference is the method. Under 301, an old client is allowed to turn a POST into a GET when it follows the redirect, while 308 promises the method and body stay exactly as they were. For an API endpoint that accepts POST or PUT, use 308. The temporary pair works the same way: 302 may change the method, 307 must not.

What does 304 Not Modified mean?

It answers a conditional request — one sent with If-None-Match or If-Modified-Since — and says the copy the client already has is still current, so no body is sent. It is how caching saves bandwidth, and it is not an error: seeing a lot of 304s in your logs means caching works.

Is 422 or 400 right for a validation error?

Use 400 when the request cannot be read at all — broken JSON, a missing required header. Use 422 Unprocessable Content when it is well-formed but its content cannot be acted on, such as an email field holding something that is not an email address. 422 began in WebDAV and was brought into HTTP itself by RFC 9110 in 2022, so it is no longer an extension.

What is the difference between 502, 503 and 504?

All three usually come from a proxy or load balancer rather than your application. 502 Bad Gateway means the server behind it sent an invalid response or none at all, often because it crashed. 503 Service Unavailable means the server is up but cannot take the request right now — overloaded or in maintenance — ideally with a Retry-After header. 504 Gateway Timeout means the server behind the proxy took too long to answer.

Is 418 I'm a teapot a real status code?

It started as a joke: RFC 2324, an April Fools' RFC from 1998, defined it for coffee pots that are asked to brew coffee but are teapots. It was never meant to be implemented, but so many frameworks added it that RFC 9110 now marks 418 as reserved, so the number cannot be given a real meaning. Using it in production is a joke your API's clients have to understand.

Why are 499, 509 and 520 missing?

They are not registered HTTP status codes. 499 is logged by nginx when the client closed the connection before the response, 509 Bandwidth Limit Exceeded comes from some web hosts, and 520 to 526 are Cloudflare's own errors for problems reaching the origin server. Each means something only for that product, so the list sticks to the official registry.

Help improve this tool

Found a bug, want a change, or need a tool we don't have?

/http-status-codes

↑↓ to move · Enter to open · Esc to close