Is It Down?
Tests reachability from our server three times and reports where a failed request stopped.
We fetch the page for you. Our server fetches the public address you enter and reads the response. Nothing you enter is stored. Free, no account.
How it works
You type your own address and the page hangs, or a customer tells you the site is broken. This tool requests your site three times from our server, a moment apart, outside your network. If it fails you see the step where it failed. Three successes prove reachability from our network, not every region or browser.
- 1
We request the site three times, a moment apart, from outside your network.
- 2
If it fails, you see the step where it fails: the DNS lookup, the connection, the secure handshake or the server's response.
- 3
Three successes prove reachability from our network, not every region or session. The result suggests further checks.
What it does not do
One location. A site can be down in one region and up in another.
A site that blocks automated requests can answer us with an error while working normally for people; the result points this out when the status suggests it.
When a source is busy or a site does not answer, this tool says so. It never fills the gap with a guess.
Questions
The tool says the site is up but I cannot reach it. What now?
Three successful requests from outside your network mean the site is answering. That does not rule out regional outages or different responses for your session. A stale DNS entry, VPN or local connection is another possibility. The result suggests what to try. Compare with another network, such as your phone on mobile data, to narrow it down.
It says the DNS lookup failed. What does that mean?
The lookup never got past the domain name stage, so the request stopped before any connection to a server. Common causes: a typo in the address, nameservers that are down, or a recent change that has not spread. Check the spelling, then check the domain at your registrar.
The site blocks bots. Will this tool give a false result?
It can. A site that blocks automated requests may answer our server with a 403 or a challenge page while working normally in a browser. When the status suggests that, the result points it out, so check the address in a browser before assuming the site is broken.
Tools that answer the next question
- HTTP Status Code CheckerChecks up to 25 addresses at once and reports the status code, final address and response time of each.
- Website Ping TestTimes five requests to a site and breaks each one into DNS, connection, TLS and first byte.
- Redirect CheckerFollows an address hop by hop and shows every redirect, status code and delay on the way to the final page.