How to Build an Attack-Surface Inventory from Certificate Transparency
A domain inventory maintained in a spreadsheet starts drifting as soon as another team creates a staging host or replaces a certificate. I built a small Python job that discovers names from Certificate Transparency, records what the domain exposes today, and reports only the changes worth reviewing.
The Domain Intelligence Suite provides the WHOIS, DNS, TLS, and certificate-derived subdomain data. Python turns that response into a durable inventory rather than another JSON file nobody checks.
Treat Certificate Transparency as discovery, not proof
Public certificate authorities submit certificates to Certificate Transparency logs. Searching those logs can reveal names such as api.example.com, staging.example.com, and wildcard entries that were included in issued certificates.
