HomeFree ToolsWebsite Down Detector
DNS Reachability • Lookup Latency
Website Down Detector & Response Time Checker
See whether your domain resolves, read the real A record it returns, and time how long the origin server takes to answer from your own browser.
Two independent live checks — a DNS-over-HTTPS lookup and a timed request to the origin — run side by side. A browser cannot read a cross-origin status code or TLS certificate, so those are reported as not measurable rather than guessed.
Live DNS Lookup
Real A record from the resolver.
DNS Latency
Exact millisecond timing of the lookup.
Origin Timing
Measured server response time.
Layer Split
DNS fault or host fault.
Website Down Detector & Response Time Checker
Two separate live checks from your browser: a DNS-over-HTTPS lookup that returns the real A record and lookup latency, and a timed request to the origin. A browser cannot read a cross-origin status code or TLS certificate, so those are reported as not measurable rather than guessed.
Resolving DNS and timing the origin response…
Running the DNS-over-HTTPS lookup and the origin request at the same time.
Not checked yet
A record: ——
Measured over DNS-over-HTTPSNot measured yet
Status code & TLS are not browser-readableRead The Result Checklist:
- DNS resolves, origin silent: the problem is at the host — an expired certificate, a dead origin process, or a firewall dropping your traffic.
- DNS does not resolve: the failure is at the name — a nameserver delegation problem, a missing A record, or a registrar hold on the domain.
- Everything resolves and answers here, but users report a problem: the fault is regional — an edge node, an ISP resolver, or a caching layer close to your users.
How Do You Determine If a Website Outage is Global or Local?
Website downtime is systematically diagnosed across three network layers: 1) Local Client/Resolver Failures (stale OS DNS cache, ISP recursive resolver timeouts, or VPN/firewall filtering); 2) Edge Network & BGP Partitioning (CDN Anycast failure, intermediate routing blackholes, or TLS handshake termination timeouts); and 3) Origin Application Crashes (HTTP 500 internal errors, 502/504 upstream gateway timeouts, or expired SSL certificates). According to Cloudflare and Akamai performance benchmarks, server response latencies exceeding 2,000ms (2s) trigger 53% mobile user abandonment, while TTFB exceeding Google's Core Web Vitals threshold of 800ms directly suppresses crawl efficiency.
1. Web Outage Diagnostic Decision Matrix
Identify the root cause of connectivity failures based on error codes and response behaviors:
| Observed Symptom | Likely HTTP/DNS Code | Underlying Failure Layer | Immediate Engineering Fix |
|---|---|---|---|
| Site cannot be reached | DNS_PROBE_FINISHED_NXDOMAIN | DNS Nameserver delegation failure or missing A record. | Check registrar nameservers and add host IP in DNS control panel. |
| Bad Gateway | HTTP 502 Bad Gateway | Reverse proxy (Cloudflare/Nginx) cannot reach origin Node/Python process. | Restart origin application worker (e.g. pm2 restart / Docker container). |
| Gateway Timeout | HTTP 504 Gateway Timeout | Origin server overwhelmed by unindexed database query or traffic spike. | Kill locked Postgres queries, increase worker timeout, enable redis cache. |
| Connection Not Private | ERR_CERT_DATE_INVALID | Expired Let's Encrypt or custom SSL certificate. | Trigger automatic certbot renewal or upload current certificate chain. |
| Forbidden Access | HTTP 403 Forbidden | WAF / Cloudflare security rule blocking user IP or country. | Review Cloudflare Security Events and adjust managed rule sensitivity. |
2. Why TTFB (Time to First Byte) Dictates Conversion Rates
TTFB measures the duration from when a client dispatches an HTTP request until the very first byte of response data is received. Industry benchmark data proves:
Optimal Performance: Edge-cached static content (Astro, Next.js SSG) or low-latency CDN origin. Maximize Google Core Web Vitals score.
Acceptable Dynamic: Standard SSR database query time. Suitable for authenticated dashboards and personalized eCommerce carts.
Critical Bottleneck: Every 100ms beyond 1s correlates with a 7% reduction in e-commerce conversion rates and higher bounce probability.
3. The 4-Step Incident Response Playbook for Web Outages
When your production web application triggers downtime alerts, follow this structured engineering checklist:
- 1. Check Edge Health vs Origin Health: Verify if your CDN (Cloudflare/Fastly) is serving stale cache while the origin server (AWS EC2 / DigitalOcean) is down. This buys immediate time for diagnosis.
- 2. Inspect Database Pool Exhaustion: 70% of sudden 500/504 errors stem from unclosed database connections or missing database connection pooling (e.g. PgBouncer).
- 3. Roll Back Recent Deployments: If downtime began within 15 minutes of a git push, trigger an immediate CI/CD rollback before attempting live production debugging.
- 4. Update Public Status Page: Maintain transparency with customers via an external hosted status page (e.g. BetterStack, Instatus) hosted outside your primary cloud provider.
Struggling with Sudden Outages or Slow TTFB?
AnyPlace architects self-healing cloud clusters on AWS, GCP, and Cloudflare Workers with automated multi-region failover and sub-200ms global latency.
Domain Age & Registration Checker
Ensure sudden site downtime is not caused by an expired domain registration or registrar suspension hold.
Check Expiration DateWebsite Uptime & Latency FAQs
Detailed guidance on troubleshooting downtime, interpreting TTFB, measuring latency, and configuring SSL alerts.
How does this Website Down Detector determine if a site is online?
It runs two separate checks from your browser. First, a DNS-over-HTTPS query for the A record, which tells you whether the hostname resolves and how long the resolver took. Second, a live request to the origin to measure how long the server takes to answer. The two are reported separately, because a domain that resolves but never answers is an origin or TLS problem, not a DNS problem.
Why does the tool not show me an HTTP status code?
A browser cannot read the status code of a response from another origin unless that site opts in with CORS headers, so reporting 200 or 502 here would be fiction. The tool instead reports what it can actually observe: the DNS answer, the DNS lookup latency, and the measured time until the origin responded. For a literal status code use curl or a server-side monitoring service.
What does it mean if a site is down 'just for me' vs. 'for everyone'?
If a site is down 'just for you', the remote web server is functioning normally, but your local connection is blocked by local DNS cache, ISP routing, browser extensions, or local firewall rules. If it is down 'for everyone', the host server, origin database, or DNS provider is experiencing an outage.
What is TTFB (Time to First Byte), and why does it matter?
TTFB is the duration in milliseconds between a client sending an HTTP request and receiving the first byte of response data from the server. A healthy TTFB is under 200ms. High TTFB (over 800ms) indicates slow server-side database queries, unoptimized backend compute, or lack of edge caching.
What do 502 Bad Gateway and 504 Gateway Timeout errors mean?
A 502 error occurs when an edge reverse proxy (such as Cloudflare or Nginx) receives an invalid or crashing response from the upstream application server. A 504 error means the upstream server failed to respond within the proxy's configured timeout window, usually due to database lockups or traffic spikes.
How does website downtime affect SEO rankings and Google indexing?
If Googlebot encounters 5xx server errors or timeouts during crawling, it temporarily backs off to avoid overloading your server. If downtime persists for more than 24–48 hours, Google begins demoting rankings and removing affected URLs from search results to preserve user search experience.
How can I fix SSL certificate errors causing site downtime?
SSL handshake errors occur when a security certificate has expired, does not match the requested hostname, or has broken certificate authority chains. Modern architectures prevent this by using automated ACME renewal tools (e.g. Let's Encrypt via Certbot or Cloudflare Universal SSL).
What are the first three steps to take when my website goes down?
First, verify the HTTP status code and server logs to see if the process crashed. Second, verify DNS resolution to ensure your nameservers haven't expired or changed. Third, check origin server resource utilization (CPU, RAM, and database connection pools).
Does AnyPlace provide high-availability architecture engineering and 24/7 recovery?
Yes. We architect resilient, self-healing cloud deployments across AWS, GCP, and Azure with automated failover, load balancing, multi-region database replication, and sub-minute disaster recovery runbooks.
Content last reviewed October 2026.
Related Services
Services That Do This Work
Each service page states what is delivered, how it is priced, and what it is a bad fit for.
- Cloud Setup & DevOpsInfra as code + runbookSetup typically 1–2 weeks per environment, then handover walkthrough
- Maintenance & Support PlansMonthly health report + proactive updatesOngoing monthly support plan with guaranteed SLA response times
- Managed IT Services24/7 proactive monitoring + automated patching + immutable backupsDiscovery and telemetry onboarding 2 weeks; continuous steady-state operations ongoing
Pairs with
The other tools that answer the same question
These run in your browser, need no signup, and send nothing to us.
HTTP Status Code & Redirect Chain Checker
Follow each real Location header hop by hop, catch redirect loops, and check protocol hops before a migration burns your crawl equity.
Open the toolDNS Record Lookup (A, AAAA, MX, TXT, CNAME, NS)
Query live DNS records for any domain through Google's DNS-over-HTTPS resolver — nine record types on one screen, no rate limits.
Open the toolEmail Authentication (SPF, DKIM & DMARC) Checker
Audit SPF, DKIM and DMARC records in one pass and get a spoofing-protection grade for your sending domain.
Open the toolTELL US ABOUT YOUR PROJECT
Tell Us What to Build, Fix or Modernize
Send a short brief. We reply within 12 hours with clarifying questions and a discovery quote — no retainers, no spam.
What Happens Next
Request a Discovery Quote
Share your goals and timeline. NDA signed first if needed.
12-hour response