Certificate Transparency
A certificate security mechanism proposed by Google in 2013 and standardized as RFC 6962, requiring CAs to record all issued certificates in publicly auditable log servers. This enables domain owners and the security community to monitor and detect unauthorized certificate issuance.
Timeline (last 90 days)
Certificate Transparency (CT) logs are public SSL/TLS certificate logging systems; researchers can discover newly launched subdomains by querying CT logs, even if those subdomains do not appear in DNS records.
The author built CT Lookup, which outputs certificate transparency data as JSON and includes a watchlist that can catch certificates issued for your domain that you did not apply for.
Certificate Transparency (CT) is a public auditing mechanism that requires certificate authorities to record every TLS certificate they issue in public, append-only, verifiable logs.
All publicly trusted CAs must submit certificate information to at least one CT log when issuing a certificate, so when a new website applies for an SSL certificate, its domain information appears in the public log.
All Facts (4)
Certificate Transparency (CT) logs are public SSL/TLS certificate logging systems; researchers can discover newly launched subdomains by querying CT logs, even if those subdomains do not appear in DNS records.
50%UnverifiedCertificate Transparency (CT) is a public auditing mechanism that requires certificate authorities to record every TLS certificate they issue in public, append-only, verifiable logs.
50%UnverifiedAll publicly trusted CAs must submit certificate information to at least one CT log when issuing a certificate, so when a new website applies for an SSL certificate, its domain information appears in the public log.
50%UnverifiedThe author built CT Lookup, which outputs certificate transparency data as JSON and includes a watchlist that can catch certificates issued for your domain that you did not apply for.
50%