HTTP vs DNS vs SSL Failures: How to Read Any Uptime Result Like a Pro

Server reachable ≠ page working. Learn to tell HTTP errors, DNS failures, TLS problems and timeouts apart from any uptime checker result.

The 10-second mental model

DNS = “does this name exist?”. TCP/TLS = “can I reach and trust it?”. HTTP = “what did the app say?”. Our result names exactly which layer failed.

Reading any result like a pro

No status code + DNS → domain/resolver. No code + timeout → firewall/overload. Code 4xx → reachable, page-level. Code 5xx → reachable, origin sick. TLS flag → reachable, identity broken.

What to do next

DNS: check spelling/WHOIS. TLS: check clock/cert. 5xx: wait + recheck, then contact owner with timestamp + status code. Slow (>3s): treat as Issues — visitors bounce like it's down.

Test it now: run a live check → then re-read your result with this guide. Each check + guide read is another pageview that funds the free tool.

FAQ

Server reachable but page failing — is that “down”?

For visitors, often yes. Technically the site is up at network level; the page/origin errors. We label it Issues to stay honest.

Why show response time?

TTFB separates slow-origin (fix hosting) from slow-network (fix route/CDN). Both cost revenue.