downinspector
downinspector
Guides / Add a trusted site

How to add a security exception for trusted sites in your browser

Browsers block sites with certificate problems, unsafe content warnings or blocked downloads. Sometimes the site is one you know and trust, such as a router page or an internal tool. Here is how to allow it safely, and when not to.

Published


First, find out why the browser is blocking the site

Browsers block sites for several different reasons, and the right response depends on which one you see. A certificate warning means the encrypted connection cannot be verified. A red “dangerous site” page means the address is on a list of known phishing or malware sites. A blocked download means the file itself looks risky. Only the first case is a candidate for a personal exception, and only when you are sure who runs the site.

Before allowing anything, run the site through the checker on the homepage. It reports the state of the site’s certificate as seen from a server outside your network. If the certificate is valid there and invalid in your browser, the problem is local: a wrong clock, outdated software or a security tool that inspects your traffic.

Quick fixes before adding an exception

  1. Check the date and time

    Set your device to update its clock automatically, then reload the page.

  2. Update the browser and system

    Outdated systems do not recognise newer certificate authorities.

  3. Try a private window

    This rules out extensions and stale cached data.

  4. Pause security software that scans web traffic

    Some antivirus and parental control tools replace certificates and cause warnings.

  5. Use the right address

    Typing the full address with the exact name the certificate covers fixes many mismatches on routers and devices.

Google Chrome and Microsoft Edge

On the “Your connection is not private” page, select Advanced, then the link to continue to the site, which Chrome marks as unsafe. The browser remembers that choice for the rest of the session. To allow a trusted site to run something the browser blocks by default, such as pop-ups or downloads, open the padlock or site information icon next to the address, go to Site settings and change the permission for that site only. Edge offers the same options under its own site permissions.

Mozilla Firefox

On the warning page, select Advanced and then Accept the Risk and Continue. Firefox stores a permanent exception for that certificate. You can review and remove stored exceptions in Settings → Privacy & Security → Certificates → View Certificates, on the Servers tab.

Safari on Mac

When Safari shows a warning, select Show Details and then the link to visit the website, and confirm. Safari may ask for your Mac password to trust the certificate. For a device you manage, such as a home server, the more permanent option is to add its certificate to the Keychain Access app and set it to always trust, which affects only your Mac.

Windows trusted sites

Some older company tools still rely on the Trusted Sites zone in Windows Internet Options. Open Control Panel → Internet Options → Security → Trusted sites → Sites, add the address and confirm. Modern browsers largely ignore this setting, so use it only when an internal tool’s instructions ask for it.

Reading the error code on the warning page

The small code under the warning names the exact fault, and it decides whether an exception makes sense at all. In Chrome and Edge, NET::ERR_CERT_DATE_INVALID points to an expired certificate or a wrong clock, NET::ERR_CERT_COMMON_NAME_INVALID means the certificate was issued for a different name, and NET::ERR_CERT_AUTHORITY_INVALID means no trusted authority signed it, which is normal for a router or a home NAS with a self-signed certificate. Firefox uses its own codes, such as SEC_ERROR_UNKNOWN_ISSUER and SSL_ERROR_BAD_CERT_DOMAIN, for the same situations.

Some sites leave no way past the warning at all. When a site has told the browser to accept only secure connections, a policy called HSTS, Chrome and Firefox remove the continue link. That is deliberate. A bank or webmail provider that shows such a page cannot be bypassed, and it should not be.

A page that fails without any certificate warning, saying instead that the site cannot be reached, has a different cause. The guide to browser connection errors covers those cases, from DNS failures to blocked connections.

When you should not bypass a warning

Never add an exception for a bank, shop, email service, social network or any site where you sign in, when the warning appears unexpectedly. Large public sites have valid certificates; a warning on them usually means a network problem or, in the worst case, an attempt to intercept your connection. Close the page, switch to another network and check the site again.

Questions

Is it safe to add a security exception?

Only for sites you control or fully trust, such as your own router, a printer or a company tool on your network. On public websites, a certificate warning can mean that someone is intercepting the connection, so do not bypass it there.

Why does my browser say the connection is not private?

The site's security certificate could not be verified. It may have expired, belong to a different name, or be self-signed. It can also appear when your device's date and time are wrong.

Can a wrong clock cause certificate errors?

Yes. Certificates are valid for a set period. If the device's date is far off, every certificate looks invalid. Set the date and time to update automatically and reload the page.

How do I remove an exception later?

In Firefox, open the certificate settings and delete the stored exception. In Chrome and Edge, the temporary allowance ends when you close the browser; site permissions can be reset in the site settings for that address.

Why does a site work on my phone but show a warning on my laptop?

The laptop may have a wrong clock, an outdated system, or security software that inspects connections. Compare the date and time first, then try another browser on the laptop.

Can I check whether a site's certificate is valid without the browser?

Yes. The checker on the homepage reports the TLS certificate state of any public site. If it shows the certificate as valid while your browser warns, the problem is on your device or network.