HTTP status codes
Saw an error like 404, 500 or 502 in your browser? Find out what it means, whether the problem is on your side or the website's, and how to fix it.
1xx Informational3 codes2xx Success5 codes3xx Redirection7 codes4xx Client errors27 codes5xx Server errors9 codesCloudflare errors (52x)7 codes
1xx Informational
The request was received and is still being processed.
HTTP 100 ContinueThe server received the request headers and the client should continue sending the request body.HTTP 101 Switching ProtocolsThe server agrees to switch to the protocol the client asked for (for example, WebSocket).HTTP 103 Early HintsThe server sends preliminary headers, such as preload links, before the final response so the browser can start loading resources early.
2xx Success
The request was received and handled successfully.
HTTP 200 OKThe request succeeded.HTTP 201 CreatedThe request succeeded and a new resource was created.HTTP 202 AcceptedThe request was accepted for processing, but processing has not finished yet.HTTP 204 No ContentThe request succeeded, but there is no content to send back.HTTP 206 Partial ContentThe server is sending only part of the file, as requested (used for resumable downloads and video streaming).
3xx Redirection
Further action is needed, usually following a redirect to another URL.
HTTP 300 Multiple ChoicesThe resource has more than one version and the client can choose one.HTTP 301 Moved PermanentlyThe page has moved permanently to a new URL; browsers and search engines should use the new address.HTTP 302 FoundThe page is temporarily available at a different URL.HTTP 303 See OtherThe client should fetch the result from another URL (common after submitting a form).HTTP 304 Not ModifiedThe copy saved in your browser cache is still up to date, so the server does not send the content again.HTTP 307 Temporary RedirectThe page is temporarily at another URL and the request must be repeated there with the same method.HTTP 308 Permanent RedirectThe page has moved permanently and the request must be repeated at the new URL with the same method.
4xx Client errors
The problem is in the request: wrong address, missing permission or invalid data.
HTTP 400 Bad RequestThe server cannot process the request because it is malformed or invalid.HTTP 401 UnauthorizedYou need to log in: authentication is required and was missing or invalid.HTTP 403 ForbiddenThe server understood the request but refuses to give access.HTTP 404 Not FoundThe server cannot find the requested page or file.HTTP 405 Method Not AllowedThe request method (for example POST) is not allowed for this URL.HTTP 406 Not AcceptableThe server cannot return the content in a format the client said it accepts.HTTP 407 Proxy Authentication RequiredYou must first sign in to the proxy server between you and the website.HTTP 408 Request TimeoutThe server waited too long for the client to finish sending the request.HTTP 409 ConflictThe request conflicts with the current state of the resource.HTTP 410 GoneThe page was removed permanently and will not come back.HTTP 411 Length RequiredThe server requires the request to state its length (Content-Length header).HTTP 412 Precondition FailedA condition in the request headers was not met by the current version of the resource.HTTP 413 Content Too LargeThe uploaded file or data is larger than the server allows.HTTP 414 URI Too LongThe URL is longer than the server is willing to process.HTTP 415 Unsupported Media TypeThe server does not accept the format of the data that was sent.HTTP 416 Range Not SatisfiableThe requested part of the file lies outside the file's size.HTTP 417 Expectation FailedThe server cannot meet the requirement in the request's Expect header.HTTP 418 I'm a teapot (Unused)An April Fools' joke from RFC 2324 ("I'm a teapot"). The code is reserved and not used in real HTTP.HTTP 421 Misdirected RequestThe request reached a server that cannot answer for this website address.HTTP 422 Unprocessable ContentThe request is well-formed, but the data in it is invalid (for example, it failed validation).HTTP 423 LockedThe resource is locked and cannot be changed right now.HTTP 425 Too EarlyThe server refuses to process a request that could be replayed (sent too early during the connection).HTTP 426 Upgrade RequiredThe client must switch to a different or newer protocol to continue.HTTP 428 Precondition RequiredThe server requires the request to be conditional, to prevent overwriting someone else's changes.HTTP 429 Too Many RequestsToo many requests were sent in a short time (rate limiting).HTTP 431 Request Header Fields Too LargeThe request headers, often the cookies, are too large.HTTP 451 Unavailable For Legal ReasonsAccess is blocked for legal reasons, such as a court order or government demand.
5xx Server errors
The server failed to handle a valid request; the problem is on the website's side.
HTTP 500 Internal Server ErrorThe server hit an unexpected error and could not complete the request.HTTP 501 Not ImplementedThe server does not support the function needed to complete the request.HTTP 502 Bad GatewayA gateway or proxy server received an invalid response from the server behind it.HTTP 503 Service UnavailableThe server is temporarily unable to handle the request because it is overloaded or under maintenance.HTTP 504 Gateway TimeoutA gateway or proxy server did not get a response in time from the server behind it.HTTP 505 HTTP Version Not SupportedThe server does not support the HTTP version used in the request.HTTP 507 Insufficient StorageThe server does not have enough storage space to complete the request.HTTP 508 Loop DetectedThe server detected an infinite loop while processing the request.HTTP 511 Network Authentication RequiredYou must sign in to the network (for example hotel, airport or public Wi-Fi) before you can use the internet.
Cloudflare errors (52x)
Unofficial codes returned by Cloudflare when it cannot get a valid response from the website's own (origin) server.
HTTP 520 Web Server Returned an Unknown ErrorThe website's server returned an empty, unknown or unexpected response to Cloudflare.HTTP 521 Web Server Is DownThe website's server refused the connection from Cloudflare (the web server is down or blocking Cloudflare).HTTP 522 Connection Timed OutCloudflare timed out while trying to connect to the website's server.HTTP 523 Origin Is UnreachableCloudflare cannot reach the website's server (the origin is unreachable).HTTP 524 A Timeout OccurredCloudflare connected to the website's server, but it did not respond before the timeout (125 seconds by default).HTTP 525 SSL Handshake FailedThe SSL/TLS handshake between Cloudflare and the website's server failed.HTTP 526 Invalid SSL CertificateCloudflare cannot validate the SSL certificate on the website's server.