NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED — certificate not logged in Certificate Transparency
Chrome requires publicly trusted certificates to have valid SCTs from CT logs, and this one doesn't.
certificate transparency required ChromeSigned Certificate Timestamp missing Meaning
Issue the certificate from a public CA that embeds SCTs, or attach them via TLS extension/OCSP stapling. Private/internal CAs and old certificates need the Chrome policy CertificateTransparencyEnforcementDisabledForUrls for exceptions.
Common causes
- Certificate lacks embedded SCTs
- Internal CA used for a public site
- Old certificate issued before CT enforcement
- Proxy re-signing without SCTs
- CT log distrusted
⚡ Quick fix
- Reissue from a CT-compliant CA
- Check SCTs:
openssl x509 -text | grep -A3 "Signed Certificate Timestamp" - Use enterprise policy for private CAs only
Detailed fix by platform
Shell
openssl x509 -in cert.pem -noout -text | grep -A4 "SCT"
How to diagnose
- SCTs — Present?
- CA — Public?
- Policy — Needed for internal?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- CORS CORS: Private Network Access preflight blocked (public site calling localhost/intranet)
- Django Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port)
- ERR_SSL_KEY_USAGE_INCOMPATIBLE Chrome: ERR_SSL_KEY_USAGE_INCOMPATIBLE — the certificate's key usage doesn't allow the negotiated cipher
Most viewed in SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- DST Root CA X3 expired (old clients fail) Old clients: certificate has expired — Let's Encrypt chain uses expired DST Root CA X3 (OpenSSL 1.0.x, Android < 7.1.1)
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026