Browser Error Codes

Connection Refused

The website's server actively rejected the connection. The server is reachable on the network but nothing is listening on the requested port.

Connection Timed Out

The server didn't respond within the time limit. It could be overloaded, unreachable, or a firewall is silently dropping packets.

Connection Timed Out

The TCP connection handshake did not complete within the timeout period. The server is either unreachable or a firewall is blocking the connection silently.

Address Unreachable

The IP address resolved fine but is unreachable from your network. The route to the server is broken — could be routing, firewall, or the server being offline.

Name Not Resolved

DNS lookup failed — the domain name could not be translated to an IP address. Either the domain doesn't exist, DNS is broken, or your internet connection is down.

DNS Probe Finished: NXDOMAIN

The domain name does not exist in DNS (NXDOMAIN = Non-Existent Domain). Your DNS server confirmed the domain has no records.

DNS Probe Finished: No Internet

Chrome detected no internet connection before it could even reach a DNS server. Your device can't reach the network.

Internet Disconnected

Chrome detected no internet connection. Your device's network interface is connected locally but has no internet access.

Network Changed

Your network changed mid-connection — Chrome detected a new IP address or interface switch and aborted the request to avoid mixing data from different networks.

Blocked by Administrator

Group Policy, parental controls, or an enterprise firewall/proxy has blocked access to this site on your device or network.

Empty Response

The server accepted the connection then closed it without sending any data. This usually means a server-side error or crash.

Too Many Redirects

The server kept redirecting you in a loop. Chrome stopped after hitting its redirect limit (usually 20 hops) to prevent an infinite loop.

Cache Miss

A form resubmission is required to reload the page. Chrome loaded this page once from a POST request and needs new data to reload it — it won't re-send the form automatically.

HTTP/2 Protocol Error

The server sent an HTTP/2 response that violated the protocol spec. This is a server-side bug or configuration issue.

SSL Protocol Error

The SSL/TLS handshake failed. The browser and server couldn't agree on an encryption protocol version or cipher suite.

Certificate Authority Invalid

The server's SSL certificate was issued by an authority your browser doesn't trust. This could mean a self-signed cert, an expired root CA, or a MITM attack.

Certificate Date Invalid

The SSL certificate has expired or its validity window hasn't started yet. This blocks the connection to protect against using old, potentially compromised certificates.

Certificate Name Mismatch

The SSL certificate doesn't match the domain you're visiting. For example, the cert is for "example.com" but you're on "www.example.com" and the cert doesn't cover "www".

SSL Version or Cipher Mismatch

Your browser and the server couldn't agree on a mutually supported SSL/TLS version or cipher suite. Often seen on very old or very locked-down servers.

Proxy Connection Failed

Chrome is configured to use a proxy server, but the connection to the proxy failed. The proxy is misconfigured, offline, or blocking the request.