Website Down Checker
Enter a site to check it from outside your own network. domhaul resolves its DNS, connects, follows any redirects and reports whether the server answered, with what status and in how many milliseconds, from one Cloudflare data center, named in the result. If it answers here but not for you, the problem is on your side: your DNS, your network, a VPN, a browser cache or a block in your country. If it fails here too, it is down for everyone, and the result says at which step it broke: DNS, the connection, or an error from the server itself (5xx). All 12 well-known sites below answered on 10 November 2026, in a median of 247 ms for the whole chain.
Free, no sign-in, 20 checks a minute. http and https on the standard ports only; private and local addresses are refused. Also: Redirect checker, HTTP header checker.
Response times of well-known sites
Checked on November 10, 2026 from one US connection, with the same code this tool runs. Click a site to run it live.
| Site | Answer | Status | Hops | Total ms | Last hop ms | Server |
|---|---|---|---|---|---|---|
| google.com | Up | 200 | 2 | 247 | 100 | gws |
| github.com | Up | 200 | 2 | 211 | 139 | github.com |
| amazon.com | Up | 202 | 3 | 475 | 113 | CloudFront |
| apple.com | Up | 200 | 2 | 129 | 100 | Apple |
| microsoft.com | Up | 200 | 4 | 954 | 787 | |
| wikipedia.org | Up | 200 | 3 | 199 | 75 | mw-web.codfw.main-679d... |
| cloudflare.com | Up | 200 | 2 | 252 | 215 | cloudflare |
| netflix.com | Up | 200 | 3 | 645 | 462 | envoy |
| youtube.com | Up | 200 | 3 | 571 | 214 | ESF |
| bbc.co.uk | Up | 200 | 3 | 167 | 100 | BBC-GTM |
| stripe.com | Up | 200 | 2 | 188 | 123 | nginx |
| example.com | Up | 200 | 1 | 43 | 43 | cloudflare |
Total runs from the first request to the final page's headers, every redirect included; Last hop is the final request alone. amazon.com's 202 still counts as up, since the server answered.
Website Down Checker questions
Is it down for everyone or just me?
If this check gets an answer and your browser does not, it is just you. Try the site on mobile data instead of Wi-Fi, in a private window, with your VPN or ad blocker off, and after flushing your DNS cache; if it then loads, one of those was the cause. If this check fails as well, the site is down for everyone, at least from here. One check comes from one place, though: a CDN can fail in one region while others work, so the data center code shown with the result tells you where the answer came from.
What do 502, 503 and 504 errors mean?
All three mean a server in front of the site is up but the site behind it is not answering properly. 502 Bad Gateway: a proxy or load balancer got an invalid answer from the server behind it, often because the app crashed. 503 Service Unavailable: the server is overloaded or down for maintenance, sometimes with a Retry-After header saying when to come back. 504 Gateway Timeout: the server behind the proxy took too long. This checker counts any 5xx as down, because visitors get an error page.
What are Cloudflare errors 520 to 526?
Cloudflare is up, but the site's own server behind it is not. 520: the server sent back an empty or unexpected answer. 521: it refused the connection, usually because the web server is stopped or a firewall blocks Cloudflare's addresses. 522: the connection timed out. 523: the server could not be reached at all. 524: it took longer than 100 seconds to answer. 525: the SSL handshake with it failed. 526: its certificate is invalid while Cloudflare is set to Full (strict). Only the site's owner can fix these, and Cloudflare's own status page will not list them.
The site answers 403 or 429 here. Is it down?
No, it is up and refusing this request. 403 Forbidden is usually bot protection (a Cloudflare, Akamai or AWS WAF rule) turning away a client that is not a browser, or a block by country; 429 Too Many Requests is a rate limit. Both prove the server is running, so this checker reads them as up. If your own browser gets a 403 too, the block may be on your IP address or country, which only the site's owner can lift.
How fast should a website respond?
Google's guidance on web.dev treats a time to first byte of 0.8 seconds or less as good and over 1.8 seconds as poor, measured at the 75th percentile of real visits. The time shown here covers the whole chain from one data center: every redirect, each with its DNS lookup, connection and TLS handshake, up to the moment the final response headers arrive. It is not the full page load, and a phone on a mobile network will see more. In the table below, example.com answered in 43 ms with no redirect, while microsoft.com's three redirects and final page took 954 ms.
More free website and domain tools
The redirect checker follows a URL through every 301, 302, 307 and 308 to the page that answers. The HTTP header checker shows the response headers a URL sends and grades its six security headers. When a name does not resolve at all, the DNS lookup, the DNS propagation checker, the CNAME lookup and the Nameserver lookup show what its DNS says. For who owns a domain and when it expires, use the WHOIS lookup; to find a name that is still free, the domain availability checker.