How Can You Tell If a Store Using Your Brand Is Fake?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
Start with the domain: if the store is not on a domain you control, it is not your store, whatever its logo says. Run your genuine domain through the free scan — if the store's domain appears as a lookalike hit with DNS and certificate evidence, you have documented proof rather than a hunch, and the fake store becomes a case with registrar, host and marketplace packets.
What is fake stores using your brand?
A fake store is an online shop that presents a real brand's identity — name, imagery, products — without the brand's authorisation, typically to take payments for goods that never ship or to harvest card details. 'Fake store' is one of the four target types TakedownCoop's case system tracks, distinct from the lookalike domain it usually lives on.
What is fake stores using your brand?
A fake store is an online shop that presents a real brand's identity — name, imagery, products — without the brand's authorisation, typically to take payments for goods that never ship or to harvest card details. 'Fake store' is one of the four target types TakedownCoop's case system tracks, distinct from the lookalike domain it usually lives on.
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 fake stores using your brand, 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 fake stores using your brand in the order an impersonator would exploit it — live doors first — while the scan states plainly which checks it could not perform.
Authorised sellers exist; unauthorised stores confess in the details
The honest complication is that legitimate resellers exist, which is why the Google Ads packet insists you state clearly whether any advertiser is authorised to use your mark. Apply the same discipline to stores: list everyone you have actually authorised, and a store not on that list, on a domain you do not own, trading on your brand, is a fake store by your own records — not by vibes.
Corroboration comes from the scan. A fake store almost always sits on infrastructure built for it: a lookalike domain registered recently, resolving, holding a fresh certificate — the 90-point profile. The evidence block gives you that profile in one place, and the case system lets the store and its domain be tracked as linked targets, so when the domain's registrar acts, the store's case can be verified closed by re-scan rather than by hope.
A worked example, end to end
A fictional candle brand, Ember & Oak at emberandoak.com, is sent a screenshot of 'its' store offering 70% off on emberandoak-outlet.com. The brand's authorised-seller list has two entries; the outlet is neither, and the domain is not theirs. The scan scores it 90. Three cases open — fake store, lookalike domain, and the scam ads customers saw — and the registrar, host and Meta packets go out with the brand's authorisation statement at the top: these sellers are authorised, this one is not.
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.
- Write down your authorised sellers before you judge any store
- Check the domain — a store on a domain you do not control is not your store
- Scan your genuine domain and match the store's domain to a documented hit
- Screenshot the store's pages, prices and checkout before filing
- Open fake-store and domain cases together and file both channels' packets
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
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
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 fake stores using your brand: walk the street, knock with evidence, keep watch.
Frequently asked questions
Could it be a legitimate reseller I forgot about?
Check your authorisation records first — the same discipline the Google Ads checklist requires when you state who may use your mark.
What if the fake store uses its own unrelated domain?
The store is still a case target type, and ads or profiles linking to it carry the domain evidence. Channels act on the store, its listings and its traffic sources together.
Do I need a test purchase to prove it is fake?
For marketplace counterfeits the checklist asks you to state whether a test buy was made — it is evidence, not a precondition for the domain and host filings.
What closes a fake-store case?
Verification by re-scan: the store gone or the domain no longer resolving — not merely a provider's acknowledgement.
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