What is Certificate Transparency?
Certificate Transparency (CT) is an open framework in which every TLS certificate issued by a publicly trusted CA is recorded in public, append-only logs. Anyone can read the logs, and anyone can watch them for certificates that name their own domains. Google engineers designed it after the 2011 DigiNotar breach, in which fraudulent certificates for major sites were issued without anyone outside the CA knowing until they were used to intercept traffic. The original specification is RFC 6962, published in 2013. CT doesn't stop a CA from issuing a bad certificate; it makes sure the certificate can't stay hidden.
How CT works
- Before issuing, the CA submits a precertificate, a copy of the certificate carrying a poison extension that stops it from being used, to several independent logs.
- Each log returns a signed certificate timestamp (SCT), its signed promise to add the certificate within a maximum merge delay, typically 24 hours.
- The CA embeds the SCTs in the final certificate. They can also be delivered during the TLS handshake or in a stapled OCSP response.
- Browsers check for valid SCTs from enough distinct logs. Chrome has required them for newly issued public certificates since 2018, and Apple platforms enforce a similar policy.
Each log is built as a Merkle tree, so it can prove that a given certificate is included and that it has only added entries, never edited or removed old ones. Independent monitors and auditors check those proofs. Running openssl x509 -noout -text on a public certificate shows the embedded evidence under a heading such as CT Precertificate SCTs, with each log's ID, a timestamp and the log's signature.
Monitoring CT logs for your domains
For defenders, CT's value is detection. A security team can subscribe to a CT monitoring service, or query a CT search tool, for every certificate issued for its domains and subdomains. An unexpected certificate might mean a team ordered one without telling anyone, a vendor acted without approval, or an attacker persuaded a CA to misissue. CT has exposed real misissuance: in 2015 Google found precertificates for its own domains that Symantec staff had issued without authorization, which led Google to require Symantec to log all of its certificates, and later problems ended with browsers distrusting Symantec's certificate authority business in 2018. Teams also watch the logs for lookalike domains, because phishing sites routinely obtain free certificates for names close to a real brand.
The other side: CT as an attacker's map
Because the logs are public, they help attackers too. Every hostname placed in a public certificate, including staging servers, VPN portals and unannounced products, can be enumerated from CT data during passive reconnaissance, and penetration testers use the same technique. Wildcard certificates reveal less, since only the wildcard name is logged. Certificates from an internal enterprise CA aren't logged at all, which is one reason internal hostnames belong on internal certificates.
Certificate Transparency vs. CAA vs. pinning vs. revocation
CAA DNS records tell CAs which of them may issue for a domain, a preventive check made at issuance. Certificate pinning has a client reject unexpected certificates at connection time. Certificate Transparency is detective: it records issuance so problems can be found afterward. Revocation through CRLs or OCSP is how a misissued certificate is then cancelled, so a domain owner who finds a rogue certificate in the logs asks the issuing CA to revoke it.
Certificate Transparency on the CompTIA Security+ exam
Certificate Transparency is taught with third-party certificates under SY0-801 objective 1.3, the cryptographic solutions objective, and CT logs reappear as a public intelligence source under objective 2.1 and as a reconnaissance source for penetration tests under objective 5.5. Wording such as "detect certificates issued for the company's domains without its knowledge" points to monitoring CT logs. "An attacker listed the company's internal-sounding subdomains without scanning its network" points to CT logs used for passive reconnaissance. Distractors include CRLs and OCSP, which report revocation rather than issuance, and CAA records, which restrict issuance but don't record it.