All ToolsDown Detector
Down Detector

Is Any Website Down Right Now?

Check live HTTP status codes, TLS response times, DNS records, and your own browser connection to see if a website is down for everyone or just you.

Web Optimization · Live Uptime, HTTP & DNS Diagnostics

Know in Seconds If a Website Is Down for Everyone or Just You

Checking whether a site is truly offline requires more than a single guess. Our Down Detector runs two real-time diagnostics side by side—a live server-edge HTTPS and DNS-over-HTTPS probe paired with a direct reachability timing test from your own browser—so you immediately know whether an outage is global or isolated to your local Wi-Fi, VPN, or ISP.

Quick Reference: What Website Outage Signals Mean

Item / RuleStandard ReferencePractical Impact
HTTP 200 – 399Site Is OnlineThe origin server or CDN edge responded cleanly with active web content or a valid redirect.
HTTP 403 / 429Online (Firewall Active)The server is up and serving visitors, but its firewall or bot shield screens automated probes.
HTTP 500 / 502 / 503Server Outage / OverloadThe website backend or upstream proxy crashed, timed out, or is temporarily overloaded.
DNS NXDOMAINDomain Not ResolvingGlobal DNS cannot find records for this hostname—often caused by a typo, deleted zone, or expired domain.
Edge Up / Browser FailedLocal Network IssueThe website is online globally, so the block is on your router, VPN, corporate firewall, or local DNS.
TLS / TimeoutUnreachable From EdgeThe server refused TCP/HTTPS connections or failed to answer before the network timeout elapsed.

How Multi-Layer Outage Detection Works

01

Enter Any Website or Domain

Type a domain name like google.com or paste any full page URL into the search bar—we normalize it automatically to its exact host.

02

Run Dual-Path Live Probes

Our edge server inspects HTTPS reachability and global DNS records while your browser measures a direct local timing check in parallel.

03

Inspect HTTP, Latency & DNS Health

Review HTTP status codes, millisecond latency, CDN edge headers, IPv4/IPv6 addresses, and authoritative nameservers.

04

Isolate Global vs. Local Issues

Follow targeted troubleshooting steps if a site loads for our server but fails from your connection due to VPN, DNS cache, or ISP routing.

Diagnostics Included in Every Website Check

01.

Dual-Path Server vs. Browser Comparison

Test target reachability from both our edge server and your own browser simultaneously to pinpoint global outages versus local network blocks.

02.

Live HTTP, Redirect & Firewall Inspection

See exact HTTP status codes (200, 301, 403 WAF challenges, 502/503 server errors), TLS protocol status, CDN edge fingerprints, and response latency.

03.

Real-Time DNS-over-HTTPS Record Audit

Query live A (IPv4), AAAA (IPv6), NS nameservers, and MX mail records alongside DNS response codes like NOERROR, SERVFAIL, and NXDOMAIN.

04.

Dedicated Shareable Status Pages

Every website check opens its own clean status URL so you can bookmark, reload, or share real-time diagnostics for any domain without outbound links.

Why Single-Source Uptime Checkers Often Mislead You

A single HTTP ping tells only half the story. Sometimes a regional ISP outage, stale local DNS resolver, or strict browser extension prevents a page from loading in your tab even though the service is completely healthy for everyone else.

Conversely, modern websites sit behind CDNs and Web Application Firewalls that may issue HTTP 403 challenges to automated server crawlers while normal browsers sail right through. By combining a live server-edge inspection, real-time DNS-over-HTTPS resolution, and an isolated browser timing test in one screen, you get the complete picture without cached stale data or paid external API delays.

Every check runs cleanly against public DNS and standard HTTP protocols without placing outbound backlinks to external target domains.

Website Status & Outage Check FAQ

Helpful answers and practical tips for Down Detector.

AllBlogThings Main Blog

How does the Down Detector tell if a site is down for everyone or just me?

It compares two simultaneous live tests: a probe from our edge server plus global DNS resolution against a direct timing request from your own browser. If our server reaches the site cleanly while your browser fails, the disruption is on your local network, ISP, or VPN.

Why does a healthy website sometimes show HTTP 403 or Firewall Active?

Many major platforms use CDN firewalls to challenge automated server-side requests. Receiving HTTP 403 proves the web server and edge network are online and responding rapidly, especially when your own browser probe connects successfully.

Does checking a website use cached status data or live probes?

Every check runs fresh in real time with Cache-Control: no-store. No cached crowd votes or pre-baked status estimates are shown.

Can I check subdomains or paste a full URL?

Yes. You can paste a full link such as a specific subdomain path and the checker automatically normalizes it to its clean domain or subdomain hostname.