Is it down right now?
Check whether a website or service is reachable: DNS, TCP connect and HTTP status.
What this tool checks
When a site will not load, the failure could be at DNS, at the network level, or in the application itself. This tool runs three separate checks to find exactly where it broke: DNS resolution, TCP connection, and an HTTP request.
Reading the results
DNS failed— the domain did not resolve to an IP. The domain may have expired, DNS records may have been changed, or propagation is still in progress. If this check resolves it but you cannot, the issue is your ISP's resolver or your router's DNS cache.
TCP failed— the server is unreachable at the network level. The port is not listening, a firewall is blocking the connection, or the server is offline. A successful TCP connect does not mean the application is healthy, only that the port is open.
HTTP status codes:
- 200–299 — site is up and responding normally.
- 301–308— server is up and redirecting. We follow redirects, so you see the final status.
- 401 / 403— server is running but blocking access. The site is technically up.
- 404— server is up, the root path just does not exist. Reachable.
- 500–599— server is reachable but the application is failing. A 503 often means maintenance or overload.
- No response— TCP connected but HTTP timed out. Usually a TLS handshake failure or a crashed application process.
Down for everyone or just you?
This check runs from our server, not your network. If we can reach the site and you cannot, the problem is on your end: your ISP, a stale DNS cache, a browser extension, or a firewall rule. If we cannot reach it either, it is likely down globally, or at least from our server's region.
CDN caveat
Large sites use CDNs that serve traffic from dozens of locations. A site can be down in one region and working everywhere else. This is one check from one server. Some sites also block cloud provider IP ranges, which can make a working site appear unreachable from here.