CT Log Search
Search certificate transparency logs to discover subdomains and issued certificates.
About CT Log Search
Searches Certificate Transparency logs for certificates issued to a domain, surfacing subdomains that have had a TLS certificate issued for them — including ones that were never publicly linked from anywhere. Since 2018, virtually all publicly trusted certificate authorities are required to log every certificate they issue to public CT logs, which means any subdomain that's ever gotten a valid cert leaves a permanent, searchable record. Queries certspotter.com as the primary source with a crt.sh fallback for reliability.
A hit in this search only proves a certificate was issued at some point — the subdomain, and even the certificate itself, may no longer be active or valid by the time you see the result.
What is CT?
Related Tools
What Certificate Transparency is
Every certificate from a publicly trusted CA is written to public, append-only logs. Browsers such as Chrome and Safari reject certificates that lack proof of logging. The logs exist so domain owners can spot certificates they didn't request, but they also form a public list of every name that ever had a certificate.
This tool queries the certspotter.com index first and falls back to crt.sh.
What to do with the results
- Map your attack surface: forgotten staging, VPN or admin hosts show up here, and attackers read the same logs. Retire what you don't need.
- Spot unauthorized issuance: a certificate from a CA you don't use deserves a look. Restrict issuance with a CAA record and check it with the DNS Lookup.
- Find dangling DNS: a name that still has a CNAME to a deleted cloud resource can be taken over. Resolve each discovered name and remove records that point nowhere.
Limits
- Wildcard certificates appear as
*.example.com, which hides the actual host names behind them. - Private and internal CAs are not logged, so internal names never appear.
- A listed name may no longer exist in DNS, and an expired certificate proves nothing about today.
Avoid putting internal or confidential host names into public certificates: once logged, they are public forever.