This site can’t be reached

“Chrome says the connection was reset. Other sites work.”

Chrome dinosaur-adjacent error: ERR_CONNECTION_RESET on a specific hostname.

Likely cause

The browser can reach the network, but the TCP session to this host is being reset. Common causes: a local firewall/antivirus HTTPS scan, a stale HTTP/3 (QUIC) path, or a captive DNS cache — not a broken Windows install.

Confidence 74%Windows · Wi-Fi connected

1
Confirm it is site-specific
Open a second tab to https://example.com. If that loads, stay focused on this host rather than repairing Windows networking.
2
Disable QUIC briefly
Go to chrome://flags/#enable-quic, set Experimental QUIC protocol to Disabled, relaunch Chrome, and retry the site.
3
Flush the host cache
In Chrome open chrome://net-internals/#dns and click Clear host cache. Then in Windows Terminal (Admin not required): ipconfig /flushdns.
4
Rule out HTTPS scanning
If you run an antivirus “HTTPS scanning” or “encrypted web” feature, turn it off for a minute and reload. If the site appears, add it as an exception rather than leaving scanning off.

Diagnose my screenshot

← All examples Next example: Where did the display scaling go? →