SiteDownRightNow
Home › Website Down Checker

Website Down Checker

Wondering whether a site has crashed, or if it is only your connection acting up? Drop in any link — we will ping it live from our own server and report back what happened: did it answer, what code it sent, how long it took, and where it bounced you.

How the checker works

From your question to a clear-cut answer in four moves.

1

You enter a website.

Paste a domain like example.com, or any link copied straight from your browser's address bar.

2

We send a live request.

Our server visits the address exactly like a browser does, then waits up to eight seconds for a reply.

3

We follow redirects.

If the address forwards us elsewhere, we trail it for up to four jumps and log each one.

4

You see the result.

You get the full picture: response or silence, status code, reply speed, the redirect trail, and the precise check time.

What the result means

Each probe closes with one of these four calls.

Responding

The site replied to our probe. Note: pages that shoo away bots with a 401 or 403 are still alive behind the scenes — we mark those as responding as well.

Couldn't reach

Silence beyond eight seconds, a 5xx breakdown, or a 429 slow-down notice. The site could genuinely be offline — or it might just be swatting automated visitors away for the moment.

Redirected

The link handed us off to a different address. You will see the final destination along with the complete hop-by-hop trail.

Kept redirecting

It kept tossing us from one address to the next, so we called it quits after four hops — much like your browser does when it flashes "too many redirects".

HTTP status codes you may see

Decode the digits your result throws at you.

Our result Responding
200 OK

The page came back fine.

401403

Bots got turned away at the door, but the server itself is awake.

404

The server is alive — that particular page just is not there.

Our result Redirected
301302303307308

The address has shifted, and the site pointed us to its new home.

Our result Couldn't reach
429

We are being asked to slow down — the site is throttling traffic right now.

500502503504

Something broke on the site's own servers or gateway.

No answer

The request timed out, the domain did not resolve, or the security certificate failed.

Is it down or just you?

Because the probe leaves from our machines rather than yours, the verdict points you toward the real culprit.

If our check gets an answer

The site is up.

Odds are the snag sits somewhere on your side of the connection:

your Wi-Fi or mobile datayour internet provider (ISP)your DNSa VPNyour browser
If our check cannot reach it either

It is probably down for everyone.

…unless the site is simply stonewalling automated probes at the moment. Two sensible next moves:

  • Give it a few minutes, then probe it once more.
  • A brand's official social accounts are typically where outages get acknowledged first.

Website not loading for you? Try these

Six speedy remedies for the classic "works for them, not for me" puzzle.

Hop between Wi-Fi and mobile data. Loads on one but not the other? Your connection is the culprit.
Try a private or incognito window. Works there? Wipe that site's cookies and cached files, then reload.
Switch off extensions and disconnect any VPN, then give the page another shot.
Reboot your router, or point your DNS at a public resolver like 1.1.1.1 or 8.8.8.8.
Glance at your device's clock. A wrong date or time trips up security certificates on loads of sites.
Borrow a different browser or device. Dead everywhere? Then it is very likely down for all.

Services we track

These come with crowd reports on top of the probe — a fuller story than any single test.

See all services →

Checking a website: common questions

The remaining curiosities, answered.

What is a website down checker?
A free tool that answers one question: is this website actually working at this moment? Ours knocks on the site’s door from our server and lays out the evidence — answer or silence, status code, speed, and redirect trail — so you can judge whether the outage is global or personal.
Is a website down for everyone or just for me?
When our server gets a reply and you don’t, the fault line runs through your own setup — connection, DNS, VPN, or browser. When our probe comes back empty-handed too, the site is very likely dark for everyone.
Why does a site I can open show a 403 result here?
Plenty of sites slam the door on bots with a 401 or 403 while welcoming human browsers warmly. A 403 tells us the machine is powered on and listening — it just dislikes robots — so we file it under responding.
Why does a website work for others but not for me?
Nine times out of ten the gremlin lives between you and the site: wobbly Wi-Fi, an ISP hiccup, stale DNS, a VPN in the way, or a rogue extension. The fix-it list further up tackles them one by one.
Is this the same as uptime monitoring?
Not quite. Uptime monitoring babysits a single site around the clock and pings its owner when it naps. This is a spur-of-the-moment health check for any public website, whenever curiosity strikes.
How often can I check a website?
Whenever you need to, within reason. There’s a per-visitor speed limit to keep things snappy for all — bump into it and a minute’s breather will reset you.
Can I check an app instead of a website?
Apps don’t expose a public address to knock on, so not directly. But an app usually leans on the same backend as its website, making the site check a decent stand-in — and our directory shows what fellow users are reporting for the service itself.
Does the checker work for any website?
Anything public, yes. Truly private corners — localhost, your router’s admin page, office intranets — are fenced off for safety and can’t be probed.