← Go back

Brand Impersonation vs Counterfeiting: What Is the Difference?

Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team

The short answer

Impersonation pretends to be your business — your name, store, profiles — while counterfeiting sells fake versions of your products under your brand. They overlap constantly: the fake store on a lookalike domain is impersonation selling counterfeits. TakedownCoop files them through linked channels — registrar, host and platform packets for the impersonation; per-listing marketplace reports, with test-buy statements, for the counterfeits.

Run the free brand scan — one domain, no account, no card

What is impersonation versus counterfeiting?

Impersonation is an identity offence: the victim is deceived about who they are dealing with. Counterfeiting is a product offence: the goods themselves are fake. A single operation usually commits both, but channels judge them differently — registrars and hosts act on the impersonating infrastructure, marketplaces act on the counterfeit listings — which is why the packet generator keeps them as distinct, linked filings.

What is impersonation versus counterfeiting?

Impersonation is an identity offence: the victim is deceived about who they are dealing with. Counterfeiting is a product offence: the goods themselves are fake. A single operation usually commits both, but channels judge them differently — registrars and hosts act on the impersonating infrastructure, marketplaces act on the counterfeit listings — which is why the packet generator keeps them as distinct, linked filings.

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 impersonation versus counterfeiting: 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.

Same operation, two evidence stories

The impersonation story is told in infrastructure: the lookalike domain, its DNS and certificate record, the cloned storefront, the fake profile. Its evidence block is the scan's output, and its filings ask infrastructure owners — registrar, host, ad platforms — to withdraw the stage the fraud performs on. Nothing in that story requires proving any single product is fake.

The counterfeiting story is told in listings: this ASIN, this listing ID, these photographs of your product, this unauthorised seller — and, as the marketplace checklist specifies, whether a test buy was made, because a purchased fake is the strongest listing evidence there is. Keeping the stories distinct matters practically: a marketplace will not suspend a domain, and a registrar will not adjudicate a handbag. File each story where it is judged.

A worked example, end to end

A fictional luggage brand, Voyager Pack at voyagerpack.com, fights one operation on both tracks in the same week. Track one, impersonation: the lookalike voyagerpack-outlet.com scans at 90, and registrar plus host packets carry the infrastructure evidence. Track two, counterfeiting: eleven marketplace listings using its product photos are reported one by one from the brand registry, each stating the seller is unauthorised and that a test buy was made on two of them. The listing reports cite the lookalike domain as the traffic source — the packet subject's own construction — so the two tracks corroborate each other.

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.

  1. Separate the operation into its two stories: infrastructure and listings
  2. File the impersonation with registrar, host and ad/platform channels using scan evidence
  3. Report counterfeits per listing from the brand registry, stating non-authorisation
  4. Record whether a test buy was made, truthfully, for counterfeit listings
  5. Link the cases — each track's IDs strengthen the other track's escalation

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 impersonation versus counterfeiting 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 impersonation versus counterfeiting stops depending on whoever happens to notice the fake next.

Frequently asked questions

Can one fake store be both?

Usually, yes: it impersonates your business and sells counterfeit goods. It still gets both filings, because different channels judge each half.

Which track should I start with?

The live infrastructure — a resolving lookalike at priority 80–90 monetises every listing it feeds. File it first, listings in parallel.

Does a test buy prove impersonation?

A test buy proves the goods are counterfeit — marketplace evidence. The domain and store evidence proves the impersonation. Keep them in their own filings.

What if there are listings but no lookalike domain?

Then the marketplace track stands alone: registry enrolment, per-listing reports, kept case IDs. The scan still checks whether a domain is feeding them.

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