Is It Down?
For everyone, or only for you
How do you know if a site is really down?
When a site will not load there are three suspects: the site itself, your own network, or something in between (DNS, your ISP, a VPN). This tool checks from two different points at once — your browser and an outside server — and works out where the problem sits from the combination.
"Down only for you" — what to do
- Try opening the site on your phone over mobile data, not Wi-Fi.
- Flush your DNS cache or switch to a public DNS resolver (8.8.8.8 or 1.1.1.1).
- Turn off any VPN, proxy or ad-blocking extensions.
- Check whether the site is blocked on your corporate network.
"Down for everyone" — what to do
If it is your own site, check your hosting control panel, your domain's expiry date and your SSL certificate's expiry date. If it belongs to somebody else, all you can do is wait.
Frequently asked questions
How do you know if a site is down for everyone?
The check runs from two points at once: your own browser and a neutral outside server located somewhere entirely different. If both fail, the site really is down. If the outside server gets through and your browser does not, the problem is on your end. That cross-check is the whole point.
The site loads for me but you say it is down
Usually caching. Your browser is showing a stored copy without contacting the server at all. Try a hard refresh with Ctrl+F5, or open the site in a private window — if it does not load there, it genuinely is unavailable.
What do I do when a site is down only for me?
In this order: open it on your phone over mobile data rather than Wi-Fi, turn off any VPN and ad-blocking extensions, flush your DNS cache or switch to a public resolver such as 8.8.8.8 or 1.1.1.1, and check whether a corporate network is blocking it. One of those four fixes it most of the time.
My own site is down — what should I check first?
Three things, in order of likelihood: whether the domain has expired, whether the SSL certificate has expired, and whether you have hit a hosting resource limit. Those are the three most common causes for a small site, and all three take a minute to check in your control panel. You can test the certificate with our SSL checker.
Why is the result sometimes inconclusive?
Some sites block automated requests or refuse cross-origin requests for security reasons. The outside server then gets no answer, but that does not mean the site is down. The external-check link in the result gives you a third opinion.
How long until a downed site comes back?
It depends on the cause. A temporary server fault, minutes. A resource limit, until it is lifted. An expired domain, up to 48 hours after renewal because of DNS propagation. An expired SSL certificate, immediately after renewal.