HTTP status codes list

Every HTTP code, in plain English.

62 rows

Code	Name	What it means
	Continue	The server got the request headers and the client can send the body.
	Switching Protocols	The server agrees to switch protocols, for example to WebSocket.
	Processing	The server is still working on a long request (WebDAV). Rarely used now.
	Early Hints	Sent before the final response so the browser can start preloading files.
	OK	The request worked. The body holds the result.
	Created	A new resource was created, usually after a POST. The Location header points to it.
	Accepted	The request was accepted for processing but isn’t finished yet.
	Non-Authoritative Information	The response was changed by a proxy from what the origin server sent.
	No Content	The request worked and there is nothing to send back.
	Reset Content	The request worked; the client should reset the form or view that sent it.
	Partial Content	Only part of the file is sent, as asked for with a Range header (used for video and resumable downloads).
	Multi-Status	Several status codes for several operations in one response (WebDAV).
	Already Reported	Members already listed earlier in the same response aren’t repeated (WebDAV).
	IM Used	The response is the result of changes applied to the current version (delta encoding).
	Multiple Choices	There are several possible responses; the client should pick one.
	Moved Permanently	The page has a new address for good. Browsers and search engines update to the new URL.
	Found	The page is temporarily at another address. Keep using the original URL.
	See Other	Get the result from another URL with a GET request, often after a form is submitted.
	Not Modified	The cached copy is still current, so nothing is sent again.
	Use Proxy	Deprecated. Browsers ignore it for security reasons.
	Temporary Redirect	Temporarily at another URL; repeat the request there with the same method and body.
	Permanent Redirect	Moved for good; repeat the request at the new URL with the same method and body.
	Bad Request	The server can’t understand the request, for example because of broken syntax.
	Unauthorized	You need to log in or send valid credentials.
	Payment Required	Reserved for future use; some services use it when payment is needed.
	Forbidden	The server understood the request but won’t allow it. Logging in again with the same account won’t help.
	Not Found	Nothing exists at this URL, or the server won’t say whether it does.
	Method Not Allowed	The URL exists but doesn’t accept this method, such as POST.
	Not Acceptable	The server can’t give a response in any format the client said it accepts.
	Proxy Authentication Required	Like 401, but you need to log in to a proxy first.
	Request Timeout	The client took too long to send the request.
	Conflict	The request clashes with the current state, such as an edit conflict.
	Gone	The resource was removed on purpose and won’t come back.
	Length Required	The request needs a Content-Length header.
	Precondition Failed	A condition in the request headers, such as If-Match, wasn’t met.
	Content Too Large	The request body is bigger than the server allows (formerly Payload Too Large).
	URI Too Long	The URL is longer than the server will handle.
	Unsupported Media Type	The server doesn’t accept the format of the request body.
	Range Not Satisfiable	The requested part of the file is outside its size.
	Expectation Failed	The server can’t meet the Expect header in the request.
	I’m a teapot	An April Fools’ joke from 1998 (RFC 2324). Some servers use it for fun.
	Misdirected Request	The request went to a server that can’t answer for this address.
	Unprocessable Content	The request is well formed but the data in it doesn’t make sense, such as a failed validation.
	Locked	The resource is locked (WebDAV).
	Failed Dependency	The request failed because an earlier request it depended on failed (WebDAV).
	Too Early	The server won’t risk processing a request that might be replayed.
	Upgrade Required	The client must switch to another protocol, given in the Upgrade header.
	Precondition Required	The server needs a conditional request (such as If-Match) to avoid lost updates.
	Too Many Requests	Rate limited: the client sent too many requests. Retry-After may say when to try again.
	Request Header Fields Too Large	The headers, or one of them, are too big.
	Unavailable For Legal Reasons	Blocked for legal reasons, such as a court order.
	Internal Server Error	Something went wrong on the server and it has no more specific code.
	Not Implemented	The server doesn’t support the feature needed for this request.
	Bad Gateway	A gateway or proxy got an invalid response from the server behind it.
	Service Unavailable	The server is overloaded or down for maintenance. Usually temporary.
	Gateway Timeout	A gateway or proxy didn’t get a response in time from the server behind it.
	HTTP Version Not Supported	The server doesn’t support the HTTP version used.
	Variant Also Negotiates	The server is misconfigured: content negotiation loops back on itself.
	Insufficient Storage	The server can’t store what’s needed to finish the request (WebDAV).
	Loop Detected	The server found an infinite loop while processing the request (WebDAV).
	Not Extended	Further extensions to the request are needed.
	Network Authentication Required	You need to log in to the network, as with hotel or airport Wi-Fi.

Click a highlighted value to copy it.

Type in the box to filter, or press / to jump to it.

Runs in your browser. Nothing uploaded.

How to use the HTTP status code list

Type a code (404), part of a name (gateway) or a word from the meaning (cache) into the filter box.
Use Client error, Server error or one of the other class buttons to show a single group of codes.
Click a code to copy it.

The five classes

The first digit tells you what kind of answer the server gave. A client that meets a code it doesn’t know treats it like the x00 code of its class, so an unknown 4xx is handled like 400.

Class	Meaning
1xx Informational	An interim reply. The request is still going.
2xx Success	The request worked.
3xx Redirection	The client has to go somewhere else, or use its cached copy.
4xx Client error	Something is wrong with the request: the URL, the login or the data sent.
5xx Server error	The request looked fine, but the server failed to answer it.

The codes you’ll meet most

200 OK: the normal answer. A “page not found” message served with a 200 is called a soft 404, and search engines may index it as a real page. Missing pages should return a real 404.
301, 302, 307 and 308: 301 and 308 mean moved for good, 302 and 307 mean moved for now. The difference between the pairs is that 307 and 308 make the browser repeat the request exactly, while with 301 and 302 a POST may turn into a GET. For an ordinary page, 301 or 308 for a permanent move is all you need.
304 Not Modified: the browser asked whether its cached copy was still current and the server said yes. Nothing is wrong. This saves bandwidth.
400 Bad Request: the request itself is broken, often a malformed URL, an oversized cookie or invalid JSON in an API call. If a URL has unusual characters, check how they’re encoded with the URL encoder.
401 vs 403: log in to fix a 401. A 403 means the account, IP address or file permissions don’t allow access.
404 vs 410: both mean the page isn’t there. 410 says it was removed on purpose and won’t come back, which is a clearer signal when you delete content for good.
429 Too Many Requests: you hit a rate limit. Wait and retry, and respect the Retry-After header if there is one.
500 Internal Server Error: a crash or misconfiguration on the server. Check the error log.
502, 503 and 504: these usually come from a proxy, load balancer or CDN in front of your app. 502 means the app behind it sent back nonsense or crashed, 504 means it took too long, and 503 means the service is down or overloaded. For planned maintenance, send a 503 with Retry-After so crawlers come back later instead of treating pages as gone.

Renamed codes

RFC 9110, the current HTTP standard from 2022, renamed two codes. 413 was Payload Too Large and is now Content Too Large. 422 was Unprocessable Entity and is now Unprocessable Content. The table uses the new names, but older docs and libraries still show the old ones. The numbers and their meaning didn’t change.

Questions

What does a 404 error mean?

The server is working, but there is nothing at that URL. The page may have been moved or deleted, or the link has a typo. If you own the site and the page moved, redirect the old URL to the new one with a 301.

What does a 500 error mean?

Something broke on the server while it handled the request, and it has no more specific code to report. Reloading won’t usually help. If it’s your site, the server’s error log will say what failed.

What is the difference between 301 and 302?

301 means the page has moved for good, so browsers cache the redirect and search engines move rankings to the new URL. 302 means the move is temporary and the old URL stays the one that counts. Use 301 for a changed URL or a switch to HTTPS.

What is the difference between 401 and 403?

401 means the server doesn’t know who you are: you aren’t logged in or your credentials are wrong. 403 means it knows who you are, or doesn’t need to, and still won’t let you in. Logging in can fix a 401, but usually not a 403.

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

It began as an April Fools’ joke in RFC 2324 (1998), which described a protocol for controlling coffee pots. It was never part of real HTTP, but it was copied into so many servers and frameworks for fun that RFC 9110 now reserves 418 so it can’t be given another meaning.