HTTP Status Code Reference

Look up what any HTTP status code means. Everything runs in your browser, so your input isn’t uploaded.

62 of 62 codes

100Continue InformationalThe request headers were accepted. The client should go ahead and send the body.
101Switching Protocols InformationalThe server agrees to switch to the protocol the client asked for, such as WebSocket.
102Processing InformationalThe server is still working on the request and has no final response yet (WebDAV).
103Early Hints InformationalSent before the final response so the browser can start loading resources early.
200OK SuccessThe request succeeded. What the response contains depends on the request method.
201Created SuccessThe request succeeded and a new resource was created, usually after a POST or PUT.
202Accepted SuccessThe request was received but processing is not finished. The result may come later.
203Non-Authoritative Information SuccessThe response was modified by a proxy and may differ from the origin server’s.
204No Content SuccessThe request succeeded and there is intentionally no response body.
205Reset Content SuccessThe request succeeded. The client should reset the view that sent it, such as a form.
206Partial Content SuccessOnly the byte range that was requested is returned, used for resumable downloads and video.
207Multi-Status SuccessThe body contains separate status codes for several operations (WebDAV).
208Already Reported SuccessMembers of a WebDAV binding were already listed earlier in the response.
226IM Used SuccessThe response is the result of one or more instance manipulations applied to the resource.
300Multiple Choices RedirectionThere are several possible responses and the client may pick one.
301Moved Permanently RedirectionThe resource has a new permanent URL. Clients and search engines should use the new one.
302Found RedirectionThe resource is temporarily at another URL. Keep using the original URL in future.
303See Other RedirectionFetch the result from another URL using GET, often after a form submission.
304Not Modified RedirectionThe cached copy is still valid, so no body is sent.
305Use Proxy RedirectionDeprecated. The resource must be accessed through a proxy.
307Temporary Redirect RedirectionTemporarily use another URL and repeat the same method and body.
308Permanent Redirect RedirectionPermanently use another URL and repeat the same method and body.
400Bad Request Client errorThe server can’t process the request because it is malformed or invalid.
401Unauthorized Client errorAuthentication is required or has failed. The client has not proven who it is.
402Payment Required Client errorReserved for future use. Some services use it to signal a payment problem.
403Forbidden Client errorThe server understood the request but refuses it. Logging in again won’t help.
404Not Found Client errorNothing exists at this URL. The server won’t say whether it ever did.
405Method Not Allowed Client errorThe HTTP method isn’t supported for this URL, for example POST to a read-only page.
406Not Acceptable Client errorThe server can’t produce a response matching the client’s Accept headers.
407Proxy Authentication Required Client errorLike 401, but the client must first authenticate with the proxy.
408Request Timeout Client errorThe server gave up waiting for the client to finish sending the request.
409Conflict Client errorThe request conflicts with the current state of the resource, such as an edit collision.
410Gone Client errorThe resource was deliberately removed and won’t come back.
411Length Required Client errorThe server requires a Content-Length header on the request.
412Precondition Failed Client errorA condition in the request headers, such as If-Match, was not met.
413Content Too Large Client errorThe request body is bigger than the server allows (formerly Payload Too Large).
414URI Too Long Client errorThe URL is longer than the server is willing to handle.
415Unsupported Media Type Client errorThe server doesn’t support the format of the request body.
416Range Not Satisfiable Client errorThe requested byte range falls outside the size of the resource.
417Expectation Failed Client errorThe server can’t meet the requirement in the Expect header.
418I’m a teapot Client errorA joke code from an April Fools’ RFC. A teapot refuses to brew coffee.
421Misdirected Request Client errorThe request was sent to a server that can’t produce a response for that address.
422Unprocessable Content Client errorThe request is well-formed but its content failed validation. Common in APIs.
423Locked Client errorThe resource is locked (WebDAV).
424Failed Dependency Client errorThe request failed because an earlier request it depended on failed (WebDAV).
425Too Early Client errorThe server won’t process a request that might be replayed.
426Upgrade Required Client errorThe client must switch to a different protocol, such as TLS, to continue.
428Precondition Required Client errorThe server requires the request to be conditional, to prevent lost updates.
429Too Many Requests Client errorThe client sent too many requests in a given time (rate limiting).
431Request Header Fields Too Large Client errorThe request headers are too big, as a whole or individually.
451Unavailable For Legal Reasons Client errorAccess is denied for legal reasons, such as a court order.
500Internal Server Error Server errorA generic error: the server hit an unexpected problem it can’t describe more precisely.
501Not Implemented Server errorThe server doesn’t support the functionality needed for this request.
502Bad Gateway Server errorA gateway or proxy received an invalid response from the server behind it.
503Service Unavailable Server errorThe server is temporarily overloaded or down for maintenance.
504Gateway Timeout Server errorA gateway or proxy didn’t get a response from the upstream server in time.
505HTTP Version Not Supported Server errorThe server doesn’t support the HTTP version used in the request.
506Variant Also Negotiates Server errorA server configuration error in content negotiation.
507Insufficient Storage Server errorThe server has no room to store what the request needs (WebDAV).
508Loop Detected Server errorThe server found an infinite loop while processing the request (WebDAV).
510Not Extended Server errorThe request needs further extensions for the server to fulfil it.
511Network Authentication Required Server errorThe client must authenticate to gain network access, as on a captive Wi-Fi portal.

Loading tool…

How to use the HTTP Status Code Reference

Type a code, name or word such as 404, redirect or timeout in the search box.
Use the class buttons to show only 2xx, 3xx, 4xx or 5xx codes.
Read the short description under each code.

About this tool

Every HTTP response starts with a three-digit status code. The first digit tells you the kind of result: information, success, redirection, a problem with the request, or a problem on the server. This page lists the codes in common use with a short explanation of each.

Good to know

Descriptions are short summaries, not the full specification. See the HTTP standards (RFC 9110) for exact rules.
Some codes, such as 418, are jokes or are used only in specific protocols like WebDAV.
How a code is used in practice can vary between APIs, so check the documentation of the service you call.

Related tools

URL Encoder & Decoder – Percent-encode or decode text for use in URLs.
HTML Entity Encoder & Decoder – Escape special characters as HTML entities, or turn entities back into text.
Base64 Encoder & Decoder – Encode text to Base64 or decode it back, including emoji and non-English text.
Unix Timestamp Converter – Convert Unix seconds or milliseconds to dates, and dates back to timestamps.
JWT Decoder – Read a JWT’s header and payload. Decoding only: it does not verify signatures.

Browse all tools