← Back to Learning Hub

DNS • Intermediate • 6 min read

Certificate Transparency Logs: Monitor Certs Issued for Your Domain

What Certificate Transparency logs are, how an SCT proves a certificate was logged, and how to monitor CT feeds to catch certs mis-issued for your domain.

Certificate Transparency is a public, append-only logging system that records almost every publicly trusted TLS certificate at the moment it is issued. Its purpose is detection: if a certificate authority issues a certificate for your domain, whether you asked for it or not, that issuance lands in logs you can watch. This guide explains what CT logs are, how a Signed Certificate Timestamp proves a certificate was logged, why modern browsers refuse certificates that lack one, and how to monitor CT feeds so you catch a mis-issued or forgotten certificate for your domain early instead of learning about it from an outage or an attacker.

Why Certificate Transparency exists

Before CT, a certificate authority could issue a certificate for any domain and no one outside that CA would necessarily know. A compromised or careless CA could sign a certificate for your bank, your mail server, or your company, and the first sign of trouble might be an active attack. Certificate Transparency, first specified in RFC 6962 and updated by the CT version 2 specification in RFC 9162, fixes the blind spot by requiring issuance to be published to public logs. It does not prevent a bad certificate from being created, but it guarantees that creating one leaves a visible, permanent record that domain owners and researchers can audit.

CT pairs naturally with CAA, which controls which CAs are allowed to issue for your domain in the first place. CAA is the lock on the door; CT is the camera that records everyone who walks through it. Our guide on CAA records and which CAs can issue your certificates covers the preventive half of that pair.

How CT logs work

A CT log is a cryptographically verifiable, append-only ledger run by a log operator. When a CA is about to issue a certificate, it submits a precertificate to one or more logs. Each log returns a Signed Certificate Timestamp, or SCT, which is a signed promise that the log has recorded the entry and will include it in its public tree within a defined maximum delay. The log's structure is a Merkle tree, so anyone can verify that an entry is present and that the log has never removed or altered an earlier entry. That append-only property is what makes the record trustworthy: a log operator cannot quietly delete evidence of a bad issuance.

What an SCT proves and why browsers demand one

An SCT travels with the certificate so a browser can confirm the certificate was logged without contacting the log itself. The CA can embed SCTs directly in the certificate, deliver them in the TLS handshake through a stapled extension, or send them in an OCSP response. As of November 2026, major browsers including Chrome and Safari require publicly trusted certificates to carry valid SCTs, typically from more than one independent log, and will reject a certificate that does not. That requirement is what gives CT its teeth: a CA that skips logging produces certificates that simply do not work in mainstream browsers, so logging is effectively mandatory for the public web.

Reading a certificate's SCTs

You can see the SCTs embedded in a live certificate without any special tooling. The table below shows the fields you will encounter and what each one tells you.

FieldWhat it isWhy it matters
Log IDIdentifier of the CT log that issued the SCTConfirms which independent logs recorded the certificate
TimestampWhen the log accepted the entryFixes the issuance moment in a tamper-evident way
SignatureThe log's signature over the entryLets a browser verify the SCT without calling the log
SCT countNumber of SCTs presentBrowsers expect several from distinct logs

Run openssl x509 -noout -text on a fetched certificate and look for the CT Precertificate SCTs section to see these values. A live external check reports the same certificate fields, as described in our guide on how to check an SSL certificate issuer, chain, expiry, and SAN.

Setting up monitoring for your domain

The real value of CT for a domain owner is monitoring. Because every issuance is logged publicly, you can subscribe to a feed and be alerted whenever a new certificate appears for your names.

  1. Decide which names to watch, including the apex, common subdomains, and any wildcard patterns you use.
  2. Choose a monitor: a free CT search front end for ad hoc lookups, or a service that emails you on new issuance for continuous coverage.
  3. Set the alert scope to your registrable domain so you catch subdomains you did not expect, not just exact matches.
  4. When an alert fires, confirm you or a known service requested the certificate; match the issuing CA against your CAA policy.
  5. Investigate anything unexpected: an unknown CA, a subdomain you never provisioned, or a certificate issued outside your normal renewal window.
  6. Keep a short record of which CAs and services legitimately issue for you, so routine renewals do not trigger false alarms.

You can sanity-check the certificate your own server presents, and its chain and expiry, with the Valla DNS SSL checker while you set your monitoring scope.

Limits of Certificate Transparency

CT is detection, not prevention. A logged certificate is still a valid certificate; CT only guarantees you can find out about it. There is also a defined window between issuance and public appearance in the tree, so monitoring catches problems quickly but not instantly. Finally, certificates that are never meant for public trust, such as those on a private internal CA, are not logged, which is correct behavior but means CT tells you nothing about purely internal PKI. Treat CT as the audit layer that sits on top of CAA and good renewal hygiene, not as a standalone defense.

Frequently asked questions

Does Certificate Transparency stop a bad certificate from being issued?

No. CT makes issuance public and permanent, but it does not block a CA from signing a certificate. To restrict which CAs may issue for your domain at all, publish a CAA record. Use CT alongside CAA so you both limit and observe issuance.

Will my site break if its certificate is not in CT logs?

Very likely. As of November 2026, Chrome and Safari require publicly trusted certificates to carry valid SCTs and reject those that do not. Any certificate from a reputable public CA is logged automatically, so this only bites with misconfigured or private certificates served to public browsers.

What is a Signed Certificate Timestamp?

An SCT is a signed receipt from a CT log confirming it has recorded a certificate and will publish it within a set time. Browsers check SCTs to confirm a certificate was logged without having to query the log directly during the handshake.

How soon will a new certificate show up in CT monitoring?

Usually within minutes to a few hours, bounded by each log's maximum merge delay. That is fast enough to catch an unexpected issuance well before most attacks could play out, though it is not truly instantaneous.

Can I use CT to find certificates I forgot about?

Yes, and it is one of the best uses. Searching CT logs for your domain surfaces every publicly logged certificate ever issued for it, including old or shadow-IT certificates you no longer track, which is useful for inventory and cleanup.

Certificate Transparency turns certificate issuance from an invisible event into an auditable one, so a mis-issued certificate for your domain becomes something you can catch rather than something that catches you. Pair CT monitoring with a CAA policy, and verify your own live certificate anytime on the SSL checker.

Troubleshooting box

If results look inconsistent, compare authoritative nameservers first, then recursive resolvers by region. Capture snapshots every 10 minutes for deterministic incident timelines.

Try VallaDNS free →

Intermediate • 6 min

How to Find a DNS Record's TTL (Current Value)

Find the TTL currently set on a DNS record: read the TTL column in dig and nslookup, tell the authoritative TTL from a resolver's countdown, and confirm a change.

Intermediate • 7 min

How to Check If Nameservers Have Propagated

Nameserver changes live at the parent TLD and follow the registry NS TTL, not your zone. Check the parent delegation and confirm the new NS set worldwide.