What Is a TLD-Swap Lookalike?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
A TLD swap is your exact second-level name registered under a different top-level domain — your brand at .net, .shop or another ending instead of your real one. The scanner appends alternate TLDs to your unchanged name as their own candidate family, then applies the same DNS and Certificate Transparency checks, so a perfect-spelling impostor cannot hide behind a perfect spelling.
What is TLD-swap lookalikes?
The top-level domain is the ending of an address — .com, .org, .io and hundreds of newer ones. A TLD-swap lookalike changes only that ending. Because the brand name itself is letter-perfect, customers who glance at the name and skip the ending walk straight in, and searchers who misremember the ending arrive there honestly.
What is TLD-swap lookalikes?
The top-level domain is the ending of an address — .com, .org, .io and hundreds of newer ones. A TLD-swap lookalike changes only that ending. Because the brand name itself is letter-perfect, customers who glance at the name and skip the ending walk straight in, and searchers who misremember the ending arrive there honestly.
TakedownCoop's free brand scan is where TLD-swap lookalikes stops being a suspicion and becomes a record. You enter one domain — no account, no card — and the scanner generates dozens of lookalike candidates from your brand name: deleted-letter, transposed-letter, duplicated-letter and keyboard-neighbour typosquats, homoglyph swaps, affix squats built from prefixes and suffixes, and the same name on different top-level domains. Every candidate is then checked against real DNS resolution, so a name that merely exists on paper is never reported as a live threat.
How the scan ranks and records it
Certificate Transparency is the scan's second witness. When a lookalike holds a publicly logged certificate, the scan records it, and names that appear in the logs but were never generated as candidates are added as CT discoveries. Hits are then prioritised the way a small team needs them: a live, resolving lookalike with a certificate scores 90, a live one without a certificate 80, a registered but non-resolving name 50 with a certificate or 40 without, and a certificate-only discovery 35 or 30. Live threats are filed first; dormant registrations are watched, not panicked over.
Perfect name, wrong ending, real problem
TLD swaps defeat the advice most businesses give their customers. 'Check the name is spelled right' fails when the name is spelled right. The defence has to live at the scan level: the generator adds the same-name candidates on alternate TLDs as a distinct family, labelled 'tld-swap', so a clean typosquat report never gives false comfort while an impostor trades happily on another ending.
The filing route is unchanged — registrar of record via RDAP, host via the A record — but the evidence reads even more cleanly than a typo case: the registered name is identical to yours, letter for letter, and only the ending differs. If the swap also resolves to a clone store with a certificate, it scores 90 and belongs at the front of the queue with the other live threats.
A worked example, end to end
A fictional coffee roaster, Alto Roast at altoroast.com, finds altoroast.shop live with a certificate, selling 'subscriptions' using the roaster's own product photography — priority 90. Customers who typed the name from memory and guessed the ending had no typo to catch. The registrar packet goes in the day the scan runs, the host packet follows with screenshots, and the roaster's packaging gains its verified-genuine page address, because the one thing the swap cannot copy is the genuine page's verification.
Turning evidence into a filing
Finding the problem is only the first third of the work. On Pro ($49/mo) and Agency ($99/mo), each confirmed hit can generate a takedown packet: a complete, channel-correct evidence packet with a filing checklist written for the specific channel — registrar abuse desk, hosting provider, Meta, Google Ads, marketplaces or app stores. The packet carries the genuine brand and domain, the lookalike, how it was detected, whether it resolved at scan time, the DNS and Certificate Transparency evidence, and the priority score, so the person receiving it does not have to take your word for anything.
- Include alternate-TLD candidates in every scan — never scan spellings only
- File registrar and host packets on resolving TLD swaps at full priority
- Screenshot the clone's use of your branding and prices
- Tell customers which ending is yours, and give them the verified-genuine page to check
- Monitor the swap after takedown — endings are cheap to re-register
After you file: tracking the case
After filing, the case — not your inbox — is the system of record. TakedownCoop's case tracking follows each target through evidence collected, packet built, submitted, provider response recorded, resolved, and, if the impersonator returns, reappeared and re-opened. Two of those states are labelled as holder attestations, because the product records what you report about a submission or a provider's reply; a resolution only counts as verified when a re-scan confirms the item is actually gone. A submitted case is scheduled for recheck seven days after submission.
Where efforts like this usually go wrong
The commonest failure with TLD-swap lookalikes 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
The last step is keeping the street watched. Re-appearance monitoring on Pro and Agency re-scans your domain and regenerates packets when an impostor returns, instead of waiting for a customer to find the fake first. The public verified-genuine page gives customers a door they can check — one page that confirms they are at your real business — and the evidence timeline exports as JSON or CSV for payment processors and insurers. Dealt with once, TLD-swap lookalikes is an incident; watched continuously, it becomes a routine.
Frequently asked questions
How does the scanner generate TLD swaps?
It appends a list of alternate TLDs to your unchanged brand name — the 'tld-swap' candidate family.
Is my-brand-but-.shop really confusing?
Yes — the name is letter-perfect; only the ending differs, and endings are the part of an address people check least.
Should I buy every TLD myself?
There are hundreds of TLDs; buying them all is impractical and still misses typos and affixes. Scanning plus monitoring covers the endings that actually get registered.
What priority does a live TLD swap get?
90 with a certificate, 80 without — the same as any resolving hit.
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