Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Certificate Transparency is a public, append-only log of every TLS certificate issued by a trusted authority. It turns silent mis-issuance into something anyone can detect within hours.

What Is Certificate Transparency?
Before 2013, a certificate authority could issue a certificate for your domain and nobody would know unless they happened to connect to the server using it. Certificate Transparency fixed that by requiring every publicly trusted certificate to be recorded in append-only logs that anyone can read. Mis-issuance is still possible; staying quiet about it is not.
The idea came out of Google’s response to the DigiNotar compromise and was published as RFC 6962, with the updated CT 2.0 specification in RFC 9162. Chrome has required CT for all new publicly trusted certificates since 30 April 2018, and Apple applies a comparable policy, so in practice a certificate without log entries will not be trusted by mainstream browsers.
A CT log is an append-only Merkle hash tree operated by Google, Cloudflare, DigiCert, Let’s Encrypt, and others. When a CA issues a certificate, it submits the certificate — or a precertificate, before final issuance — to several logs. Each log returns a Signed Certificate Timestamp, a promise to include the entry within a defined window, usually 24 hours.
The SCT then travels to the browser in one of three ways: embedded in the certificate as an X.509 extension, delivered in the TLS handshake, or attached to an OCSP response. The browser checks that enough SCTs from qualifying logs are present before trusting the chain.
The Merkle tree structure is what makes the log honest. Because every entry is hashed into a tree whose root is signed and published, a log operator cannot remove or alter an entry retrospectively without producing an inconsistent root, and auditors continually verify that consecutive roots are consistent.
CT works because people watch it. In September 2015 Google engineers found Symantec test certificates for google.com in the logs, which began the chain of events ending in Symantec’s distrust. Organisations routinely discover subdomains they did not know were public, certificates issued by a departed supplier, and typosquatted domains being prepared for phishing campaigns, often before the phishing site goes live.
It also exposes mistakes that would otherwise stay hidden: certificates with invalid characters, internal hostnames leaked into public certificates, and reused private keys across unrelated organisations.
Monitoring costs very little and should be standard practice.
%.example.co.uk to see every certificate issued for your namespace.Combine it with CAA records. CAA tells authorities who may issue; CT tells you who did. Together they close the loop: if a certificate appears from a CA that your CAA record excludes, you have a reportable incident with evidence attached, and the CA is obliged to investigate.
Transparency is symmetrical. Because the logs are public, they are an excellent reconnaissance source, and they are one of the first places a penetration tester or an attacker looks. Request a certificate for uat-payments.internal.example.co.uk and you have published the hostname to the world, along with the fact that a payments system exists and is in testing.
Two mitigations help. Use wildcard certificates for internal or pre-production names so that individual hostnames are not disclosed, accepting the key management trade-off that a wildcard brings. Or issue those certificates from a private certificate authority, which is not logged at all. Do not try to keep a name secret while also asking a public CA to vouch for it.
Our continuous vulnerability scanning services use CT data to track the external estate as it changes, because new certificates are usually the earliest public signal that a new service has gone live.
The next phase is static CT logs, a simpler tiling design adopted by Google and Let’s Encrypt from 2025, which lowers the cost of running and auditing a log. The direction matters because short certificate lifetimes mean far more issuance: when the CA/Browser Forum’s 47-day maximum takes effect in 2029, the volume flowing through the logs will rise sharply, and the architecture has to carry it.
No, it makes mis-issuance detectable. A certificate authority can still issue a certificate it should not have, but the entry appears in public logs within hours, so the domain owner, researchers, and root programmes can see it. Detection has proved powerful in practice, because CAs now face public incident reports and the prospect of distrust.
They will if you obtain the certificate from a publicly trusted CA, even for a host that is not reachable from the internet. Anyone searching crt.sh for your domain will see the name. Use a private CA for internal services, or a wildcard certificate, if hostname disclosure is a concern for you.
Free services such as Cert Spotter and Censys will email you when a certificate matching your domain appears in the logs, and crt.sh offers an API you can poll from your own tooling. Set the alerts at apex and wildcard level, route them to a monitored inbox, and treat an unexpected issuer as an incident.
Browsers do: Chrome, Edge, and Safari enforce CT, and Firefox began enforcement in 2025. Many command line tools, API clients, and embedded devices do not check SCTs at all. That gap matters when the attacker’s target is a machine-to-machine connection rather than a user with a browser.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.