Forum Discussion

Bart Sipes's avatar
Bart Sipes
Copper Contributor
Apr 09, 2019

NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

I'm getting a privacy error attempting to connect to a corporate intranet page. The specific error is NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

 

I have the domain added to the certificate transparency URL exclusion list as is specified in https://www.chromium.org/administrators/policy-list-3#CertificateTransparencyEnforcementDisabledForUrls which works fine with Google Chrome. However it does not appear that it's working with Edge.

 

I'm using Version 74.1.96.24 (Official build) dev (64-bit).

3 Replies

Sort By
  • malysina's avatar
    malysina
    Copper Contributor
    Jul 16, 2025

    The error NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED is mainly caused by issues related to website SSL certificates. This error occurs when a website’s SSL certificate fails to comply with the Certificate Transparency policy enforced by browsers such as Chrome. When Chrome is unable to validate an SSL certificate on a website owing to a lack of transparency in the certificate’s issuing, this error appears. It is a security mechanism put in place to ensure that a trustworthy entity has issued the SSL certificate and that it has not been tampered with. There are n number of reasons for the error to be occured which are as follows:-

    1) Certificate not added to transparency log

    2) Incorrectly installed SSL certificate

    3) Corrupted SSL certificate

    4) Expired SSL Certificate

    There are many different ways to fix the error which you need to  understand in detail and helps to solve it. Further I am attaching a resource for error solution:- https://cheapsslweb.com/blog/err-certificate-transparency-error-in-chrome/. Hope it helps!

  • Eric_Lawrence's avatar
    Eric_Lawrence
    Icon for Microsoft rankMicrosoft
    Apr 10, 2019

    Bart Sipes Thanks for the report; please file this issue using the Feedback button for tracking.

     

    The problem you're encountering at this time is that Edge's policies are not read from Chrome's policy location.

     

    I am curious to learn more details of your issue, however-- What is the hostname and the CA in use? (Feel free to email me directly ericlaw@). It's unexpected that many environments will hit this issue. In most cases like this, the CA root certificate used by the enterprise is considered a "legacy" root and thus CT is not enforced. In contrast, public CAs working under the baseline requirements should be issuing with CT and will not issue to "dotless" hostnames. Rare exceptions include Microsoft (which has a CA that is both trusted by default and issues our intranet certificates).

Resources