Certificate Transparency Logs and SSL/TLS Discovery
What you'll learn: How to mine public certificate transparency logs to discover subdomains, infrastructure, and organizational certificates without directly scanning targets.
What Are Certificate Transparency Logs?
When a website obtains an SSL/TLS certificate from a certificate authority (CA), that certificate is logged in public Certificate Transparency (CT) logs—massive, searchable databases required by modern browsers for security. Think of CT logs as a permanent public registry of every website certificate ever issued.
For reconnaissance, these logs are goldmines. Each certificate reveals:
- Domain names and subdomains (in the Subject Alternative Name field)
- Organization details (company name, location)
- Infrastructure hints (wildcard certificates, internal naming conventions)
- Historical data (old certificates show infrastructure changes)
Why This Matters for OSINT
Instead of actively probing a target's network (which leaves traces and may be illegal), you query public CT log databases like crt.sh, Censys, or Shodan. This is completely passive—you're reading public records, not touching the target.
Example scenario: A company example.com might have certificates for api.example.com, internal.example.com, staging.example.com—all revealing infrastructure you'd never find in DNS enumeration alone.
The Discovery Process
- Search CT logs by domain or organization name
- Extract all listed domains/subdomains from certificates
- Note patterns (e.g., AWS regions, environment names)
- Cross-reference with other OSINT sources
- Build a complete infrastructure map—passively
CT logs complement techniques like DNS enumeration and Google dorking by revealing domains that may not be publicly linked or indexed.
Key Takeaway:
Certificate Transparency logs provide a passive, legal treasure trove for discovering an organization's web infrastructure, subdomains, and certificate history without ever touching their systems.