What Does Certificate Transparency Reveal About Lookalike Domains?
Published 2026-11-14 ยท Reviewed 2026-11-14 ยท By the Ingenious AI team
The short answer
Certificate Transparency (CT) is the public log of issued certificates โ and a lookalike that wants a padlock must appear in it. TakedownCoop searches CT for names containing your brand, adds lookalike domains the generator missed as CT discoveries (priority 35), and filters out shared certificates carrying unrelated names so the evidence only ever names your brand.
What is Certificate Transparency evidence?
Certificate Transparency is the system of public, append-only logs in which certificate authorities record the certificates they issue. Any site that wants browsers to trust its HTTPS connection leaves a CT record โ including impersonator sites, which is what makes the logs a detection source as well as a trust mechanism.
What is Certificate Transparency evidence?
Certificate Transparency is the system of public, append-only logs in which certificate authorities record the certificates they issue. Any site that wants browsers to trust its HTTPS connection leaves a CT record โ including impersonator sites, which is what makes the logs a detection source as well as a trust mechanism.
Detection starts with the free scan on TakedownCoop's home page. From your one genuine domain, the scanner builds the candidate set an impersonator would plausibly register โ typosquats made by deleting, transposing, duplicating or substituting letters, homoglyph lookalikes, affix combinations, and TLD swaps โ and tests each candidate against live DNS. That order matters for Certificate Transparency evidence: generation first, evidence second, and nothing is called a hit until DNS or a certificate log says it is real.
How the scan ranks and records it
The results are ranked, not dumped. The scanner's own priority scores put a resolving lookalike with a certificate at 90 and one without at 80, registered-but-dormant names at 50 or 40 depending on whether a certificate exists, and CT-only discoveries at 35 or 30. Certificate Transparency evidence is filtered for relevance โ shared certificates carrying unrelated names are not treated as evidence against your brand โ and any check that could not be performed is reported as exactly that, never converted into a reassuring claim.
The padlock leaves a paper trail
An impersonator faces a dilemma the logs exploit: a fake shop without HTTPS warns every visitor's browser, but a fake shop with HTTPS is written into public logs at the moment the certificate issues โ often before the site itself is finished. TakedownCoop's CT fetch uses the public logs aggregated through crt.sh and records how many names it checked, and if the sources fail or answer with an error, the scan says so instead of silently returning nothing.
The filtering is as important as the search. Shared and SAN certificates carry many unrelated names, so the scan keeps only names that actually contain the brand string, and treats those as evidence. Names that survive the filter but were never in the generated candidate set are added as CT-only discoveries at priority 35 (30 when the record stands alone) โ lower than live hits because a certificate alone is preparation, not yet an attack, but far too significant to discard.
A worked example, end to end
A fictional hotel, Casa Miramonte at casamiramonte.com, scans clean on generated candidates โ then the CT results add one discovery: miramonte-booking.com, seen only in the logs, priority 35, not yet resolving. The hotel puts it on monitoring rather than filing. Eleven days later the monitor's re-scan finds it resolving with a booking page, priority 90, and the registrar and host packets are filed with the original CT record showing exactly when the certificate โ and the intent โ first appeared.
Turning evidence into a filing
Evidence only helps if it arrives in the shape the channel expects. TakedownCoop's packet generator produces one packet per channel โ registrar, host, Meta, Google Ads, marketplace, app store โ each with that channel's own subject line and filing checklist, built on the same evidence block: genuine brand, lookalike domain, detection method, DNS and CT evidence, and priority. Packets are a Pro feature ($49/mo; Agency $99/mo covers multiple client brands), and they are prepared for the brand owner or their authorised agent to file.
- Read the CT section of every scan โ discoveries there bypassed the candidate generator
- Do not file CT-only names as live threats; score and treat them as preparation, priority 35
- Put CT discoveries on monitoring so activation becomes a case, not a surprise
- Keep the CT record in the evidence block โ its date anchors your timeline
- Note when a scan reports CT unavailable, and re-run rather than assuming a clean result
After you file: tracking the case
The follow-through is where most takedowns quietly die, so the product tracks it as a case. States run from evidence collected through packet built, submitted and provider response, to resolved โ and a case can be re-opened as reappeared when monitoring finds the same threat back. Submitted and provider-response states are recorded as holder attestations, honestly labelled, while a verified resolution needs a re-scan showing the target is gone. The recheck after submission is set at seven days.
Where efforts like this usually go wrong
A second failure is overreach โ padding a filing with suspicions the evidence does not carry. TakedownCoop's scan is careful to separate what it confirmed from what it could not check, and a filing should inherit that discipline exactly: claim the resolving domain, the certificate, the screenshots you actually hold, and stop there. Reviewers act fastest on filings whose every sentence they can verify, and a single inflated claim taxes all the true ones beside it.
Finally, do not let a win delete the record. Brands that close a takedown by celebrating and clearing the folder meet the reappearance defenceless; brands that keep the case โ evidence, tickets, verified resolution and all โ meet it with precedent. In this product the record is not paperwork after the work. Kept properly, it is most of the work, because the second filing is always the one that ends the pattern.
Keeping it from coming back
Impersonators rotate, so a one-off filing is a snapshot, not a solution. Monitoring re-scans the domain, and when a known threat reappears the case re-opens and its packet regenerates. Pair that with the verified-genuine page โ a public page where customers can confirm they are dealing with the real brand โ and the timeline export (JSON and CSV) that processors and insurers ask for, and Certificate Transparency evidence stops depending on whoever happens to notice the fake next.
Frequently asked questions
Where does the CT data come from?
The public Certificate Transparency logs, aggregated through crt.sh, as the scanner's own documentation states.
What is a CT discovery?
A lookalike second-level domain found in the logs that the candidate generator never created โ added at priority 35 with the note 'seen in Certificate Transparency logs'.
Why filter CT results by the brand string?
Shared/SAN certificates carry unrelated names. Only names containing your brand are evidence about your brand.
What if CT is unavailable during a scan?
The scan states it โ the note records the failure rather than hiding it. Treat the result as incomplete and re-scan.
Keep exploring
TakedownCoop home โ run the free brand scan ยท All TakedownCoop guides ยท Pricing โ Free, Pro and Agency ยท Get a license key ยท Takedown cases ยท My street (dashboard) ยท Terms ยท Privacy ยท Ingenious AI โ all platforms