Idiomas

Website Down Checker

Free, no signup. Is it down from this independent Cloudflare vantage point? Check one URL for its current response, redirect path, and a bounded explanation.

Built by Patrick Stox

Checks run from our server; we fetch the URL you enter and don't keep the results. This is one point-in-time request from a Cloudflare location, not a multi-region uptime monitor. HTTPS results show only whether a connection completed — never certificate expiry or full TLS details. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Website Down Checker? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
Sample report
Illustrative example — deterministic fixed response data
Reachable, but returning an error
The server responded with HTTP 503; that is different from a network outage.
842 ms · TLS handshake succeeded.
  1. 301 — http://example.test/status
  2. 503 — https://example.test/status
The example is classified from the shown status, hops, latency, and TLS state. It does not claim that example.test was requested.
 
 
 
How to use it
  1. Enter the exact page URL, including HTTPS and path when relevant.
  2. Choose Check website and read the reachability verdict before the timing.
  3. Inspect the redirect chain to confirm the final response is the page you expected.
  4. Follow the DNS, hosting, and RDAP links when the report receives no HTTP response.
 
 
 
       
     
     
What the results mean
  • Reachable means the final status is below 400 from this location.
  • Reachable, but returning an error means an HTTP 4xx or 5xx response arrived; the network path worked.
  • DNS name not found is used when the fallback DNS probe returns NXDOMAIN.
  • TLS connection failed, timed out, or not reachable describe the bounded failure evidence; they do not identify a certificate or origin root cause.
 
How it works
A Cloudflare Worker makes a bounded external request, records the redirect hops, final status, elapsed time, and whether an HTTPS connection completed. When no HTTP status arrives, a fallback DNS result and the returned error text help distinguish NXDOMAIN, TLS failure, timeout, and other unreachable states.
 
Features
  • One point-in-time external reachability check.
  • Final status plus complete observed redirect path.
  • Latency and limited TLS-handshake state.
  • DNS fallback evidence and prefilled diagnostic handoffs.
 
Limitations
This is not continuous or multi-region monitoring. It cannot prove availability for every user, inspect application correctness behind a 200, expose certificate details, bypass bot protection, or distinguish every firewall, routing, DNS, origin, and transient network cause.
 
Frequently asked questions
Is the website down for everyone or just me?
This checker can only say what happened from one Cloudflare location at one moment. Compare another network or a multi-region monitor before concluding that everyone is affected.
Does an HTTP 500 mean the website is down?
The server is reachable, but it is returning an application or server error. The tool labels that “reachable, but returning an error” rather than treating it as a network outage.
Can the checker diagnose an expired TLS certificate?
No. It reports whether a secure connection completed or failed, but the Worker interface does not expose certificate expiry, chain, hostname, or cipher details.
Why does the site work for me but show as unreachable here?
The target may vary by geography, IP reputation, firewall policy, DNS resolver, user-agent, cache, or timing. A single external vantage point is useful evidence, not an uptime consensus.
Next stepHosting Checker — look up the exact spec and expected values.

People also explore
ToolHTTP Header CheckerToolDNS CheckerToolWebsite Safety & Security CheckerArticle200 OKArticle204 No ContentArticleBlocked Due to Unauthorized Request (401)
 
 
 
Feature requests for Website Down Checker
 

Upvote what you want most. New ideas can be submitted from the floating Feedback menu;
      requests appear here once approved, and the most-wanted rise to the top.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
   
  
Sobre a ferramenta
Verificação whether um URL é reachable de um Cloudflare location right now, com status, redirecionamento cadeia, timing, DNS fallback evidência, e honesto TLS limites.
O alvo pode vary por geography, IP reputation, firewall policy, DNS resolver, user-agent, cache, ou timing. Um single external vantage point é useful evidência, não um uptime consensus.
Recursos
  • Features Um point-in-time external reachability verificação. Final status plus Concluído observado redirecionamento caminho. Latency e limited TLS-handshake estado. DNS fallback evidência e prefilled diagnostic handoffs.
  • Como funciona Um Cloudflare Worker makes um limitado external solicitação, registros o redirecionamento hops, final status, elapsed time, e whether um HTTPS connection concluído. Quando Não HTTP status arrives, um fallback DNS resultado e o retornado Erro texto help distinguish NXDOMAIN, TLS failure, timeout, e outro unreachable states.
  • O que o resultados mean Reachable means o final status é below 400 de este location. Reachable, but returning um Erro means um HTTP 4xx ou 5xx resposta arrived; o rede caminho worked. DNS nome não encontrado é usado quando o fallback DNS probe retorna NXDOMAIN. TLS connection failed, timed out, ou não reachable describe o limitado failure evidência; they faça não identify um certificate ou origin root cause.
  • Amostra relatório Illustrative example — determinístico fixed resposta dados Reachable, but returning um Erro O servidor responded com HTTP 503; que é different de um rede outage. 842 ms · TLS handshake succeeded. 301 — http://example.test/status 503 — https://example.test/status O example é classified de o mostrado status, hops, latency, e TLS estado. Isso faz não alegação que example.test foi requested.
Como funciona
Como funciona Um Cloudflare Worker makes um limitado external solicitação, registros o redirecionamento hops, final status, elapsed time, e whether um HTTPS connection concluído. Quando Não HTTP status arrives, um fallback DNS resultado e o retornado Erro texto help distinguish NXDOMAIN, TLS failure, timeout, e outro unreachable states.
Limitações
  • Limitations Este é não continuous ou multi-region monitoring. Isso cannot prove availability para cada user, inspecionar application correção behind um 200, expose certificate detalhes, bypass bot protection, ou distinguish cada firewall, routing, DNS, origin, e transient rede cause.
  • Este verificador pode somente say o que happened de um Cloudflare location em um moment. Compare outro rede ou um multi-region monitor antes concluding que everyone é affected.
Perguntas frequentes
É o site down para everyone ou just me?
O alvo pode vary por geography, IP reputation, firewall policy, DNS resolver, user-agent, cache, ou timing. Um single external vantage point é useful evidência, não um uptime consensus.
Faz um HTTP 500 mean o site é down?
O servidor é reachable, but isso é returning um application ou servidor Erro. O ferramenta labels que “reachable, but returning um Erro” rather than treating isso como um rede outage.
Pode o verificador diagnose um expired TLS certificate?
Não. Isso relatórios whether um secure connection concluído ou failed, but o Worker interface faz não expose certificate expiry, cadeia, hostname, ou cipher detalhes.
Por que faz o site work para me but mostrar como unreachable here?
O alvo pode vary por geography, IP reputation, firewall policy, DNS resolver, user-agent, cache, ou timing. Um single external vantage point é useful evidência, não um uptime consensus.