What Is Certificate Transparency Monitoring?
2026-11-06 · 7 min read · By the DomainGuard team
The short version
Certificate Transparency (CT) monitoring is the practice of watching the public CT logs — the append-only records of every TLS certificate issued on the internet — for certificates you did not request: for your domain, for lookalike domains impersonating you, and for subdomains you deliberately keep unused as tripwires. Anyone can request a certificate for your domain; the log is where you find out. A certificate naming your brand that your team never ordered is one of the earliest possible warnings of a phishing site being built, because the attacker needs that certificate before the clone can show a padlock. Mechanics as implemented in DomainGuard's CT watch, November 2026.
What is a Certificate Transparency log?
Every publicly trusted certificate authority publishes each certificate it issues to CT logs as a condition of browsers trusting it. The result is a permanent, searchable, public record: which CA issued the certificate, for which names, and when. You can search it yourself right now — crt.sh is the best-known public interface, and searching your own domain takes ten seconds. Certificates your team ordered are expected. The monitoring discipline is everything after that first look: new certificates, watched continuously, matched against what you actually requested.
What does CT monitoring actually catch?
Rogue certificates for your own domain. If a CA is tricked or compromised into issuing a certificate for your real domain to someone else, that certificate appears in the logs. In October 2026, reports described hackers forging valid TLS certificates for Google domains (The Register, October 7) — which is why Google publicly recommends that all domain owners monitor CT logs.
Certificates for lookalike domains. A typosquat is just a registered name until it has hosting and a certificate. The certificate is a staging signal: the clone is being made padlock-ready. Watching CT for your variant families (the seven in our lookalike check guide) catches impersonation builds before the phishing emails go out.
Your own shadow infrastructure. Forgotten test subdomains, a vendor who ordered a certificate on your behalf years ago, a staging host that was never decommissioned — CT logs show every name you have ever certified, including the ones your current team has never heard of. Each is attack surface you can retire.
Canary trips. The sharpest signal of all, covered next.
What is a canary subdomain?
A canary subdomain is a subdomain you create deliberately and then never use: no website, no mail, no legitimate service ever touches it. Because nothing legitimate will ever request a certificate for it, any certificate issued for that name is hostile or erroneous by definition — there is no innocent explanation to sort through. DomainGuard's scanner runs exactly this tripwire: it polls CT logs for your canary subdomains, and any certificate found is raised as a critical finding. It is the same principle as a canary token in a document or a honeypot on a network: a signal with a zero false-positive rate, because the tripwire guards a door nobody legitimate ever opens.
Setting one up is three steps: pick an unguessable-but-plausible subdomain name under your domain, add it to your monitoring, and then never use it for anything. The moment a certificate names it, someone is building infrastructure under your brand without you.
How is this different from CAA records?
CAA and CT are the prevention/detection pair, and our CAA record guide covers the first half. A CAA record tells the world's CAs which of them may issue for your domain at all — prevention, set once in DNS. CT monitoring assumes prevention sometimes fails (a CA that ignores CAA, a compromised CA, a certificate for a lookalike where your CAA does not apply) and gives you detection. You want both: CAA narrows who can issue; CT tells you the moment anyone does. Neither replaces the other, and neither costs anything to start.
How do you start monitoring, practically?
Today, free, ten minutes: search your domain on crt.sh and eyeball the issuer column for anything your team does not recognise; do the same for your two or three most plausible lookalike variants. Then publish a CAA record if you have not (ten of the thirteen agency domains in our October teardown had none).
Continuously: the logs grow by millions of certificates; the discipline is a standing query, not a recurring calendar reminder someone will eventually skip. DomainGuard's free report includes your domain's CT picture, and the paid watch keeps the query — including the canary tripwire — running permanently. Our practice guide, Certificate Transparency: Catch Rogue Certificates, goes deeper on reading what a suspicious certificate means once you have found one.
FAQ
What is Certificate Transparency in simple terms?
A public, permanent record of every TLS certificate issued on the internet. Certificate authorities must publish each certificate to these logs for browsers to trust it, which means anyone — including you — can search for every certificate ever issued for a domain.
Can someone really get a certificate for my domain without my permission?
Yes, if a certificate authority is tricked, compromised, or careless — domain-validated certificates only prove control at the moment of the check, and attackers have forged valid certificates even for major brands' domains, as reported in October 2026. CAA records reduce who may issue; CT monitoring catches the issuances that happen anyway.
What is a canary subdomain?
A subdomain you create and deliberately never use. Since nothing legitimate ever needs a certificate for it, any certificate issued for that name is a critical warning with no innocent explanation. DomainGuard's scanner polls CT logs for canary subdomains and raises any hit as a critical finding.
How do I check my domain's certificates for free?
Search your domain on crt.sh — the public CT log interface. Look for issuers and dates your team does not recognise. DomainGuard's free report includes the same picture for your domain alongside its lookalike variants.
Does CT monitoring stop phishing sites?
Not by itself — it detects the certificate an impersonator needs before their clone can show a padlock, which is one of the earliest staging signals available. Acting on the signal is the takedown ladder: blocklists, hosting, registrar. Detection early is what makes those filings fast.