1xx — Informational
100 ContinueThe server received the request headers; the client should send the body.
101 Switching ProtocolsThe server is switching to the protocol requested in Upgrade (for example WebSocket).
103 Early HintsPreliminary headers (such as Link preload) sent before the final response.
2xx — Success
200 OKThe request succeeded.
201 CreatedThe request succeeded and a new resource was created.
202 AcceptedThe request was accepted for processing but is not finished.
204 No ContentSuccess with no response body.
206 Partial ContentOnly part of the resource is returned (Range request).
3xx — Redirection
301 Moved PermanentlyThe resource has a new permanent URL; search engines transfer ranking to it.
302 FoundTemporary redirect; the original URL should keep being used.
303 See OtherRedirect to another URL using GET, typically after a POST.
304 Not ModifiedThe cached copy is still valid; no body is sent.
307 Temporary RedirectTemporary redirect that keeps the original HTTP method.
308 Permanent RedirectPermanent redirect that keeps the original HTTP method.
4xx — Client error
400 Bad RequestThe server cannot process the request because it is malformed.
401 UnauthorizedAuthentication is required or has failed.
403 ForbiddenThe server understood the request but refuses to authorize it.
404 Not FoundThe resource does not exist at this URL.
405 Method Not AllowedThe HTTP method is not supported for this resource.
406 Not AcceptableThe server cannot produce a response matching the Accept headers.
408 Request TimeoutThe server timed out waiting for the request.
409 ConflictThe request conflicts with the current state of the resource.
410 GoneThe resource was permanently removed and will not come back.
411 Length RequiredThe request needs a Content-Length header.
412 Precondition FailedA precondition in the request headers was not met.
413 Content Too LargeThe request body is larger than the server allows.
414 URI Too LongThe request URL is longer than the server accepts.
415 Unsupported Media TypeThe request's content type is not supported.
416 Range Not SatisfiableThe requested byte range cannot be served.
418 I'm a teapotJoke status from RFC 2324; some servers use it to reject bots.
421 Misdirected RequestThe request was sent to a server that cannot produce a response.
422 Unprocessable ContentThe request is well-formed but semantically invalid.
423 LockedThe resource is locked.
425 Too EarlyThe server will not process a request that might be replayed.
426 Upgrade RequiredThe client must switch to a different protocol.
428 Precondition RequiredThe server requires the request to be conditional.
429 Too Many RequestsRate limit exceeded; check the Retry-After header.
431 Request Header Fields Too LargeThe request headers are too large.
451 Unavailable For Legal ReasonsAccess is denied for legal reasons.
5xx — Server error
500 Internal Server ErrorA generic server-side failure.
501 Not ImplementedThe server does not support the requested functionality.
502 Bad GatewayA gateway or proxy received an invalid response from upstream.
503 Service UnavailableThe server is overloaded or down for maintenance; may include Retry-After.
504 Gateway TimeoutA gateway or proxy timed out waiting for the upstream server.
505 HTTP Version Not SupportedThe HTTP version is not supported.
507 Insufficient StorageThe server cannot store the representation needed to finish the request.
511 Network Authentication RequiredThe client must authenticate to gain network access (captive portal).

Runs entirely in your browser — nothing you type is sent to our servers.

About this tool

A searchable reference of HTTP status codes from 100 to 511 with a plain-language explanation of each one, including when a redirect or an error is the right response.

Related tools