← Go back

How Can You Check If Someone Is Impersonating Your Business Online?

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

The short answer

Run the free brand scan on your domain — one entry, no account, no card. It checks dozens of generated lookalike candidates against live DNS, searches Certificate Transparency for lookalike certificates, and runs a public profile check at your exact handle. Add two manual passes the scan cannot do for you — a search of your brand terms for scam ads, and store search if you ship an app — and read every 'could not be checked' as a task, not a clearance.

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

What is checking for impersonation of your business?

An impersonation check is the systematic search for your business's doubles across the surfaces impersonators use: domains, certificates, profiles, ads, listings and apps. TakedownCoop's scan covers the first three mechanically; the others are structured by the same evidence model — if it exists, is it on infrastructure you control, and if not, it becomes a case.

What is checking for impersonation of your business?

An impersonation check is the systematic search for your business's doubles across the surfaces impersonators use: domains, certificates, profiles, ads, listings and apps. TakedownCoop's scan covers the first three mechanically; the others are structured by the same evidence model — if it exists, is it on infrastructure you control, and if not, it becomes a case.

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 checking for impersonation of your business, 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 checking for impersonation of your business in the order an impersonator would exploit it — live doors first — while the scan states plainly which checks it could not perform.

What the machine checks, what you check, what nobody can check for you

The machine's share is everything enumerable: the candidate families are finite and generatable, DNS and CT are public records, exact-handle profiles are publicly addressable. That is a larger share than most owners expect — the typical first scan's surprise is not that it found something, but that it checked so much in one pass and can prove, per candidate, what exists and what does not.

Your share is the logged-in world: ads you are served, profiles behind login walls the public check honestly flags as unchecked, listings inside marketplaces where you hold the brand account. The division is principled, not lazy — the scan never pretends to a logged-in view it does not have — and it defines your routine: machine re-scans on a rhythm, human checks on the same rhythm, both feeding the same cases.

A worked example, end to end

A fictional guesthouse in Belize, The Palms at thepalms.bz, does its first full check in one morning. The scan checks its candidate set and finds a dormant affix domain at 40 and a CT discovery at 35. The profile check finds nothing at its exact handle on two platforms and reports a third as could not be checked; the owner verifies that one manually — also clean. A brand-term search surfaces no scam ads. Result: no filings, two monitoring entries, and a baseline the owner can re-run monthly in minutes — which she does, and which catches the affix domain activating the following season.

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.

  1. Run the free scan on your genuine domain — domains, certificates, profiles in one pass
  2. Read 'could not be checked' verdicts as manual tasks and complete them logged-in
  3. Search your brand terms for scam ads and screenshot any you find with destinations visible
  4. Search the app stores for your brand if you ship an app
  5. Record the baseline and re-check on a rhythm — monitoring automates the domain side

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 checking for impersonation of your business: walk the street, knock with evidence, keep watch.

Frequently asked questions

What does the check cost?

The scan is free — one complete scan for one domain, no account, no card. Ads and store searches are your own time.

How long does a full check take?

The scan itself is one submission. The manual complements — brand-term ad search, store search, verifying unchecked profiles — take minutes each.

A clean check means I am safe, right?

It means nothing was found that day, within stated limits. Impersonation is registered continuously, which is why the workflow ends in monitoring and rhythm, not a certificate of safety.

Where do findings go?

Each becomes a case — domain, store, profile or ad — with packets generated per channel on Pro.

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