Free tool

Website down checker

Paste a public address and see whether it answers from the ismysiteup server right now. You get the final HTTP status, how long the request took, and the TLS certificate on port 443.

Free 5 checks per hour. Sign up for 24/7 automated monitoring.

How the website down checker works in 60 seconds

What this website down checker does

The check is one HTTP GET from our server, with a 10 second timeout. A bare domain such as example.com is requested as https://example.com. We follow up to five redirects and report the final response. Up means that status was 200–399. Down means DNS failed, the connection was refused, the request timed out, TLS failed, or the final status was 400 or higher.

The check comes from one location: our own server. Other checkers test from several countries at once; this one does not, so it cannot tell you that a site is down in one region only. One result is one place at one moment. It does not prove the site is down for every visitor. If you and this checker disagree, try a second network before you open a ticket with the host.

How to read the result

Up with HTTP 200 means this URL responded successfully. Up with a 3xx code means it is still redirecting after we followed the chain. Down with HTTP 404 means this path is missing — the host can be fine. Down with 502 or 503 means the app or the proxy in front of it failed. Down with no status code means we never got an HTTP response; the error line says whether that was DNS, a refused connection, a timeout, or TLS.

Response time includes redirects. SSL shows the issuer and days left when port 443 presents a certificate. Domain, when a registration lookup returns, shows days until the name expires. A dash means no date came back, not that the domain is safe.

Common causes and what to try

Match the error to the layer that failed. A new certificate will not fix a process that is not listening, and a DNS change will not fix a typo in the path.

  • DNS failed: check the registrar, the DNS host, and whether a nameserver change is still propagating.
  • Connection refused: nothing is accepting traffic on that port, or a firewall is dropping it.
  • Timeout: the server did not answer within 10 seconds. Look at CPU, a stuck deploy, and slow upstreams.
  • HTTP 502 or 503: the app behind the proxy crashed or is restarting. Read the application log.
  • HTTP 404: confirm the path and that the deploy you expect is the one that is live.
  • SSL/TLS error: browsers warn visitors even when the process is up. Renew the certificate and check the hostname on it.

When a one-off check is not enough

This page answers “is it down right now?” It stops when you leave. The free plan monitors 5 URLs and checks each every 10 minutes. Pro checks every 5 minutes. Business checks every minute. Alerts go to WhatsApp, Telegram, Slack, or email after a failure is confirmed, so one blip does not page you, and you get a note when the URL recovers.

Questions

Does down mean the site is down for everyone?

No. This is one check from our server. If you can open the site and we cannot, something between our network and the host may be filtering datacenter traffic. If we can open it and you cannot, check your network or DNS first.

Why does a 404 count as down?

Because this URL did not return a successful page. The domain can still be up. Test the homepage, and check the path you pasted.

Do you keep a history of the check?

No. The public checker shows this result only and allows 5 checks per hour per IP address. An account is what turns the URL into a monitor with repeated checks.

Can I check localhost or a LAN address?

No. Localhost and private addresses are refused, so this checker cannot be used to probe internal networks.