website browser errors
This Site Can’t Be Reached
Compare your connection with a server-side website check, then separate one-site problems from wider browsing failures.
Check Site and Connection ↓Measurements describe the endpoint and test shown. HTTP timing is not network-layer packet loss or a direct measurement of your router, WiFi radio or ISP.
Your guided check
Observe. Compare. Take the next step.
Read the smaller error code
This site can’t be reached is a broad message. ERR_NAME_NOT_RESOLVED, ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_RESET describe different failures reported by your browser. Select the code you see, not a suspected cause.
Compare one site with other sites
If unrelated sites open, a complete loss of internet access is less likely. Check spelling and compare the affected site on mobile data or another browser.
Interpret a server check in its own location
A server reports its own DNS, TLS or HTTP failure class. It does not reproduce your browser’s DNS, VPN, account or regional path. A 403 or 500 proves an HTTP response arrived, not that the site works normally.
Frequently asked questions
Should I ignore a certificate warning?
No. Do not bypass certificate checks or enter credentials on a connection marked unsafe.
Why can your server reach a site that I cannot?
The resolver, network route, region and browser environment can differ.