Skip to content
Aback Launch
Guides11 min read

Website Down Checker: How to Tell if a Site Is Down for Everyone or Just You

How to use a website down checker to tell if a site is down for everyone or just you, what each error means (DNS, SSL, 5xx, CDN, expired domain), the order to troubleshoot in, and what downtime does to SEO.

Devvrat Hans

Founder

November 19, 2026
Website Down Checker: How to Tell if a Site Is Down for Everyone or Just You

To find out if a website is down for everyone or just you, load it from somewhere other than your own network. A website down checker does exactly that: it requests the site from its own servers and tells you whether it answered, how fast, and with what status. If the site loads there but not for you, the problem is on your side. If it fails there too, the site itself is down. The free website down checker runs this check from Cloudflare's network and reports the status code, response time, DNS and HTTPS in one go.

That first answer tells you whose problem it is. The rest of this guide tells you what to do next: the local fixes when it is just you, the causes behind each error when it is down for everyone, a troubleshooting order for your own site, what an outage does to your search rankings, and how to handle a site that falls over on launch day.

Is it down for everyone or just me?

Run these four checks in order. Together they take about a minute.

  1. Run a site down check from outside your network. Enter the domain or full URL in the site down checker. You get a verdict (up, slow, erroring or unreachable) and the reason.
  2. Try a different network. Turn off wifi on your phone and open the site on mobile data. A different network means a different DNS resolver and a different route to the server.
  3. Try a private window or another browser. This rules out extensions, cached files and stale cookies.
  4. Open a site you know works. If nothing loads, your connection is the problem, not the site.

How to read the website status check

ResultWhat it meansNext step
Up, with a 2xx statusThe site works from outside your networkThe problem is local; see the next section
Up, but slowIt answered, but took more than about 2 secondsServer overloaded or a slow backend; check hosting
403 ForbiddenThe server is up but refused an automated checkMany sites block bots; the site is probably fine
Other 4xxThe server answered but refused the requestCheck the exact URL; a 404 means the page, not the site, is missing
5xxThe server, or something in front of it, failedThe site is down for everyone; see causes below
UnreachableNo answer at all: DNS failed or the connection didCheck DNS and the domain registration

A website down checker is a one-off check. It tells you the state of the site now. To be told the moment your own site goes down, you need an uptime monitor that checks every minute or so and alerts you.

If the site is down just for you

When the checker says the site is up but your browser cannot load it, the cause is somewhere between you and the server. Work through these from quickest to slowest.

  • Stale DNS cache. Your computer may remember an old address for the site, especially if it recently moved hosts. Flush it: on Windows run ipconfig /flushdns; on macOS run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Then restart the browser.
  • Your DNS resolver. Your internet provider's resolver may be failing or filtering. Switching your device to a public resolver such as 1.1.1.1 often fixes it.
  • VPN or proxy. Turn it off and try again. Some sites block VPN address ranges, and some VPNs block sites.
  • Browser extensions. Ad blockers and privacy extensions sometimes break sites. The private window test above rules them out.
  • Firewall or office network. Workplace and school networks block categories of sites. Mobile data bypasses that.
  • Your IP address is blocked. A site's firewall may block an address after too many requests, which happens to developers testing their own site. Another network will work while yours does not.
  • The hosts file. If you once pointed a domain at a test server in your hosts file and forgot, your machine still goes there.

If the site is down for everyone: causes by symptom

When the down checker cannot load the site either, the error tells you where to look. Browsers name the problem, though not always in plain words.

What you seeLikely causeCheck with
DNS_PROBE_FINISHED_NXDOMAIN, "server IP address could not be found"DNS records missing or wrong, or the domain expiredDNS lookup, WHOIS lookup
NET::ERR_CERT_DATE_INVALIDThe SSL certificate expiredSSL checker
NET::ERR_CERT_COMMON_NAME_INVALIDThe certificate does not cover this name (often www vs bare domain)SSL checker
ERR_CONNECTION_REFUSED or ERR_CONNECTION_TIMED_OUTThe server is off, or a firewall blocks the portHosting dashboard
500 Internal Server ErrorThe application crashed on this requestApplication logs
502 Bad GatewayA proxy or CDN got a bad answer from the server behind itServer process and logs
503 Service UnavailableOverloaded, or in maintenance modeHosting load and limits
504 Gateway TimeoutThe server behind the proxy took too longSlow database or backend
Cloudflare 521 to 526Cloudflare is up, but your origin server is not answering it properlyOrigin server and its certificate
ERR_TOO_MANY_REDIRECTSA redirect loop, often between http and httpsRedirect checker
A parking or registrar pageThe domain registration expiredWHOIS lookup

DNS problems

DNS turns your domain into the address of your server. If the A, AAAA or CNAME record is missing, points at an old host, or the domain's name servers changed, nobody can reach the site even though the server is fine. A DNS lookup shows every common record (A, AAAA, CNAME, MX, TXT, NS, CAA and SOA) with its TTL. Compare them with what your host asked for. After a fix, resolvers can keep the old answer for up to the TTL, so a record with a one-hour TTL can take an hour to be seen everywhere.

SSL certificate problems

An expired or mismatched certificate does not stop the server, but browsers show a full-page warning that most visitors will not click past, so to them the site is down. Most certificates now last 90 days or less and renew automatically. When renewal fails silently, the site breaks on the expiry date. The SSL checker shows the current certificate's issuer, expiry date, days left and the names it covers, and whether http redirects to https. An expiry under two weeks away usually means automatic renewal is failing.

Server errors (5xx)

A 5xx status means the request reached your stack and something failed. A 500 is usually your code: a bad deploy, a missing environment variable, a database that refuses connections. A 502 or 504 means a proxy in front of your app (a load balancer, a CDN, a platform's router) could not get a good answer in time. A 503 usually means the server is overloaded or deliberately in maintenance. The fastest fix for a 500 right after a deploy is almost always to roll the deploy back, then investigate.

CDN and proxy errors

If your site sits behind a CDN such as Cloudflare, the error page often comes from the CDN, not from you. Cloudflare's codes are specific: 521 means your web server refused the connection, 522 means the connection timed out, 523 means the origin is unreachable, 524 means the origin connected but took too long to answer, 525 means the SSL handshake with your origin failed, and 526 means the origin's certificate is invalid. In every case the CDN is working and your origin server is the problem.

An expired domain

The most embarrassing outage, and a common one for side projects: the card on file expired and so did the domain. The site shows a registrar's parking page, or nothing. A WHOIS lookup shows the expiry date, the registrar and the status codes. A status such as clientHold or serverHold means the domain has been taken out of DNS, often after expiry or a billing problem. Most registrars give a grace period to renew; do it at once, then turn on auto-renew.

A troubleshooting order for your own site

When it is your site, you want the cause fast. This order goes from the outside in, and each step uses a free tool.

  1. Confirm the outage with the website down checker. Note the status code and whether DNS resolved.
  2. Check DNS with the DNS lookup. Are the A or CNAME records what your host expects? Did the NS records change?
  3. Check the domain with the WHOIS lookup. Is it expired, or on hold?
  4. Check HTTPS with the SSL checker. Is the certificate valid, unexpired and covering both the bare domain and www?
  5. Check the response with the HTTP header checker. It shows the status and every response header. Headers such as server or a CDN's own headers tell you which layer answered, and an X-Robots-Tag: noindex there is worth catching while you are looking.
  6. Check redirects with the redirect checker if the browser reports too many redirects.
  7. Check your host. Its status page, then your logs and your last deploy. If something changed in the last hour, undo it first.

What website downtime does to SEO

Short outages rarely hurt rankings. Googlebot retries pages that fail, and a site that is down for a few minutes or a few hours usually recovers without anyone noticing in search. Longer outages are different.

  • Crawling slows down. When Google gets 5xx or 429 responses, it crawls the site more slowly to avoid adding load.
  • Pages can drop out of the index. If pages keep returning server errors for an extended time (think days, not hours), Google may remove them from its index. They can return once the site works, but indexing takes time to recover.
  • A broken robots.txt can pause everything. If /robots.txt itself returns a server error, Google may stop crawling the whole site until it can fetch the file again.
  • The wrong status code makes it worse. An error page that returns 200 OK tells Google your pages now contain "Something went wrong", and a 404 tells it the pages are gone. For planned or temporary downtime, return 503, ideally with a Retry-After header.
HTTP/1.1 503 Service Unavailable
Retry-After: 3600
Content-Type: text/html; charset=utf-8

Even a 503 is meant for short periods. If the site is down for more than a day or two, get a static version of the key pages back up, even a simple one. Once you are back, check the Page indexing and Crawl stats reports in Search Console, and follow our guide to getting a website indexed by Google for any important pages that dropped.

What to do when your site goes down on launch day

Launch day is when your site gets the most visitors it has ever had, from people who have never seen it, and that is exactly when weak hosting breaks. Plan for it.

The week before

  • Check the certificate and the domain. Make sure neither expires in the next month.
  • Lower your DNS TTL a day ahead if you might need to switch hosts quickly.
  • Make the landing page static and served from a CDN. A page that needs a database for every visit is the first thing to fall over.
  • Test speed with the page speed checker: server response time and page weight both matter more under load.
  • Set up an uptime monitor that alerts your phone, and prepare a simple fallback page with a sign-up form.

During the outage

  1. Confirm it from outside with the down checker, so you know it is not your own network.
  2. Post an honest comment on your launch thread: what broke, that you are on it, and where people can leave their email meanwhile.
  3. Put the fallback page up, returning 503, while you fix the app.
  4. Fix the cause or roll back, then confirm with another check.
  5. Update the thread when it is back. People are forgiving of outages and unforgiving of silence.

A launch that runs longer than one day softens the blow. On a weekly launch, an hour of downtime is a small part of the window, and people who could not get in can come back. Our startup launch checklist for first-time founders covers the rest of the preparation.

FAQ

How do I check if a website is down for everyone or just me?

Use a website down checker, which loads the site from its own servers instead of your network. If it loads there but not for you, the problem is local: your DNS cache, VPN, browser or network. If it fails there too, the site is down for everyone.

Why does a site work on my phone but not my computer?

Your phone on mobile data uses a different network and DNS resolver. The usual causes on the computer are a stale DNS cache, a VPN or proxy, a browser extension, a firewall, or your IP address being blocked by the site. Flushing DNS and trying a private window fixes most cases.

What do 502, 503 and 504 errors mean?

A 502 Bad Gateway means a proxy or CDN got an invalid answer from the server behind it. A 503 Service Unavailable means the server is overloaded or in maintenance. A 504 Gateway Timeout means the server behind the proxy took too long to answer. All three are server-side problems.

How long can a website be down before it hurts SEO?

Outages of minutes or a few hours rarely affect rankings. If pages return server errors for several days, Google slows crawling and may drop them from its index. For planned downtime, return a 503 status with a Retry-After header and keep it short.

Can a website down checker monitor my site?

No. A down checker makes a one-off check and tells you the state of the site at that moment. To be alerted when your site goes down, use an uptime monitor that checks it every minute or few minutes and sends you a message.

What does it mean if a site returns 403 to a down checker?

A 403 Forbidden means the server is up and answered, but refused the request. Many sites block automated checks, so a 403 from a down checker usually means the site is working for normal visitors.

Written by

Devvrat Hans

Founder

Share
Newsletter
Get the Monday launch email
The week's new launches and winners, in one short email.

By subscribing, you agree to get our newsletter by email. Unsubscribe any time in one click. See our Privacy policy and Terms.

Launch your startup on Aback Launch

Get a launch page that search engines and AI assistants can read, a place in the weekly launch list, and a review by a real person. Free to join.