Someone Registered Your Brand with a Different TLD — What Next?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
Establish its state with the free scan, then act on the score. If the TLD swap resolves — 80, or 90 with a certificate — file registrar and host packets this week: it is a letter-perfect impersonation in production. If it is registered but dormant — 50 or 40 — the registrar channel is still open to you, and monitoring should hold the name so activation becomes an alert. Either way, do not buy it from the squatter as your first move.
What is your brand registered on another TLD?
This is the TLD-swap scenario from the registrant's side: your second-level name, unchanged, appearing in someone else's registration under another top-level domain. The scan treats same-name alternate-TLD names as their own candidate family, so this discovery is usually made by the scan itself — or by a customer who typed your name and guessed the wrong ending.
What is your brand registered on another TLD?
This is the TLD-swap scenario from the registrant's side: your second-level name, unchanged, appearing in someone else's registration under another top-level domain. The scan treats same-name alternate-TLD names as their own candidate family, so this discovery is usually made by the scan itself — or by a customer who typed your name and guessed the wrong ending.
The scan behind this page works in one pass over your whole street. It generates typosquat, homoglyph, affix and TLD-swap candidates from your domain, checks every one against real DNS resolution, searches Certificate Transparency logs for lookalike certificates, and tries a public, no-login check for fake profiles using your exact brand handle. For your brand registered on another TLD, that means the first artefact you work from is evidence — what resolved, what holds a certificate, what could not be checked — rather than a screenshot someone sent you.
How the scan ranks and records it
Prioritisation is built into the result list. A hit that resolves and holds a certificate scores 90; resolving without a certificate, 80; registered but not resolving, 50 with a certificate and 40 without; a name seen only in Certificate Transparency logs scores 35, or 30 when it neither resolves nor is registered. You therefore deal with your brand registered on another TLD in the order an impersonator would exploit it — live doors first — while the scan states plainly which checks it could not perform.
The state decides the filing, the name decides the strength
A registered TLD swap is not yet a harm; a resolving one is. The scan's DNS and CT checks separate the two in one result — resolution for the live question, the certificate record for intent — and your response should track the score rather than your adrenaline. Live means packets; dormant means a considered registrar challenge and a certain monitoring entry, because a name held today is a store tomorrow.
When you do file, the evidence is uncommonly clean. Trademark exhibits aside, the registrar compares two strings: your brand name and the registrant's — identical but for the ending you own and they took. There is no typo to argue about, no similarity threshold to debate. Pair that with resolution and content evidence if it is live, and the TLD-swap packet is among the strongest the generator produces.
A worked example, end to end
A fictional law-office supplier, Precedent Supply at precedentsupply.com, is alerted by its own scan: precedentsupply.co is registered, dormant, but holding a certificate — priority 50. The owner files nothing with a host (there is nothing to host-report) and opens monitoring the same day. When the name resolves six weeks later to a copied catalogue, the re-scan re-scores it 90, the case opens with six weeks of history, and the registrar packet leads with the certificate's issue date — preparation documented before the first customer was ever at risk.
Turning evidence into a filing
A complaint says 'this is fake'; a packet proves it. The Pro packet generator turns a confirmed hit into a channel-correct evidence packet — one for the registrar, one for the host, and separate ones for Meta, Google Ads, marketplaces and app stores where they apply — each with a filing checklist written for that channel. The honesty rule is printed in every packet: TakedownCoop prepares the evidence and never claims to submit to a channel it cannot actually submit to. Filing stays with you or your agent, which is also why the evidence has to stand on its own.
- Scan to establish the swap's state — resolving, certified, dormant — before choosing a response
- File registrar and host packets immediately on a resolving swap (80–90)
- For a dormant swap, consider the registrar challenge and always set monitoring
- Do not open with an offer to buy the name — it prices the next ten registrations
- Tell customers which ending is genuinely yours and publish your verified-genuine page
After you file: tracking the case
What happens next is tracked, not hoped for. Each target becomes a case — domain, fake store, social profile or scam ad — moving through evidence collected, packet built, submitted, provider response, resolved or reappeared. TakedownCoop distinguishes what you attest (that you submitted, that a provider replied) from what is verified by re-scan (that the item is actually gone), and it schedules a recheck seven days after a case is submitted so silence from a provider becomes a prompt, not a dead end.
Where efforts like this usually go wrong
The commonest failure with your brand registered on another TLD 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
Closing the loop matters because clones come back under new names and new accounts. Re-appearance monitoring re-scans and regenerates packets; the verified-genuine page lets a cautious customer verify your real door before paying anyone; and the case timeline — every event, in order — exports as JSON or CSV when a processor, insurer or marketplace asks how you handled it. That is the co-op model applied to your brand registered on another TLD: walk the street, knock with evidence, keep watch.
Frequently asked questions
How do I even find these registrations?
The scan generates same-name candidates on alternate TLDs as its 'tld-swap' family and checks them against DNS and CT — most owners learn of a swap from the scan, not from a customer.
A dormant swap: file or watch?
Both routes exist: the registrar channel addresses the registration itself; monitoring guarantees you learn the hour it activates. Watching alone is the minimum.
Should I just buy the name from the registrant?
Purchasing is your commercial choice, but it rewards the registration and funds the next one. The packet route exists so buying is never the only option.
The swap uses my name but sells unrelated goods. Still file?
The infrastructure evidence stands regardless of the goods: identical name, another ending, your trademark exhibit. File the registrar packet and let the channel judge.
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
Related guides
- A Fake Profile Is Messaging Your Customers — What Should You Do Next?
- Why Do Fake Shops Target Your Busiest Sales Periods?
- How Do You Monitor Your Brand Terms in Search Ads Weekly?
- How Do You Monitor App Store Search for Clones Weekly?
- How Do You Build a Brand Protection Routine for a Small Team?
- Free Brand Scan vs Pro: What Actually Changes?