Certificate Transparency Asset Discovery
Every HTTPS certificate is logged publicly — and that log is a goldmine for finding assets you forgot you had. This surfaces a domain's certificates (wildcards included), when they first and last appeared, and the sibling hostnames issued alongside them. A clean way to uncover shadow assets and expansion no inventory captured.
How it uses the graph
Traverses the DNS, TLS layers of the graph, in 4 steps:
How it walks the graph4 steps
01CT certificates
Reading certificates seen in Certificate Transparency…
DNSTLS
02CT observation detail (wildcard + cert count)
CT observation detail (wildcard + cert count)…
DNSTLS
03CT-observed sibling assets under the same apex
CT-observed sibling assets under the same apex…
DNSTLS
04Shared serving footprint of CT siblings (IP → prefix → ASN)
Shared serving footprint of CT siblings (IP → prefix → ASN)…
DNSTLS
Why each step runs
- 01CT certificates. CT certs (incl. wildcards) reveal assets and unexpected issuance.
- 02CT observation detail (wildcard + cert count). Shows each certificate this exact host was seen in, including whether it is a wildcard cert and how many certificates share that observation — detail the anchor's bare cert list omits.
- 03CT-observed sibling assets under the same apex. Finds other hostnames under the same apex domain that were issued certificates — forgotten or sibling assets — and enriches each with its resolving IP, owning ASN and threat verdict.
- 04Shared serving footprint of CT siblings (IP → prefix → ASN). Collapses the CT sibling set to the distinct IP / prefix / ASN it serves from — a single shared IP or ASN across many siblings is the classic shared-hosting / connected-infrastructure tell.