Certificate Transparency Logs
What you'll learn: How Certificate Transparency logs provide a public, verifiable record of every certificate issued by Certificate Authorities.
The Problem CT Logs Solve
Certificate Authorities can issue certificates for any domain—but what if a CA mistakenly (or maliciously) issues a fraudulent certificate for your domain? Without transparency, you'd never know an imposter certificate exists until it's used in an attack. Certificate Transparency (CT) creates a public audit trail.
How CT Logs Work
CT logs are append-only public ledgers that record every issued certificate. Think of them like a blockchain for SSL/TLS certificates—once a certificate is added, it cannot be removed or altered, only new entries can be appended.
The technical foundation is a Merkle tree structure. Each certificate added to the log becomes a "leaf" in the tree. The tree's nodes are cryptographic hashes that chain together, making it mathematically impossible to tamper with old entries without detection. Any change would break the hash chain all the way to the root.
Signed Certificate Timestamps (SCTs)
When a CA submits a certificate to a CT log, the log returns a Signed Certificate Timestamp (SCT)—a cryptographic promise that the certificate will be added within a maximum merge delay (usually 24 hours). Browsers can check for SCTs to verify the certificate is logged.
Public Auditability
Anyone can download and audit CT logs. Domain owners can monitor logs for unexpected certificates issued for their domains. Security researchers scan for misissued certificates. This transparency deters misbehaving CAs and enables rapid detection of compromise.
Key Takeaway: Certificate Transparency logs use append-only Merkle trees to create a public, tamper-proof record of all issued certificates, enabling domain owners and the community to audit and detect fraudulent certificates through Signed Certificate Timestamps.