How to find the certificates logged for your domain in Certificate Transparency logs
Certificate Transparency (CT) logs are public, append-only records of the certificates that certificate authorities issue. Chrome requires publicly trusted TLS certificates to meet its CT policy, so certificates meant to work in Chrome end up in the logs. That makes CT the quickest way to see what has been issued for your domain.
Search the logs
- Open crt.sh, a free search site for CT logs.
- Search for
example.comto see certificates for that exact name, or%.example.comto include subdomains (%is the wildcard). - Each row shows when the certificate was logged, its "Not Before" and "Not After" dates, the names it covers and the issuer.
You will often see two entries per certificate: a precertificate and the final certificate are both logged. crt.sh is a free service; it is suited to occasional manual searches rather than frequent automated polling.
What to look for
- Hostnames you do not recognise: old staging sites, campaign landing pages, mail, VPN or vendor-hosted subdomains. Each one with a certificate is something that can expire.
- Issuers you do not use: a certificate from an unexpected certificate authority is worth asking about.
- Many certificates in a short time for the same names, which can point to a renewal loop.
- Certificates valid for many months next to short-lived ones. Long-lived certificates are often renewed by hand.
Limit who can issue: CAA records
A CAA DNS record (defined in RFC 8659) names the certificate authorities allowed to issue for your domain, for example:
example.com. CAA 0 issue "letsencrypt.org"
List every CA you actually use before adding one, or renewals with an unlisted CA will fail.
What CT logs do not show
- Certificates from private or internal certificate authorities.
- Which certificate a server is presenting: a renewed certificate that was never installed still appears in the logs.
- Domain registration expiry, which is a separate date (see how to check a domain's expiration date).
Doing this for many domains?
Lindenkit queries CT logs through the Cert Spotter API by SSLMate for every domain you add, keeps the latest certificate per hostname, and flags the ones that look manually renewed.
Lindenkit Certificates lists the certificates logged in public Certificate Transparency logs for each domain you add, tracks the domain's registration expiry through RDAP, and emails you 30, 14, 7 and 1 days before either lapses. It reads public data and does not connect to your servers, so it shows the latest certificate per CT logs, which may not be the one a server presents. Free for up to 10 certificates; Base US$29/month for 100.
Sources
- Chrome's Certificate Transparency policy (checked 22 November 2026)
- RFC 8659: DNS Certification Authority Authorization (CAA) Resource Record (checked 22 November 2026)
- crt.sh certificate search (checked 22 November 2026)