Certificate transparency (CT) logs are public, append-only records of every TLS certificate issued by a publicly trusted certificate authority. When an attacker requests a certificate for a lookalike of your domain so their fake site shows a padlock, that certificate shows up in the logs, usually before the site is ever used against anyone. Watching CT logs is one of the earliest warnings you can get.
What certificate transparency is
Certificate transparency was created to catch mis-issued certificates: a certificate authority issuing a certificate for a domain to someone who doesn’t control it. The fix was to make every issuance public. Certificate authorities submit each certificate to independent logs, which anyone can read, and browsers check for proof of logging.
Major browsers, including Chrome and Safari, require publicly trusted certificates to be logged. In practice, that means nearly every certificate on the public internet, legitimate or not, is visible in CT logs within minutes of being issued.
Why attackers end up in the logs
A phishing page without HTTPS triggers browser warnings and looks wrong to anyone paying attention. So attackers get certificates, and free, automated certificate authorities make that easy. A typical staging sequence looks like this:
- Register a lookalike domain such as
acme-login.comoracrne.com. - Request a TLS certificate for it, or for a subdomain like
secure.acme-login.com. The certificate is logged. - Stand up a cloned login page, often from a phishing kit.
- Wait for the domain to age, then send the campaign.
Step 2 is public. The attacker has to announce the domain to the world to get the padlock, and that announcement usually comes days or weeks before step 4.
What a CT log entry tells you
- The domain names on the certificate, including subdomains, which often reveal intent (
login.,billing.,sso.). - When it was issued, which tells you how fresh the infrastructure is.
- Which certificate authority issued it.
A new certificate for sso.acme-support.com on a domain registered three days ago is a very different signal from an old certificate on a parked typo.
The limits of CT monitoring on its own
CT logs are powerful, but they aren’t complete coverage:
- No certificate, no entry. A lookalike domain used only to send email doesn’t need a certificate at all. Business email compromise often works this way.
- Wildcard certificates hide subdomains. A certificate for
*.acme-support.comshows the domain but not the specific subdomain being used. - Volume. Millions of certificates are logged every day. Searching them by hand for your brand name catches exact matches and misses homoglyphs and creative misspellings.
- Context. A log entry tells you a certificate exists. It doesn’t tell you whether the site is live, what it’s hosting, or whether it’s a threat.
That’s why CT monitoring works best alongside newly registered domain monitoring, which catches lookalikes whether or not they ever get a certificate, plus enrichment that tells you what’s actually on each domain.
How to start using CT logs
- Check your own domains first. Free public CT search tools let you look up every certificate issued for your domain. Anything you don’t recognize could mean a forgotten system or a misused account.
- Search your brand name, not just your domain, to catch certificates on combosquats like
acme-billing.com. - Automate it. Manual searches are a snapshot. Attackers stage infrastructure every day, so monitoring needs to be continuous and needs to score similarity, not just match exact strings.
How FirmGuardian uses CT logs
The FirmGuardian platform monitors certificate transparency logs and newly registered domains continuously, scores each potential lookalike for how closely it mimics your brand, and enriches it with registration, certificate, hosting, and screenshot data. You see the threat while it’s being staged, with the context to decide whether it matters.
Related reading: How lookalike domains attack your business and The Anatomy of an Attack.
See what’s being staged against you
Add your domain and see the lookalikes already registered and certified against your brand. Free, no card, about five minutes.