Few browser messages are more frustrating than typing in an address, hitting Enter, and being told this site can’t be reached — just an error page and a small code underneath. The good news is that this message is a symptom rather than a diagnosis: it appears when your browser tried to connect and failed somewhere along the way, and the cause is usually ordinary — a hiccup in your connection, a DNS problem, stale browser data, or the website itself being offline. This guide explains what the message means and the standard checks that resolve it in most cases.
What “this site can’t be reached” actually means
When you enter a web address, several things happen in sequence. Your browser asks the Domain Name System (DNS) to translate the address into its server’s numeric IP address, connects, negotiates security if the site uses HTTPS, and requests the page. The “this site can’t be reached” message means the process broke down before the page could be delivered — most often at the looking-up or connecting stage.
Because it is a general message, Chrome adds a more specific code beneath it, and that code is your best clue. ERR_NAME_NOT_RESOLVED means the DNS lookup failed, so your browser could not find the server’s address. ERR_CONNECTION_TIMED_OUT means the server was found but did not respond in time. ERR_CONNECTION_REFUSED means something actively rejected the connection. Whichever code you see, the checks below are the right starting point for reaching any website.
Start with the basic connection checks
Before changing any settings, rule out the simple explanations. Confirm that other websites load. If nothing loads anywhere, the problem is your connection: check Wi-Fi or the cable, toggle airplane mode on a phone, and restart your router or modem (off for thirty seconds, then back on).
If only one website fails, try it on a second device and, if possible, a different connection — a phone on mobile data instead of home Wi-Fi. If the site fails on every device and network, it is down at the source. If it works elsewhere, the fault lies with your device, browser, or network. Similar messages can mean different things — see the 1337x error code 1006 explainer.
Clear the DNS cache and check your DNS settings
DNS is a frequent hidden cause, because your device and browser remember previous lookups. If a website has moved servers and your stored answer is out of date, your browser keeps trying an address that no longer works. Flushing the DNS cache forces fresh lookups: on Windows, from the Command Prompt with ipconfig /flushdns; on a Mac, from the Terminal. Restarting the browser usually clears its own DNS cache too.
If flushing does not help, your provider’s DNS servers may be slow or faulty. Many people switch their device or router to a well-known public DNS service in the network settings; write down your original settings first so you can restore them.
Rule out your browser: cache, extensions, and settings
A browser can also block itself. Corrupted cached files or cookies occasionally stop a specific site from loading even though the connection is fine. Test this by opening the site in a private or incognito window, which ignores stored data and most extensions. If the page loads there, clear that site’s cookies and cached files in your normal window, then disable extensions one at a time.
Also check the system-level connection settings. If your device is configured to use a proxy server or network tool that is no longer running, every request is sent to a dead end. On a device managed by a workplace or school, those settings may be controlled by IT policy, and changing them is a job for their support team.
When the website itself is down
Sometimes every check at your end comes back clean, because the fault is not yours. Websites go offline for maintenance, server failures, expired hosting, or configuration mistakes, and then the only honest fix is waiting. A status-checking service can confirm this by testing the address from its own servers. Do not chase unofficial workarounds that ask you to disable security features or install unknown software — a temporary outage is not worth a permanent risk. Regional availability is another reason an address may not load, as explained in why some sites are unavailable in certain countries.
Frequently Asked Questions
Why does one site say “can’t be reached” while others work?
Because the failure is specific to that address: the site’s server may be down, its DNS records may have changed while your cached answer is stale, or stored data for that site in your browser is corrupted. Flushing DNS, testing in a private window, and trying a second network are the most useful first checks.
What does ERR_NAME_NOT_RESOLVED mean?
It means the DNS lookup failed: your browser asked for the numeric address behind the site’s name and got no usable answer. Causes include a mistyped address, stale cached DNS data, a faulty DNS server, or DNS records still updating at the site’s end. Restarting your router, flushing the DNS cache, and trying a different DNS service are the standard fixes.
Can my internet provider cause this error?
Yes. Provider outages, faulty DNS servers, and routing problems can all produce this message even when your home equipment is fine. The clue is timing: if several sites fail at once, or neighbours on the same provider report the same trouble, it is provider-side.
Is it safe to change my DNS settings?
Changing DNS is a normal, reversible setting, and using a reputable public DNS service is a common troubleshooting step. It only changes which directory service translates addresses for you; it does not remove security warnings or make unsafe sites safe. Note your previous settings so you can switch back.
Conclusion
“This site can’t be reached” tells you the journey between your browser and a website broke down, not why — but the pattern points to the cause. Nothing loading anywhere means your connection; one site failing everywhere means the website; one site failing only for you means your DNS, stored data, or network settings. Work through the checks in order — restart the connection, test another device or network, flush DNS, test in a private window, review extensions — and in most cases the page will load again. When the site itself is down, the correct fix is patience, not risky workarounds.
