A single “This site can’t be reached” message—or a failed Googlebot fetch—does not prove a small-business website is down for everyone. The problem could be a DNS record, an HTTPS certificate, the host or network path, crawler access, or one visitor’s connection. Check the exact error and compare access across hostnames, devices, and networks before calling it an outage.
How to tell a sitewide outage from a limited failure
Sort each report along four axes: scope (one visitor, one network, a crawler, or many visitors), failure layer (DNS, TLS, host or origin, CDN, or local network), symptom (resolution error, security warning, timeout, refused connection, or HTTP status), and reproducibility (continuous or intermittent). These distinctions help direct troubleshooting; they do not diagnose a particular site without tests of its domain, configuration, logs, and visitor access.
As an Amazon Associate I earn from qualifying purchases.
Start by recording the full URL, time, browser, exact error text, and whether the person reporting it can reproduce the failure. Then compare the same page from another device and another network. A report from one visitor establishes that their attempt failed—not that the site is unavailable to everyone.
Five common cases that can look like a dead website
1. The hostname does not resolve
Errors such as DNS_PROBE_POSSIBLE, DNS_PROBE_FINISHED_NXDOMAIN, err_name_not_resolved, “This site can’t be reached,” or “Can’t find the server” can appear when a hostname has no usable DNS answer. Causes include a misspelled domain, a missing record, or an incorrect record for the apex domain or www. A local network or DNS resolver problem can produce a similar experience for one visitor.
#1 Best Overall
Check the spelling and test the apex domain and www hostname separately, along with any subdomain in the failing URL. Confirm with the domain or DNS provider that each relevant record points to the intended origin; if DNS is managed by a hosting partner, make changes through that provider. Cloudflare’s documentation explains that “DNS_PROBE_POSSIBLE means that the resolver could not find DNS records for the requested hostname” (Cloudflare DNS_PROBE_POSSIBLE troubleshooting; page last updated 2026-04-16). Its guidance also covers general DNS issues and NXDOMAIN errors.
2. HTTPS is blocked by a certificate problem
A website’s server can be running while a browser blocks access or displays a security warning because its certificate is expired, untrusted, corrupted, not yet valid, or does not cover the requested hostname. Compare the exact hostname in the failing URL with the certificate’s covered names. Ask the hosting provider or certificate administrator to correct the issue; do not tell customers to bypass a security warning. Google’s SSL certificate guidance describes how certificate problems affect browser access and why the hostname must match.
3. The host or origin is unavailable, overloaded, or slow to respond
A timeout, refused connection, 5xx response, or very slow dynamic page can point to a server or network-path problem. Check the hosting or CDN provider’s service status, the server logs, and the response for the exact URL. Compare results from a separate network or location before describing the failure as universal.
Google lists server downtime or load, DNS routing, excessive response time, and crawler blocking among possible causes of an unreachable URL. Search Console’s possible categories also include 5xx responses, DNS issues, unreachable robots.txt, network-unreachable, failed connection, no response, truncated response, and connection refused. See Google’s URL-unreachable errors and its general hosting guidance. The latter dates to 2011, so use it for these general failure modes rather than current product-specific instructions.
4. Search Console or Googlebot reports a failed fetch
A crawler’s failed attempt is evidence about that fetch, not automatic proof that human visitors cannot open the page. Google lists DNS errors, timeouts, network errors, inaccessible robots.txt, and a host blocking Googlebot as possible causes. Open the page in a normal browser, inspect the specific Search Console error, and check crawler access separately.
Google says its Search Status Dashboard is intended to report issues affecting many sites or users; a problem not listed there may be isolated or limited in scope. The dashboard is useful context, not a test of one site’s availability. See Google’s URL-unreachable guidance and its Search Status Dashboard guide.
5. Only some visitors see an intermittent TLS or connection error
If a failure appears intermittently or only on certain networks or devices, compare visitor-side DNS, network conditions, device and browser compatibility, and protocol behavior before announcing a global outage. Cloudflare describes HTTP/3 as one possible cause of intermittent SSL protocol errors when some networks or devices mishandle UDP traffic. That is a troubleshooting branch, not a diagnosis without more evidence. Record the exact message—such as ERR_SSL_PROTOCOL_ERROR, “Secure Connection Failed,” or Safari’s “can’t open the page because it couldn’t establish a secure connection to the server”—and which visitors are affected. See Cloudflare’s SSL protocol troubleshooting guidance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A practical diagnostic sequence
- Capture the report: record the exact URL, timestamp, browser, error text, and whether the reporter can reproduce the failure.
- Check the hostname: verify the URL spelling, then compare the apex domain and
wwwhostname. Include the relevant subdomain if the failing URL uses one. - Compare access: try another device and another network. Note whether the result is consistent, intermittent, or limited to one visitor or network.
- Verify DNS: ask the domain or DNS provider to confirm the records and intended origin. If a hosting partner manages DNS, coordinate changes through it.
- Check HTTPS: confirm the certificate is valid and covers the exact hostname. Route certificate warnings to the host or certificate administrator.
- Inspect hosting and delivery: check provider status, server logs, and the response for the exact URL. Distinguish an origin failure from a provider or edge incident where the available evidence permits.
- Investigate crawler reports separately: inspect the specific Search Console fetch error and compare Googlebot reachability with human access.
- Describe only what the checks establish: for example, “one visitor is affected,” “Googlebot could not fetch this URL,” or “multiple networks are receiving a 5xx response.”
How to report the problem accurately
Match the wording to the evidence. A DNS error on one device is not proof the whole website has disappeared; a crawler error is not proof that customers are blocked; and a failure affecting several networks is stronger evidence of a broader problem than one failed attempt. State which URL failed, who or what could not reach it, and whether the result reproduced elsewhere. For ongoing visibility after an incident is resolved, a website uptime monitor can help flag future interruptions.
Quick Recap
Best Value
- Easy To Track Your Finances: HAUTOCO horizontal accounting ledger book keeps you on top of your expenses and income! Help you keep your money organized, spend well, and set and achieve financial goals
- Practical Design: The accounting book is PU leather hardcover, with double-wire spiral binding that allows it to lay flat 360°; 100gsm thick paper, comes with an elastic band, pen loop, bookmarks, and 2 large pockets for storing loose notes
- Plenty of Space: The expense tracking notebook measures 10.78 x 8'' and has 120 pages with 3000 lines of entries giving you enough space to record each of your transactions
- Manage Your Finances Effectively: Undated accounting books with number, date, description, account, payment or deposit amount, and total balance. You will be able to easily analyze your financial activities and quickly prepare accurate financial statements
- Ideal For Small Business or Personal Use: An accounting log journal can track your business or personal financial status. With a clear record of transactions, you can find unnecessary expenses or fraudulent charges
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
