A Customer Found a Fake Store Before You Did — What Do You Do Next?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
Move the same day, in this order: thank the customer and capture exactly what they saw — the address they visited, screenshots, any order or payment details; run the free scan on your genuine domain to document the fake's infrastructure; file the registrar and host packets on the live hit; and tell your customers, through your real channels and your verified-genuine page, which door is yours. Speed matters because the fake monetises every day of confusion.
What is a customer finds the fake store first?
The customer-first discovery is the most common way small businesses learn they are being impersonated — the landing page's model assumes it, which is why the scan is free and accountless: the worst day of your brand's year should not begin with a signup form. The customer's message is not just a warning; handled properly it is the first evidence in the case.
What is a customer finds the fake store first?
The customer-first discovery is the most common way small businesses learn they are being impersonated — the landing page's model assumes it, which is why the scan is free and accountless: the worst day of your brand's year should not begin with a signup form. The customer's message is not just a warning; handled properly it is the first evidence in the case.
TakedownCoop's free brand scan is where a customer finds the fake store first 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.
The first hour: evidence before outrage
A customer report decays fast. The fake store can change its name, its prices or its entire storefront the moment it senses attention — and the customer's recollection of the address blurs within days. So the first moves are capture moves: the exact domain they used, screenshots of what they saw, the order confirmation or card statement if they paid. Then the scan converts their anecdote into infrastructure evidence — the domain's DNS, certificate and priority — that packets and cases are built from.
The second obligation is to the other customers, the ones who have not reported anything because they have not yet doubted. A short notice on your genuine channels — there is a fake store, this is our only real address, check it here on our verified-genuine page — costs you an awkward hour and saves strangers real money. Businesses hide impersonation out of embarrassment; impersonators count on exactly that silence.
A worked example, end to end
A fictional plant shop, Verdant at verdantplants.com, gets a Sunday message: a customer paid verdant-plants-sale.com for a plant that never shipped. The owner replies within the hour, captures the customer's order email and the address, and scans: the domain is live with a certificate, priority 90. Registrar and host packets are filed Monday with the customer's screenshots consented and attached, a case is opened, and the shop posts the warning with its verified-genuine page link. Three more customers come forward under the post — each one's details joining the same case instead of starting new ones.
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.
- Reply fast and capture: exact address, screenshots, order or payment details
- Run the free scan the same day and match the reported domain to a documented hit
- File registrar and host packets on the live hit within days, not weeks
- Warn customers through your genuine channels and link the verified-genuine page
- Open the case and add every subsequent customer report to it — one thread, all the evidence
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 a customer finds the fake store first 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, a customer finds the fake store first is an incident; watched continuously, it becomes a routine.
Frequently asked questions
The customer paid the fake. Can the takedown get their money back?
The packets remove the fake; refunds run through the customer's payment provider. Your timeline export — scan, filings, verified resolution — is the document that supports their dispute.
Should I confront the fake store directly?
No — capture first. Contact can tip the operator into changing or moving the evidence, and channels, not conversations, remove infrastructure.
Is one customer report enough to file on?
With the scan behind it, yes: the report locates the target, the scan documents it. Do not wait for a second victim to begin.
Will publicising the fake hurt my brand?
Silence helps only the impersonator. A clear warning with a checkable genuine page protects customers and demonstrates the diligence processors later ask about.
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
- Your Brand Is in a Scam Ad — What Should You Do First?
- Someone Registered Your Brand with a Different TLD — What Next?
- 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?