Certificate Transparency monitoring: find certificates issued for your domain
Certificate Transparency logs are public. Learn how to search them for your domains, spot unexpected certificates, and lock down issuance with CAA records.
· 6 min read · By the Spot Downtime team
Checking that your own certificate has not expired is one job. Checking that nobody else has obtained a certificate for your domain is another. Certificate Transparency (CT) gives you a way to do the second one, because public certificate authorities record the certificates they issue in public, append-only logs that anyone can read.
What Certificate Transparency is
CT is a system of public logs. When a certificate authority (CA) issues a certificate, it submits it to one or more logs and receives a signed proof, called a Signed Certificate Timestamp (SCT), which is embedded in the certificate. Major browsers expect publicly trusted certificates to carry SCTs, so certificates that skip the logs generally do not work in them.
The result is that almost every publicly trusted certificate for your hostnames ends up somewhere you can search. That includes certificates you did not request.
Why you would watch the logs
- Mis-issuance. A CA that makes a mistake, or is tricked by an attacker, may issue a certificate for your domain. The log is where you see it.
- Forgotten services. Teams create certificates for staging hosts, test environments and vendors. The logs show hostnames you may have forgotten you had.
- Dangling DNS. A certificate issued for a subdomain that points at a decommissioned service is a warning sign worth investigating.
- Unauthorized third parties. A vendor or an employee may have requested a certificate you did not approve.
Hostnames in CT logs are public. Names in a certificate, including internal-looking ones, are visible to everyone, so avoid putting sensitive hostnames in publicly trusted certificates.
Search the logs by hand
The simplest tool is a web search interface over the logs, such as crt.sh. You can search for a domain and its subdomains and see each certificate, its issuer and its validity dates. It also offers a JSON output you can script:
# All certificates for example.com and its subdomains
curl -s 'https://crt.sh/?q=%25.example.com&output=json' \
| jq -r '.[] | [.not_before, .issuer_name, .name_value] | @tsv' \
| sort -r | head -20The %25 is a URL-encoded % wildcard. Public search services can be slow or rate limited, so use them for occasional checks and not for tight polling loops.
What to look for
- An issuer you do not use. If you only ever use one or two CAs, a third one stands out.
- Hostnames you do not recognize, especially look-alike names and subdomains no one has set up.
- Certificates issued at times when no one on your team requested one.
- Unusual bursts: many certificates for the same name in a short time can point to a misconfigured automation loop. That can also hit CA rate limits; see Let's Encrypt renewal failed.
Get alerts instead of searching by hand
Manual searches go stale. Several free and paid services watch the logs for you and send an email when a new certificate appears for a domain you register. Certificate authorities and security vendors offer such monitors, and some cloud providers include them. Pick one, register your apex domains, and decide who receives the email. The alert is only useful if someone reads it and knows what normal looks like.
If you prefer to run your own, you can poll a search service on a schedule and compare the result to an allow list of expected issuers and hostnames:
#!/bin/sh
# Print certificates for the domain whose issuer is not on the expected list
curl -s 'https://crt.sh/?q=%25.example.com&output=json' \
| jq -r '.[] | select(.issuer_name | test("Let.s Encrypt|Amazon") | not)
| [.not_before, .issuer_name, .name_value] | @tsv'Run it once a day from cron. If it prints anything, treat that as a lead to check. Remember that a silent cron job can fail without anyone noticing, so cover it with a heartbeat. See Cron job silent failures.
Limit who can issue: CAA records
Watching the logs tells you after the fact. A CAA DNS record tells CAs, before issuance, which of them may issue for your domain. Compliant CAs must check it and refuse if they are not listed.
example.com. IN CAA 0 issue "letsencrypt.org"
example.com. IN CAA 0 iodef "mailto:[email protected]"CAA does not replace monitoring. It only constrains CAs that honor it, and an attacker who controls your DNS can edit it. The two controls work together. The full details are in DNS CAA records.
What to do when you find an unexpected certificate
- Identify the hostname and issuer, and ask the likely owners internally whether they requested it.
- Check whether the hostname resolves, and where it points. A dangling record may let someone else serve content under your name.
- If it is not legitimate, report it to the issuing CA and ask for revocation. CAs publish an abuse or problem report channel.
- Review DNS access and the accounts that can change records or validate domains with your CAs.
- Add or tighten CAA records and remove stale DNS entries.
Revocation is not instant
Pair CT watching with expiry monitoring
CT monitoring answers "who has certificates for my names?" Expiry monitoring answers "will my own certificate still work next week?" You want both. Spot Downtime's SSL monitoring is included with HTTPS checks and warns you before your own certificate expires; it does not search CT logs, so use a separate CT watcher for that. For lead times that make sense, see SSL expiry alert lead times.
SSL checkerCheck the certificate your server presents right now: issuer, validity dates and chain.Get new guides by email
Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.
Keep reading
- SSL · TroubleshootingCertificate pinning and rotation: how to renew without breaking your appsPinned certificates turn a routine renewal into an outage for mobile apps and API clients. How to pin the public key, plan backup pins and rotate safely.November 9, 2026 · 7 min read
- SSL · TroubleshootingHSTS explained: how to enable it, and how to undo it when it locks you outWhat the Strict-Transport-Security header does, how to roll it out safely, why browsers show an error with no bypass button, and how to remove HSTS or the preload list.November 7, 2026 · 7 min read