Websites Won't Open but Messaging Works? Diagnose Browser, DNS and HTTPS
A messaging app can keep an existing connection while a browser must perform new DNS, proxy, TCP and TLS steps. Partial connectivity therefore does not prove that the whole network is healthy.
Define the exact failure scope
Record the full error code rather than only 'page cannot be reached.' Try three unrelated reputable sites, another page on the same domain, a private window and another supported browser. One domain failing suggests its service or DNS; one browser failing suggests browser state; every browser failing suggests system or network configuration.
Compare another device on the same Wi-Fi. If every device fails, check router and upstream connectivity. If the site opens on cellular but not home internet, preserve the result; it may indicate household filtering, DNS, IPv6 or an ISP route rather than a broken phone.
Check date, time and HTTPS safely
HTTPS certificates are validated against the device clock. Set date, time and time zone automatically, then restart the browser. A clock far in the past or future can make many secure sites fail while an already-connected app keeps working.
Do not click through certificate warnings for banking, email, shopping or account pages. Inspect whether antivirus HTTPS scanning, a workplace proxy or captive portal is presenting a different certificate. On public Wi-Fi, open the network's documented sign-in page rather than entering credentials into an unexpected warning page.
Separate browser profile and extension problems
A private window can bypass some cache, cookies and extensions, but not every policy. If it works, disable extensions one at a time, clear data only for the affected site and update the browser. Preserve passwords and synced data before resetting a profile.
If all browsers fail, do not repeatedly reinstall Chrome. Check the operating system proxy, hosts file changes made by trusted software, firewall policy and DNS. Unknown modifications can be a security concern; scan with an updated trusted security product rather than downloading random repair tools.
Test DNS, VPN, proxy and secure DNS
Flush the local DNS cache and renew the address using supported operating-system controls. Compare browser secure DNS with system DNS, and pause VPN, proxy or content filtering only when policy permits. Change one item at a time so the cause remains visible.
A reputable public DNS is a temporary comparison, not a universal repair. Record original settings and use provider-verified addresses. If IP connectivity also fails, changing DNS will not restore the router, WAN or Wi-Fi link.
Handle IPv4 and IPv6 evidence correctly
A site may prefer IPv6 while a router or ISP has a broken IPv6 path. Compare several destinations and devices and inspect whether the failure is limited to one address family. Do not permanently disable IPv6 based on one page; update router firmware or report the faulty path.
Path MTU, filtering and proxy issues can also allow small app traffic while large HTTPS pages stall. A wired comparison, another ISP and timestamps help an ISP or IT team distinguish these from DNS.
Escalate without destroying useful settings
Contact the website owner when one site fails across independent networks and official status confirms an issue. Contact the ISP when all household devices and wired tests fail to open multiple sites. Provide exact errors, times, DNS choice and comparison networks.
On work or school devices, filtering and proxy configuration may be intentional. Do not bypass controls, remove management profiles or publish internal details. Give IT the browser, URL category, error, time and connection type. Avoid router factory reset unless settings and ISP credentials are backed up.
Frequently asked questions
Does messaging working mean the internet is fine?
No. The app may keep an existing session or use different endpoints while new browser connections fail at DNS, proxy or TLS.
Should I reinstall Chrome?
Only after another browser proves the issue is limited to Chrome and simpler profile, cache or extension checks fail.
Why do only HTTPS sites fail?
Incorrect time, certificate interception, a captive portal, proxy, antivirus scanning or TLS policy can affect HTTPS specifically.
Should I turn off IPv6?
Not permanently as a first response. Confirm an IPv6-only failure across destinations, then fix or report the router or ISP path.
Confirm basic connectivity and latency before resetting the browser or router.
Test internet connection