When a site seems broken, the first question is always: is it down for everyone, or just me? This tool checks a website from our external infrastructure and tells you in seconds whether the issue is on the server side, somewhere on the network, or local to your connection.
We run four checks in sequence: DNS resolution → TCP port 443 → TCP port 80 → HTTP GET. Each step is reported individually so you can see exactly where the failure occurs.
Possible verdicts
- UP — server reachable and responding with a 2xx/3xx code.
- UP with errors — DNS and TCP fine, but the application itself returns 4xx or 5xx.
- DOWN — DNS fails, or no TCP port answers, or HTTP times out.
FAQ
The site works for me but you say "DOWN" — why? Some sites block our datacenter IP range or apply aggressive bot protection. Try ping and port check to confirm.
Why does it say "UP with errors"? The infrastructure is healthy but the app returned a 500 or 503. That's a backend bug, not a network issue.
What if only DNS fails? The domain is expired, misconfigured or the DNS delegation broke. Check whois for expiration.