No websites load: separate connection failure from a browser problem
A practical check sequence for blank tabs, connection errors, and browsers that appear offline.
If every site fails at once, clearing cookies is rarely the first useful action. Your device may have lost connectivity, DNS resolution may be failing, a VPN may be intercepting traffic, or the browser itself may be stuck. Test one variable at a time to avoid making the situation worse. The purpose of this workflow is to identify the broken layer—network, device, browser, or security policy—without disabling protection permanently.
Check the network before the browser. Do not enter passwords on unverified pages or bypass browser security warnings.
Check whether the device can reach anything
Try another app that requires the internet, then visit a different website in another browser. If the whole device appears offline, inspect Wi-Fi or cable connection, airplane mode, captive-portal prompts, and router indicators. Do not rely only on the Wi-Fi icon: it proves a local connection, not working internet access. If possible, use a phone hotspot as a controlled alternative; the result distinguishes the usual network from the device.
Look for pattern in the error message
A name-resolution error suggests DNS or the domain address, while a certificate warning indicates a trust or interception question. A timeout is broader and can reflect network loss, filtering, or a service that does not respond. Record the wording before taking action. If you are using a managed school or work device, do not alter security agents or proxy settings without the administrator.
Restart the smallest component first
Close and reopen the affected tab, then browser, before restarting the computer. If multiple devices on the same network fail, a router reboot may be appropriate when you manage it. Avoid factory-resetting a router or deleting network configuration without knowing login credentials and provider requirements. After each step, test a known safe site to learn whether connectivity returned.
Review VPN and security software cautiously
A VPN outage or security product configuration can affect all browsing. Check the official status or settings of your own service. If you temporarily disconnect an optional VPN to test, avoid using an untrusted public network during the experiment and restore the connection after the test. A corporate VPN may be required for internal sites; ask support rather than bypassing a mandatory connection.
Escalate using useful evidence
Collect the time, browser and operating system, exact errors, affected websites, whether other devices fail, and whether switching networks changes the result. This gives an ISP or IT team actionable context. Never send screenshots containing passwords, private domains, session tokens, or full account identifiers. If only one browser fails while others work, continue with its extensions and browser-specific troubleshooting.
How this looks in practice
A laptop shows “no internet” errors in Chrome, Safari, and a mail app while two phones on the same Wi-Fi are fine. That combination points toward the laptop, not a specific browser. Rejoining Wi-Fi and checking device-level network settings is more relevant than deleting Chrome history. If the laptop works on a hotspot but not home Wi-Fi, the problem shifts toward that network or its configuration.
Your short checklist
- Test an unrelated networked app.
- Compare another browser.
- Compare another device on the same network.
- Record error wording.
- Restart one layer at a time.
- Do not bypass managed security controls.
Official documentation and verification
These publisher links support the browser behavior and instructions discussed above. BrowserSignal’s example cases are illustrative scenarios, not claims of hands-on vendor testing.
- Google Chrome Help — Fix connection and loading errors
- Microsoft Support — What to do if Edge is not working
Menu labels, software versions and policies can change. If a device is managed by an employer or school, follow its instructions. Avoid sharing passwords, tokens, or private account details with support forums.
Use the interactive Pathfinder, then record what actually fixed the issue.