HTTP status codes
What each code means when a website shows it, whether the site is actually down, and what you can do about it. Type a number or a word to find one.
Showing 56 of 56 codes.
1xx informational
100Continue
The server has the request headers and is ready for the body.
Part of an upload handshake. Browsers handle it themselves and you never see it.
101Switching Protocols
The server agrees to change protocol, usually to WebSocket.
Normal for live chats, games and dashboards that keep a connection open.
103Early Hints
A preview of headers sent before the real answer, so the browser can start loading styles and scripts early.
A speed optimisation. The real status code follows.
2xx success
200OK
The request worked and the answer is in the body.
The normal answer for a page that loads. A site that shows an error message with a 200 is still broken for you, even though the server says OK.
We count it as up: the server answered.
201Created
The request worked and created something new, such as an account or an order.
Seen from APIs and forms, not when browsing pages.
We count it as up: the server answered.
202Accepted
The request was accepted but will be handled later.
Common for exports and other slow jobs: the result arrives afterwards, often by email.
We count it as up: the server answered.
204No Content
The request worked and there is nothing to send back.
Normal for saving settings or sending analytics. Not something a page should answer with.
We count it as up: the server answered.
206Partial Content
Only part of a file was sent, as asked for.
Normal when streaming video or resuming a download.
We count it as up: the server answered.
3xx redirects
301Moved Permanently
The page has a new address for good; the Location header says where.
Browsers follow it and may remember it; search engines move the old address's standing to the new one. The right choice for HTTPS and domain moves.
We count it as up: the server answered.
302Found
The page is temporarily at another address.
Browsers follow it every time. Fine for logins and short-term moves; for a permanent move, use 301.
We count it as up: the server answered.
303See Other
Go and fetch another address with GET, usually after a form was sent.
Stops a form being sent twice when you press reload.
We count it as up: the server answered.
304Not Modified
The copy the browser already has is still current.
A good sign: the browser reuses its cached copy and saves a download.
We count it as up: the server answered.
307Temporary Redirect
Like 302, but the browser must repeat the request exactly, form data included.
Also used by browsers themselves when they upgrade a site to HTTPS (HSTS).
We count it as up: the server answered.
308Permanent Redirect
Like 301, but the request must be repeated exactly.
A permanent move that also keeps uploads and API calls working.
We count it as up: the server answered.
4xx client errors
400Bad Request
The server couldn't understand the request.
Often a corrupted or oversized cookie. Clearing the site's cookies, or trying a private window, usually fixes it.
We count it as up: the server answered.
401Unauthorized
You need to log in first, or your login is no longer valid.
Sign in again. If it keeps happening right after signing in, the site's login service may be having problems.
We count it as up: the server answered.
402Payment Required
Reserved for payments; some services use it when a subscription or quota has run out.
Check the account's billing or plan.
We count it as up: the server answered.
403Forbidden
The server understood the request but refuses to answer it.
You may lack permission, or a firewall or bot protection is blocking your network, VPN or country. The site itself is usually up.
We count it as up: the server answered.
404Not Found
There is nothing at this address.
Check the address for typos, or start from the home page. The site is up; only this page is missing or has moved without a redirect.
We count it as up: the server answered.
405Method Not Allowed
The address exists but doesn't accept this kind of request.
Usually a bug in a form or an app, not something you can fix as a visitor.
We count it as up: the server answered.
406Not Acceptable
The server has nothing in a format the request said it would accept.
Rare in browsers. Some security filters also answer automated requests with it.
We count it as up: the server answered.
408Request Timeout
The server gave up waiting for the request to finish arriving.
Usually a slow or unstable connection on your side. Try again.
We count it as up: the server answered.
409Conflict
The request clashes with the current state, such as an edit made at the same time by someone else.
Reload to get the latest version, then try again.
We count it as up: the server answered.
410Gone
The page was removed on purpose and isn't coming back.
Unlike 404, this is deliberate. Search engines drop such pages faster.
We count it as up: the server answered.
411Length Required
The server needs to know the size of the upload first.
A problem in the app or tool sending the request.
We count it as up: the server answered.
413Content Too Large
The upload is bigger than the server allows.
Try a smaller file, or compress it first.
We count it as up: the server answered.
414URI Too Long
The address itself is too long for the server.
Usually a link with far too many tracking parameters, or a redirect loop that kept adding to the address.
We count it as up: the server answered.
415Unsupported Media Type
The server doesn't accept the type of file or data sent.
Check the file format the site asks for.
We count it as up: the server answered.
418I'm a teapot
An April Fools' code from 1998: the server refuses to brew coffee because it is a teapot.
Some sites use it as a joke answer to bots.
We count it as up: the server answered.
421Misdirected Request
The request reached a server that doesn't serve this site.
Usually a hosting or CDN setup issue after a DNS or certificate change.
We count it as up: the server answered.
422Unprocessable Content
The request was understood, but the data in it isn't valid.
Check what you entered in the form: the error message usually says which field.
We count it as up: the server answered.
425Too Early
The server won't risk handling a request that might be replayed.
Browsers retry this on their own.
We count it as up: the server answered.
426Upgrade Required
The server only answers over a newer protocol.
Update the browser or app.
We count it as up: the server answered.
428Precondition Required
The server wants proof you are editing the latest version.
An API safety check against overwriting someone else's changes.
We count it as up: the server answered.
429Too Many Requests
You (or your network) sent too many requests in a short time.
Wait a minute and try again. Shared networks, VPNs and busy offices hit this more often. The site is up.
We count it as up: the server answered.
431Request Header Fields Too Large
The request headers, usually the cookies, are too big.
Clear the site's cookies.
We count it as up: the server answered.
451Unavailable For Legal Reasons
The page is blocked for legal reasons, such as a court order or sanctions.
Usually depends on your country. The number is a nod to the novel Fahrenheit 451.
We count it as up: the server answered.
5xx server errors
500Internal Server Error
Something went wrong on the server while handling the request.
A fault in the site, not your device. Try again in a few minutes; if it persists, the site's team has to fix it.
We count it as down.
501Not Implemented
The server doesn't support what the request asks for.
Rare when browsing; usually an app or API mismatch.
We count it as down.
502Bad Gateway
A proxy or CDN in front of the site got no valid answer from the server behind it.
The site's own server is down, restarting or overloaded. Nothing to fix on your side; try again shortly.
We count it as down.
503Service Unavailable
The server can't handle the request right now.
Planned maintenance or overload, usually short. Some bot protection also answers with 503 while it checks your browser.
We count it as problems: it can mean maintenance, overload or bot protection.
504Gateway Timeout
A proxy or CDN waited too long for the server behind it.
The site is up in front but its server or database is too slow. Often a sign of heavy load during an outage.
We count it as down.
505HTTP Version Not Supported
The server doesn't speak the HTTP version used.
Rare; a server setup problem.
We count it as down.
507Insufficient Storage
The server has run out of space to finish the request.
A problem on the site's side, common with self-hosted file storage.
We count it as down.
508Loop Detected
The server found an endless loop while handling the request.
Some hosts also use it when a site goes over its resource limits.
We count it as down.
511Network Authentication Required
The network you are on wants you to sign in first.
Typical of hotel, airport and café Wi-Fi: open any page to get the sign-in screen.
We count it as down.
Codes from nginx and Cloudflare
444No Responsenginx
The server closed the connection without answering.
Used to shut out unwanted traffic; you see a connection error, not a page.
No answer arrives, so we count it as down.
499Client Closed Requestnginx
The visitor gave up before the server answered.
Only appears in server logs, often during slowdowns.
520Web Server Returned an Unknown ErrorCloudflare
The site's server sent Cloudflare an empty or invalid answer.
A problem on the site's server, not at Cloudflare.
We count it as down.
521Web Server Is DownCloudflare
The site's server refused Cloudflare's connection.
The site's server is off or its firewall blocks Cloudflare. The site is down for everyone.
We count it as down.
522Connection Timed OutCloudflare
Cloudflare couldn't connect to the site's server in time.
The server is overloaded, offline or unreachable. Down for everyone until it recovers.
We count it as down.
523Origin Is UnreachableCloudflare
Cloudflare can't find a route to the site's server.
Often a wrong DNS record for the server, or a network outage at its host.
We count it as down.
524A Timeout OccurredCloudflare
Cloudflare connected but the server took more than 100 seconds to answer.
A slow page or a stuck server on the site's side.
We count it as down.
525SSL Handshake FailedCloudflare
Cloudflare and the site's server couldn't agree on a secure connection.
A certificate or TLS setup problem on the site's server.
We count it as down.
526Invalid SSL CertificateCloudflare
The site's server has a certificate Cloudflare won't accept.
Usually an expired or self-signed certificate on the server behind Cloudflare.
We count it as down.
530Origin DNS ErrorCloudflare
Cloudflare couldn't resolve or reach the site's server; shown with a 1xxx error number.
A DNS or setup problem on the site's side.
We count it as down.
Seeing an error on a site?
Or follow its redirects and see each status code with the redirect checker.
Status code questions
- What is an HTTP status code?
- A three-digit number a web server sends with every answer, before the page itself. The first digit gives the kind of answer: 2xx worked, 3xx go somewhere else, 4xx something is wrong with the request, 5xx something went wrong on the server.
- Which status codes mean a website is down?
- The 5xx codes, above all 500, 502, 504 and Cloudflare's 52x range: the server, or the one behind its CDN, failed. A 503 often means planned maintenance or overload. The 4xx codes, such as 403, 404 and 429, mean the server is up and answering but won't or can't give you this page.
- Is a 404 error my fault?
- Rarely. It means nothing is at that address: a mistyped link, a page that was moved without a redirect, or one that was deleted. Check the address, or start from the site's home page and search from there.
- How do I see the status code a page returns?
- Use the redirect checker on this site: it shows the status code of each step, and the response headers. In a browser, open the developer tools (F12), go to the Network tab and reload the page; the Status column shows each code.
- Why does a site show an error page with code 200?
- Some sites answer every request with 200 OK and show their error inside the page, especially apps that build pages with JavaScript. The server is working, but the part that loads the content isn't. Status codes only tell the server's side of the story.