Skip to content

Fix untrusted site error on Chrome

If you’re encountering untrusted site errors on Chrome, it can be frustrating. Let’s explore some ways to fix this issue.

Understanding “Not Secure” Warnings Across Browsers

When you see a “Not Secure” warning in your browser, it means the website you are trying to access does not have a valid SSL certificate. This can put your personal information at risk. To fix this error on Chrome, ensure you are visiting reputable websites with a secure connection.

To resolve the untrusted site error on Chrome, avoid entering any personal information on the site and consider using a VPN for added security. Additionally, clear your browsing data and cookies regularly to prevent any security issues from arising. If the warning persists, contact the website administrator to address the SSL certificate problem. By taking these precautions, you can protect yourself from potential security threats online.

The Role and Limitations of chrome-untrusted://

The chrome-untrusted:// protocol is used by Google Chrome to block access to potentially harmful websites. It serves as a warning to users that the site they are trying to access may not be secure. However, this feature has its limitations and may sometimes block legitimate websites by mistake.

If you encounter the chrome-untrusted:// error, try clearing your browser cache and cookies. This can help resolve issues with false positives. Additionally, check for any browser extensions that may be causing the error and disable them temporarily. If the issue persists, consider updating your browser to the latest version.

Ensuring Secure Connections via HTTPS

Padlock icon with https in the address bar

Step Description
1 Ensure the website is using HTTPS instead of HTTP.
2 Check the SSL certificate of the website to ensure it is valid.
3 Update your browser to the latest version.
4 Clear your browser cache and cookies.
5 Disable any browser extensions that may be causing the error.
6 Verify that your system date and time are correct.

Handling Mixed Content and SSL/TLS Issues

Issue Description Solution
Mixed Content When a webpage served over HTTPS also includes resources (such as images, scripts, or stylesheets) that are served over HTTP. Ensure all resources are served over HTTPS or use protocol-relative URLs.
SSL/TLS Certificate Issue When the site’s SSL/TLS certificate is not trusted by the browser, leading to the “Your connection is not private” error. Install a valid SSL/TLS certificate from a trusted Certificate Authority (CA) and make sure it is correctly configured.
Outdated TLS Protocol When the site is using an outdated TLS protocol version that is no longer secure. Upgrade to a newer, more secure TLS protocol version (e.g., TLS 1.2 or higher).


Why does my Chrome say every website is not secure?

Your Chrome may be saying that every website is not secure because it is displaying a warning for sites that do not support HTTPS. This warning indicates that the connection to the website is not encrypted and could potentially be compromised. It is recommended not to enter any private or personal information on these pages and to avoid using the site if possible.

How do I force Chrome to trust a website?

To force Chrome to trust a website, you can add the site to the list of Trusted Sites in the browser settings. This can be done by clicking on Settings, scrolling to the bottom, clicking on Show Advanced Settings, then navigating to Change proxy settings under Network. From there, click on the Security tab, select the Trusted Sites icon, click on Sites, enter the URL of the Trusted Site, click Add, then click Close and OK.

Why does every website say your connection is not private?

Every website says your connection is not private because your browser is unable to verify a Secure Sockets Layer (SSL) certificate, which is crucial for ensuring security.

How do you solve your connection to this site is not secure?

Your connection to this site is not secure can be solved by taking steps such as installing an SSL Certificate, forcing an HTTPS connection, reinstalling the SSL Certificate, resetting the SSL Cache and clearing browser cache, turning off QUIC Protocol Support, and checking the date and time settings.

Was this article helpful?