CT Log (Certificate Transparency Log)
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%2Fct-log%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/ct-log/Add a dynamic SVG badge to your README or docs.
[](https://statuscodefyi.com/glossary/ct-log/)Use the native HTML custom element.
An append-only, cryptographically verifiable log of all TLS certificates submitted to the Certificate Transparency ecosystem. CT logs use a Merkle tree structure so that any inclusion or tampering can be independently verified by log monitors. When a CA submits a certificate to a CT log, the log returns a Signed Certificate Timestamp (SCT) that browsers check during the TLS handshake. Public CT logs are operated by Google (Argon, Xenon), Cloudflare (Nimbus), DigiCert, and others. Domain owners can monitor CT logs for unauthorised certificate issuance using services like crt.sh.