Website Down Checker
Down for everyone or just you? One check from Cloudflare, one from your browser.
Check a website
Checking from Cloudflare and from your browser…
Result
Likely causes
What you can do
How to clear the DNS cache
- Windows (Command Prompt)
ipconfig /flushdns - macOS (Terminal)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Linux with systemd-resolved
resolvectl flush-caches - Chrome, Edge, Brave
chrome://net-internals/#dns → Clear host cache - Android / iPhone
Turn airplane mode on and off again
Response details
About the Website Down Checker
Find out whether a website is down for everyone or only for you. MySmartCoPilot’s server requests the address from the Cloudflare data centre that handled your visit — usually one near you — and reports whether it answered, the HTTP status code, how long it took and where redirects led. When it fails, you see the exact reason: a domain that does not exist, missing DNS records, a timeout, a refused or failed secure connection, an invalid certificate, a server error, or one of Cloudflare’s own error codes.
At the same time your browser tries to reach the site directly. If MySmartCoPilot can reach it and you cannot, the problem is on your side — your DNS cache, VPN, network or internet provider — and the page lists the fixes, including the commands to clear your DNS cache.
How to use it
- Enter the address, such as
example.comor a full URL likehttps://example.com/login. - Keep Also test from this browser on to compare MySmartCoPilot’s view with yours.
- Press Check website. The verdict at the top says whether the site is up, down for everyone, or unreachable only for you.
- Read Likely causes and What you can do. For problems on your side, open How to clear the DNS cache for the command for your system.
- Press Copy report to send the result to the site’s owner or your IT support.
Examples
example.com is up From Cloudflare · Mumbai, India (BOM): Up — 200 OK · 182 ms From your browser: Reachable
It’s just you: example.com is up, but your browser cannot reach it From Cloudflare: Up — 200 OK · 95 ms From your browser: Cannot connect
Clear your DNS cache, try another DNS resolver (1.1.1.1 or 8.8.8.8), turn off your VPN or blocker, or try mobile data.
example.com looks down for everyone The site is behind Cloudflare, but Cloudflare could not connect to the web server in time (error 522).
Cloudflare itself is fine; the server behind it is not answering.
Common uses
- A site will not load and you want to know whether to wait or fix something on your side.
- Telling a customer or colleague whether your site is reachable from outside your office network.
- Getting the precise error (DNS, TLS, timeout, 5xx) to give your hosting provider.
- Checking a site after DNS, hosting or certificate changes.
What the errors mean
- Domain does not exist (NXDOMAIN): a typo, an expired domain, or one that was never set up.
- No A or AAAA records / DNS failure: the domain exists, but its DNS does not say where the server is, or its DNS servers are failing.
- Timeout or connection failed: the server is down or overloaded, nothing listens on the port, a firewall drops the connection, or the secure (TLS) connection cannot be set up.
- 5xx status (500–599): the server answered but could not produce the page (RFC 9110 §15.6).
- Cloudflare 520–526 and 530: the site uses Cloudflare and the problem is between Cloudflare and the site’s own server — 521 “web server is down”, 522 “connection timed out”, 524 “a timeout occurred”, 525 SSL handshake failed, 526 invalid SSL certificate, 530 Cloudflare could not resolve the origin’s address (Cloudflare 5xx errors).
- 4xx status: the site is up, but this page is missing (404), needs a login (401), refuses the request (403 — often bot protection or a regional block) or is rate-limited (429).
Why “just you” happens
- Your device or router still uses an old or wrong DNS answer — clearing the DNS cache or switching to another resolver fixes it.
- A VPN, proxy, firewall, antivirus or browser extension blocks or reroutes the connection.
- Your internet provider, company, school or country blocks the site, or a route between you and the site is broken.
- The site blocks your network or region, or one of its servers fails while others work.
How the check is made
MySmartCoPilot’s server runs on Cloudflare’s network: the request comes from the data centre that received your visit (shown with the result). It looks the name up over DNS-over-HTTPS, refuses private and internal addresses, then sends a GET request as MySmartCoPilotBot without cookies, follows up to 5 redirects (browsers allow 20) and waits up to 10 seconds per request. The browser test asks the site from your own connection without cookies or a referrer. Browsers do not reveal another site’s status code to a web page, so it can only tell whether something answered — an error page counts as an answer too.
Some sites tell browsers not to share their pages with other websites at all (the Cross-Origin-Resource-Policy: same-origin header), and a secure page may not follow a redirect to an http:// address. MySmartCoPilot’s server sees both in the site’s answer; the browser test is then marked Can’t tell instead of reporting that you cannot connect.
Limitations
- One check from one location: an outage that affects only some regions or networks may not show.
- Some sites block automated or cloud-based requests (403, bot checks) while working for people in a browser.
- The browser test cannot see status codes, and ad or privacy blockers can make it fail. It cannot test sites that forbid other websites to read them (Cross-Origin-Resource-Policy); the result then rests on MySmartCoPilot’s check alone.
- Browsers do not let a secure page contact http:// addresses, so http:// sites are tested from MySmartCoPilot’s server only.
- It checks once when you press the button — it does not monitor a site or send alerts. Each visitor has an hourly limit.
Privacy
The address you enter is sent to MySmartCoPilot’s server, which requests it from the site (as MySmartCoPilotBot, without cookies) after a DNS-over-HTTPS lookup. With the browser test on, your browser also requests the site directly, without cookies or a referrer, so the site sees your IP address as it would if you visited it. MySmartCoPilot does not store the address or the result; its log records only the host, status code and time of each request.
Frequently asked questions
How do I know whether a site is down for everyone or just me?
Compare the two cards. If MySmartCoPilot (from Cloudflare) gets an answer but your browser cannot connect, it is just you. If both fail, the site is most likely down for everyone. If MySmartCoPilot gets no answer at all but your browser connects, the site may block cloud networks or some regions. When the browser card says Can’t tell, the site does not allow the test from another website — open it in a new tab to see whether it loads for you.
What do Cloudflare errors 521, 522 and 524 mean?
The site uses Cloudflare, and Cloudflare is working, but the site’s own server is the problem: 521 means it refused the connection (usually down), 522 that it did not accept the connection in time, and 524 that it accepted but took too long to answer. Only the site’s owner or host can fix these.
The site is up, but it will not load for me. What should I do?
Reload without the cache, then clear your DNS cache (commands on this page), try another DNS resolver such as 1.1.1.1 or 8.8.8.8, turn off your VPN, proxy or blocker, and try another network such as mobile data. If nothing helps, your provider or network may block the site.
Why does the check say 403 Forbidden?
The site answered but refused the request. Many sites block automated or data-centre requests, or whole countries, to stop bots. People in a normal browser may still get in — the browser test shows whether you can.
How do I clear my DNS cache?
Windows: ipconfig /flushdns in Command Prompt. macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. Linux with systemd-resolved: resolvectl flush-caches. Chrome and Edge also keep their own cache: open chrome://net-internals/#dns and press Clear host cache. On a phone, switch airplane mode on and off.
Can it monitor a website and alert me when it goes down?
No. It checks once each time you press the button. For continuous monitoring with alerts, use an uptime-monitoring service.