DD DevDome Track. Protect. Grow.

Is It Down?

Find out if a website is down for everyone or just for you. One request from our server, with the status code, the response time and the exact error when it fails.

How to use it

  1. Enter the site address. The homepage is checked unless you paste a specific page.
  2. Press Check now. Our server sends one request and waits up to 30 seconds for an answer.
  3. Read the verdict: up with the status and time, or down with the reason (DNS, refused, timeout, server error).

Down for everyone, or just for you

When a site will not load, the question is where the fault is. A request from a second network answers it in one step. If our server gets a normal page back, the site is up and the problem is on your side: a DNS cache that still points at an old address, a router that needs a restart, an office firewall, or a block on your IP. If our server fails too, the site is down, and the error says how: DNS failure means the domain does not resolve, connection refused or timeout means the server is unreachable, a 5xx status means the server is up but the site on it has failed.

The check requests the page the way a plain visitor would, without cookies and without a browser session, and reports the first status and the final one if there was a redirect.

Website down FAQ

How does this check whether a site is down?

Our server, which sits on a different network from yours, requests the homepage once and reports what came back: a status code and how long it took, or the error that stopped it (DNS failure, connection refused, timeout). If our server gets a normal answer and you do not, the problem is between you and the site: your DNS, your network, a firewall, or a block on your address.

The site shows "up" here but it does not load for me. What now?

Try the address in a private window (a stale cookie or cached redirect is a common cause), then try a different network such as your phone on mobile data. If it loads there, your connection or DNS resolver is the problem; switching your DNS to 1.1.1.1 or 8.8.8.8 often fixes it. If it fails everywhere for you but works here, the site may be blocking your country or your address.

What do 5xx errors mean when the site is "up"?

The server answered, so the network path is fine, but the application behind it failed: 500 is a crash or misconfiguration, 502 and 504 mean a proxy could not reach the real server, 503 means it is overloaded or in maintenance. Those count as down for visitors even though the server is reachable.

Is one check enough to say a site is down?

For a quick answer, yes. A single check cannot tell you whether the outage started a minute ago or has been going on for an hour, and it cannot wake you when your own site goes down at 3 am. That is what an uptime monitor is for.

Can I check a site that blocks bots?

Some sites answer 403 or show a challenge page to any request that does not come from a browser. The checker reports that honestly as a 403 or a challenge; it does not mean the site is down for people.