Opens in a new tab

NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED: the certificate was not publicly logged

Publicly trusted certificates must be recorded in public Certificate Transparency logs, and carry proof of it. This certificate did not, so Chrome — and Firefox since 2025 — refuses it. The fix is a replacement certificate from the certificate authority.

Your connection is not private
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
How one other client words the same error

Firefox

Error code: MOZILLA_PKIX_ERROR_INSUFFICIENT_CERTIFICATE_TRANSPARENCY — “Firefox doesn’t trust example.com because it couldn’t prove it meets public certificate transparency requirements.”
ErrorNET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
Usually fixed byThe website
ChromeRequired since Chrome 68 (2018) for certificates issued after 30 April 2018
FirefoxEnforced since Firefox 135 (February 2025); Android since 145
Applies toPublicly trusted certificates, not private or company CAs

Check the certificate a site serves

Enter the site’s domain: we connect the way a browser does and show the certificate, its chain and the TLS versions it offers.

What it means

Certificate Transparency makes every publicly trusted certificate visible in public logs, so a certificate issued for your domain without your knowledge can be spotted. Browsers require proof — signed timestamps from several independent logs — delivered in the certificate or during the handshake. A certificate without enough of them is refused.

Why it happens

  • The certificate authority did not log the certificate, or logged it in too few logs.
  • The server strips or does not deliver timestamps it was meant to send in the handshake.
  • A certificate from an authority that is not publicly trusted used where a public one is expected.

How to fix it

  1. Contact the certificate authority for a replacement certificate that meets the Certificate Transparency policy — Chrome’s own guidance for site owners.
  2. Install it with its full chain and reload.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Hear about it before your visitors do

Add your domain and we check its certificate on every scan and email you before it expires, and when it changes or stops being valid — along with DNS, email and security headers. Free for your first domain.

Create a free account