How to Add Trusted Websites in Chrome, Edge, and Firefox

Modern browsers do not have one universal “trusted websites” switch. In Chrome, Edge, and Firefox, the safest approach is to allow only the specific permission or compatibility exception a site needs. Windows still has a legacy Trusted sites security zone, but Microsoft Edge uses Windows Security Zones only for limited decisions and Internet Explorer mode—not as a general allowlist for normal browsing.

Choose the right kind of exception

Before changing anything, identify what the browser is actually blocking. Granting a narrow permission is safer than weakening browser-wide protection.

How to add a trusted website in Google Chrome

Chrome lets you override individual site permissions. Google documents this under Change site settings permissions.

1. Open Chrome and visit the website.
2. Select the site information icon to the left of the address.
3. Select Site settings.
4. Change only the permission the site needs, such as camera, microphone, notifications, pop-ups, or insecure content.
5. Return to the page and reload it.

Allow insecure content only when necessary

If an HTTPS page depends on an HTTP image, frame, or other mixed content, Chrome can allow Insecure content for that site. This is not the same as declaring the whole website safe, and it does not remove Safe Browsing or certificate checks. Use it only when you understand why the site requires mixed content.

How to allow a site in Microsoft Edge

Edge also uses per-site permissions. Microsoft notes that most Edge permissions are configured per site rather than through the old Windows security-zone model. See Microsoft’s per-site configuration guidance.

1. Open the website in Edge.
2. Select the lock, information, or warning icon beside the address.
3. Select Permissions for this site.
4. Allow only the capability you need, then reload the page.

You can also review permission categories in Settings > Privacy, search, and services > Site permissions > All permissions. Menu names can move slightly between Edge releases, but per-site permission controls remain the preferred approach.

How to trust a site in Firefox

Firefox does not provide a single desktop “Trusted Sites” list. For normal permissions, use the site’s permissions controls or Page Info. Mozilla explains these controls in its Site Permissions panel documentation.

If a legitimate site is broken because Firefox Enhanced Tracking Protection blocks required resources, click the shield beside the address and turn Enhanced Tracking Protection off for that site. Mozilla recommends this as a site-specific troubleshooting step; it does not make certificate or malware warnings safe. You can turn protection back on at any time. See Mozilla’s Enhanced Tracking Protection guide.

What about Windows Trusted Sites?

The Internet Options > Security > Trusted sites zone still exists in Windows for legacy and enterprise scenarios. To add a site, press Windows + R, enter inetcpl.cpl, open the Security tab, choose Trusted sites, select Sites, and add the address. Keep the HTTPS requirement enabled whenever possible.

Do not expect this Windows list to override normal Chrome, Firefox, or Edge security warnings. Microsoft states that modern Edge relies mainly on its own per-site settings and uses Security Zones only for a few decisions such as integrated authentication, certain download behavior, and Internet Explorer mode.

Do not whitelist certificate or malware warnings

If Chrome shows Your connection is not private, Google recommends resolving the certificate, network, or device problem rather than installing certificates yourself. See Chrome’s error-message guidance. Likewise, a red phishing or malware warning is a Safe Browsing alert; Google advises against visiting the site. Microsoft gives similar guidance for sites flagged by Defender SmartScreen in Edge security documentation.

For an internal company site with a private certificate authority, the correct fix is usually for IT to deploy the organization’s trusted root certificate and configure the browser or device by policy. Avoid broad security exceptions when a narrow permission or proper certificate configuration will solve the problem.