What Is a Lookalike Domain?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
A lookalike domain is a registered domain designed to be mistaken for a genuine brand's domain — by a typo, a visual swap, an added word or a different ending. TakedownCoop's scan generates the plausible lookalikes of your domain across all four techniques, confirms which exist using DNS and Certificate Transparency, and ranks them live-first by priority score.
What is lookalike domains?
A lookalike domain is any domain, other than the brand's own, whose name is close enough to the genuine domain to divert its visitors. Closeness is engineered, not accidental: each lookalike family — typosquat, homoglyph, affix squat, TLD swap — exploits a different weakness in how people type, read and remember addresses.
What is lookalike domains?
A lookalike domain is any domain, other than the brand's own, whose name is close enough to the genuine domain to divert its visitors. Closeness is engineered, not accidental: each lookalike family — typosquat, homoglyph, affix squat, TLD swap — exploits a different weakness in how people type, read and remember addresses.
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 lookalike domains: 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.
Close enough is a design specification
Impersonators do not pick names at random; they pick the names your customers will produce or accept. That is why detection works backwards from the same specification: the scanner's generator enumerates the names a customer could plausibly land on — every deletion, swap, neighbour, homoglyph, decoration and re-ending of your name — and reality, via DNS and CT, decides which ones someone actually registered.
A lookalike's danger is not its name but its state. The priority scale encodes it: resolving with a certificate, 90; resolving, 80; registered and dormant, 50 or 40; a certificate in the logs before anything resolves, 35 or 30. Two lookalikes with identical names on paper can be a live fraud and a parked speculation, and the scan's job is to make sure you spend your filing effort on the fraud first.
A worked example, end to end
A fictional meal-kit company, Supper Society at suppersociety.com, scans and gets a tour of the whole taxonomy in one result list: suppersociety.shop (TLD swap, 90), supper-society.com (affix-style hyphen variant resolving, 80), suppersocety.com (deletion, dormant, 40) and a CT-only discovery at 35. Four lookalikes, four different techniques, one ordered work list — the two live names are filed within the week, the two quiet ones go to monitoring.
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.
- Scan your genuine domain so all four lookalike families are enumerated
- Sort by priority — live lookalikes are filed before dormant ones are watched
- For each live hit, generate the registrar and host packets from the same evidence
- Record each lookalike as its own case with its kind and score
- Monitor the whole set — a dormant lookalike is a lookalike in waiting
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
The commonest failure with lookalike domains is treating it as a message instead of a case. A report typed from memory, sent from the wrong account, missing its ticket number within the week — each is a small thing, and together they are why impersonators outlast brands that were right about everything. The artefacts exist to remove memory from the loop: the evidence block is generated, not recalled; the checklist is written for the channel, not improvised; the case holds the IDs, not an inbox thread nobody can find in month two.
There is also a sequencing mistake: acting on the loudest artefact instead of the highest-priority one. A furious customer message about a dormant name feels urgent; a quiet scan result showing a live, certified clone is urgent. The priority score exists to arbitrate exactly that conflict — 90 before 40, live before loud — and the teams that follow it spend their filing hours where the money is actually leaving.
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 lookalike domains stops depending on whoever happens to notice the fake next.
Frequently asked questions
What are the lookalike families?
Typosquats (deletion, transposition, duplication, keyboard), homoglyphs, affix squats and TLD swaps — the scanner's candidate families.
Is a similar name automatically an infringement?
The scan establishes existence and state, not legal conclusions. The packet presents the registration, resolution and content evidence for the channel to judge.
My lookalike list has names I registered myself. Problem?
No — your own defensive registrations will appear as registered names. Note them in your records so filings only target names you do not control.
How often do new lookalikes appear?
Registrations are cheap and continuous, which is why the workflow ends in monitoring rather than a one-time clean-up.
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