Is It Down?
Check whether a website responds from our server and investigate the response. A result from this location does not show what every visitor can reach.
How the check works
We look up the domain's IP address, connect to it and request the page, following up to six redirects. If a bare domain fails over HTTPS, we also try plain HTTP so you can tell a certificate problem from a server that is switched off. The result tells you which step failed.
What the common failures mean
- The domain does not resolve. There is no DNS record for it, or the domain has expired. Nothing else can work until that is fixed.
- Connection refused. The server is online but nothing is listening for web traffic. The web server has probably stopped.
- Timed out. The server did not answer at all. It may be off, overloaded, or blocking us at the firewall.
- 5xx errors. The web server is running, but the site behind it failed. A 502 or 504 usually points to PHP or the application.
- Cloudflare 52x errors. Cloudflare itself is fine, but it cannot get a good answer from the server behind it. The result explains each code.
Limitations
- This is one check from one place at one moment. A site can be down in one region and up in another, or come back a minute later.
- Sites behind strict bot protection may block our request even when they are working for people. We say so when we can tell.
- We check the web page only, not email, apps or other services on the same domain.
Questions
The site is up here but not for me. Why?
Common causes are an old DNS answer cached on your device or router, a network that blocks the site, a browser extension, or a firewall on the site that has blocked your IP address. The steps in the result help you narrow it down.
Can you tell me when a site comes back?
Not yet. Uptime monitoring with alerts is planned for a later release. For now, run the check again in a few minutes.