Free tool Website down checker: down for everyone or just you?
Enter a site and three checks run at once: does the domain still resolve, does the server answer a request from Cloudflare’s network, and can your own browser reach it. Comparing the three tells you whether the site is really down, has a DNS problem, or is only unreachable from your network.
- 3 checks at once
- Response time
- Sent only when you click
Check if a website is down
Enter a domain or a full URL. Until you click Check, the result is a sample for example.com.
check.tapcub.com, which fetches it from Cloudflare’s network with the user-agent shown and a From: tools@tapcub.com header, then returns the status codes, response headers and at most 512 KB of the page. One check uses one request. At the same time your browser asks Cloudflare’s public DNS (cloudflare-dns.com) for the domain’s addresses and, if ticked, requests the URL directly from your own connection, which the site sees as a normal visit from your IP address. The service records only the host name, status and timing for rate limiting, not the path, query or page content, and stores no results. Limits: 10 requests a minute and 200 a day per IP address.A domain such as example.com or a full URL.
Status code
200
From Cloudflare’s network.
Response time (ms)
830
Sum of the server responses, including redirects.
Verdict
- OKexample.com is up: it answered 200 in 830 ms.
The three checks
| Check | Result | Detail |
|---|---|---|
| DNS (from your browser) | Resolves: 2 IPv4, 2 IPv6 | 104.20.23.154, 172.66.147.243, 2606:4700:10::ac42:93f3, 2606:4700:10::6814:179a |
| Server (from Cloudflare’s network) | 200 · 830 ms | https://example.com/ |
| Your own connection | Not part of the sample | — |
Share these inputs: the values go after the # in the link, so they never reach a server.
https://tapcub.com/tools/website-down-checker
Version v1.0Updated Update history
How to read the three checks together
Each check fails in a different way, so the combination points to the cause.
All three fine
The site is up. If it still does not load for you, clear the browser cache, try a private window and check whether a specific page, not the whole site, is broken.
DNS fails
NXDOMAIN or no addresses means nobody can reach the site. Common causes: an expired domain, records deleted while changing hosts, or a typo in the name servers.
Server fails, your browser connects
The site is up but turned our request away, or is unreachable from Cloudflare’s data centres. Some sites block cloud and data-centre IP ranges or certain countries.
Server answers, your browser does not
The site is fine; the problem is between you and it: Wi-Fi, a company firewall, VPN, a browser extension or a stale DNS cache on your device.
Our request goes from the Cloudflare data centre nearest to you, not from many places at once. A site that is down only in other regions may look up here. For continuous monitoring from several locations, use an uptime monitoring service.
Three steps
Nothing is requested until you click Check.
-
1
Enter the site
Type the domain or paste the URL that fails for you.
-
2
Click Check
DNS, the server request and (if ticked) your own connection run at the same time and finish within about 8 seconds.
-
3
Act on the verdict
If it is down for everyone, wait or tell the owner. If only you are affected, troubleshoot your network. If you own the site, check the status code and DNS first.
What each check does
Three independent checks, compared:
- DNS: your browser asks Cloudflare’s DNS-over-HTTPS service for the A and AAAA records. Status 3 means the name does not exist (NXDOMAIN)
- Server: check.tapcub.com sends a GET from Cloudflare’s network with an 8-second timeout per hop, following up to 5 redirects. 2xx and 3xx count as up, 4xx as up with an error, 5xx, timeouts and connection failures as down
- Your connection:
fetch(url, { mode: "no-cors" })from your browser. A cross-site response is opaque, so the browser only learns whether a connection was made - Response time is the sum of the server’s answers (each redirect included), without our own DNS checks
| DNS | Server | Your browser | Verdict |
|---|---|---|---|
| OK | 2xx / 3xx | Connected | Up |
| OK | 2xx / 3xx | Failed | Up, problem on your side |
| OK | 4xx (403, 429) | — | Up, but refused our checker or this URL errors |
| OK | 5xx / timeout | Failed | Down for everyone |
| OK | Timeout | Connected | Blocking data centres or a regional problem |
| NXDOMAIN / none | — | — | DNS problem |
example.com on 2026-11-17
The sample on this page was checked on 2026-11-17 (without the browser check).
| Check | Result | Reading |
|---|---|---|
| DNS | 2 IPv4 and 2 IPv6 addresses | The domain resolves; the addresses are Cloudflare’s |
| Server | 200 in 830 ms | Up; served from Cloudflare’s cache (cf-cache-status: HIT) |
| Verdict | Up | No redirects, no error |
A site that times out from the server check while your browser connects is the interesting case: it means the site is up but treats requests from data centres differently from those of home connections.
Misreading an outage
Most “the site is down” reports turn out to be something narrower.
Blaming the server for DNS
After moving hosts, old DNS answers can linger in caches for hours. Check what DNS returns before restarting anything.
Taking a 403 as down
A firewall that blocks checkers returns 403 or a challenge page while real visitors get in. Test from a browser too.
Testing one page
One broken URL is not an outage. Check the homepage and the failing page separately.
Ignoring slow responses
A server that answers in 10 seconds is up on paper and down for visitors who leave first.
Notice problems from your own traffic
TapCub does not ping your site, but your analytics shows when pages start failing for real visitors.
Errors next to speed
JavaScript, resource and API errors with affected sessions, in the same report.
Learn more404s with their source
Broken internal links show up as 404 visits together with the page that sent people there.
Learn moreWeb Vitals per page
Real-user LCP, INP and CLS for each page, to see whether a script (ours included) slows it down.
Learn moreWebsite down checker questions
Still have a question?
Chat with the team behind TapCub — we usually reply within a few hours on business days.
How do I know if a website is down for everyone or just me?
Run the check above. If our server request succeeds and your browser fails, the problem is on your side. If both fail, or the server returns 5xx, it is down for everyone.
Why does a site work for me but show as down here?
Our request comes from a Cloudflare data centre. Some sites block cloud IP ranges, rate-limit unknown clients, or only serve some countries. Your browser check shows whether it works from your own connection.
What does a 503 error mean?
503 Service Unavailable means the server is overloaded or in maintenance. If it sends a Retry-After header, it says when to try again.
What is NXDOMAIN?
The DNS answer for “this name does not exist”. Either the domain is misspelled, expired, or its records were removed.
Can this monitor my site continuously?
No, it is a one-off check from one location. For uptime percentages and alerts you need a monitoring service; the uptime calculator turns an SLA percentage into allowed downtime.
Does the direct browser check reveal anything about me?
It is an ordinary request from your browser to that site, so the site sees your IP address, as with any visit. No cookies are sent. Untick the option if you do not want that.
Update history
New features, fixes and data refreshes for this tool, newest first.
-
· v1.0
LaunchedFirst release.
Data this tool relies on
- Sample fetches (github.com, apple.com, wikipedia.org, example.com, bbc.com) — checked 2026-11-17, reviewed every 6 months (next review by 2027-05-17)
Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates
Dig into the cause
Once you know where it fails, look closer at that layer.