Checking if a site is down for everyone, not just you
Enter a URL and this tool makes a direct server-to-server request to it from this server - completely bypassing your own browser cache, your local DNS, and your own network - so you get a genuinely independent answer to "is it just me, or is this site actually down for everyone?" It reports whether the site responded at all, its HTTP status code, and the response time.
Why checking from an independent server matters
A huge share of "the website is down" reports turn out to be local problems - a stale DNS cache, a browser extension blocking the request, an ISP-level issue, or a regional outage affecting only some visitors. Because this check runs entirely from this server's own network and has no connection to your device or ISP, it gives you a genuinely separate data point to rule those local causes in or out.
What counts as "down" here
A connection failure - a DNS error, a timeout, or a refused connection - or a server error response (any 500-range HTTP status code) is reported as down. A 4xx client error, like a 404 Not Found, is reported as up, because the server itself is responding and working - it's simply not returning the specific page you expected, which is a different kind of problem than the site being offline.
What to do if it shows down for everyone
Check the site's official status page or social media accounts if available, try again in a few minutes since many outages are brief, and if it's your own site, check your hosting provider's status dashboard and server logs for the actual underlying cause.