Certificate Transparency Log Growth Report 2026

Q2 2026 public issuance share by CA (%)
source: Cloudflare Radar Certificate Transparency, Q2 2026
SSL CA usage share of websites (%)
source: W3Techs, 2026-10
By 2026, Certificate Transparency (CT) logs have accumulated more than 13 billion publicly trusted TLS (still commonly called SSL) certificates, and the ledger keeps growing at roughly 33% per year (Google CT dashboard, Q2 2026). For domain owners, CT is a free early-warning system: search your domain and you can surface any certificate you did not request. This report walks through the 2026 data and the monitoring steps you can take today.
What CT is and why browsers mandate it
CT is a set of public, append-only logs that record every publicly trusted TLS certificate. Chrome has rejected certificates without a valid Signed Certificate Timestamp (SCT) since April 2018, and Apple then enforced its own CT policy in Safari (October 2018) — a separate rule from Chromium's, not an extension of it. A CA can no longer quietly issue a certificate for your domain — every issuance must land in a public log that anyone can audit.
2026 log scale: past 13 billion and still accelerating
Google's official CT dashboard counted more than 13 billion cumulative issuance events by the end of Q2 2026, up about 33% year over year (Google Transparency Report, Q2 2026); the third-party index crt.sh holds roughly 15 billion entries, including full copies of every log and duplicates (verified via CyberSecTools, 2026-06). The core driver is issuance volume: short-lived automated certificates now dominate the market, and the shorter the certificate, the more issuance records the same website produces each year.
The 2026 issuance landscape: more than half from Let's Encrypt
Cloudflare Radar's CT data shows Let's Encrypt accounted for 56.7% of all public issuance in Q2 2026, followed by Google Trust Services at 13.4%, Sectigo/ZeroSSL at 11.8% and Amazon Trust Services rising to 6.5% (Cloudflare Radar, Q2 2026). Nearly all of these certificates are issued automatically via ACME, mostly with 90-day lifetimes, and every one lands in the logs.
The website-side view: CA usage is highly concentrated
Looking at which CAs websites actually use, the W3Techs survey of October 2026 shows Let's Encrypt used by 64.4% of all websites (67.4% market share among sites with an identifiable CA), GlobalSign 22.1%, Sectigo 4.6%, GoDaddy 3.6% and DigiCert 1.6% (W3Techs, 2026-11-02). The dominance of free, short-lived DV certificates is the most direct source of CT log growth.
Policy changes: shorter validity plus tighter SCT delivery
CA/Browser Forum ballot SC-081v3 set a new maximum-validity schedule: 200 days from 2026-03-15, dropping to 100 days on 2027-03-15 and 47 days on 2029-03-15. Meanwhile Chrome 148 (2026-05-05) removed the option to deliver SCTs inside OCSP responses — SCTs must now be embedded in the certificate or conveyed via a TLS extension. Together these changes mean CT log write volume will keep growing for years.
Step 1: Search your domain
Use this site's CT Log Search (which queries crt.sh and Cert Spotter) to list every historical issuance for your domain.
Step 2: Review every result
Entries from your hosting platform or certificate provider are legitimate; anything you did not request deserves scrutiny — inspect the issuer, SANs and validity with the Certificate Decoder. If you find a certificate from an unknown CA, check your DNS and ACME account security immediately.
Step 3: Set up daily monitoring for high-value domains
High-value domains should get daily log searches or an alerting service such as Cert Spotter; every other site should be checked after any server compromise or domain transfer, then quarterly. CT is free, public and immediate — the cheapest domain-asset monitoring available.
Troubleshooting checklist
| Symptom | Likely cause | What to do |
|---|---|---|
| Certificates you never requested appear in the logs | Automatic issuance by your hosting platform/CDN (Cloudflare, Vercel, etc.) | Confirm the issuer with the Certificate Decoder; no action needed if it is your own platform |
| An unknown CA issued a certificate for your domain | Unauthorized issuance attempt or compromised ACME account | Rotate account credentials, audit DNS, revoke the certificate if necessary |
| Unfamiliar internal subdomains appear in certificates | Staging environments or temporary hostnames issued publicly | CT records cannot be deleted; retire unused subdomains and stop issuing for them |
| crt.sh queries time out | crt.sh overload or indexing lag | Retry later, or use Cert Spotter / this site's CT tool |
| Browser reports a missing or invalid SCT | SCT not embedded or stapled, or still delivered via OCSP | Upgrade your ACME client/server; Chrome 148 no longer accepts OCSP-delivered SCTs |
| A wildcard certificate shows up in the logs | Wildcard issuance must be logged too | Verify the issuer is your own automation platform to rule out abuse |
Take action now: check your certificate and SCT status with the SSL Checker, search your domain with the CT Log Search, and use the CSR Generator when you need a new certificate. For systematic TLS hardening, see the SSL certificate guide.
Related articles: Certificate Transparency Logs: SCTs, Monitoring, crt.sh, Let's Encrypt Market Share and E5/E6 Chain Transition Report 2026, HTTPS Adoption and TLS Deployment Report 2026
FAQ
Can certificates be hidden from CT?
No. No publicly browser-trusted certificate can be issued without SCTs. Some CAs offer logging-delayed or private issuance for special cases, but such certificates are not trusted by mainstream browsers.
How often should I check my domain?
High-value domains should be monitored continuously (daily log searches). Everyone else should check after any account or server compromise and after domain transfers, then fold checks into a quarterly review.
Do CT logs expose my internal hostnames?
Yes. Every hostname in the SANs of a public certificate is public, and expired records are retained permanently. That is why "search first, issue later" has become a standard reconnaissance step for attackers — subdomains you want to keep private should never appear in public certificates.
Free SSL/TLS tools
Verify and inspect your certificates in seconds.
Related Certificate Info
Learn more about choosing and buying certificates.