Certificate Transparency (CT)
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="proxy.php?url=https%3A%2F%2Fstatuscodefyi.com%2Fiframe%2Fglossary%2Fcertificate-transparency%2F" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://statuscodefyi.com/glossary/certificate-transparency/
Add a dynamic SVG badge to your README or docs.
[](https://statuscodefyi.com/glossary/certificate-transparency/)
Use the native HTML custom element.
A public logging framework (RFC 6962) that requires all publicly trusted TLS certificates to be recorded in one or more append-only CT logs before browsers will accept them. Each log entry produces a Signed Certificate Timestamp (SCT) that browsers verify during the TLS handshake. CT enables domain owners, security researchers, and CAs to detect misissued or fraudulent certificates within hours. Google Chrome has required CT for all new certificates since 2018.