How Do You Spot a Fake Social Profile of Your Business?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
Check your exact brand handle on each platform — impersonators take it where you did not, or a spelling a follower cannot distinguish. TakedownCoop's free scan includes a public, no-login profile check at your exact handle, and it reports the outcome honestly: a profile found, no profile found, or 'could not be checked' where a login wall blocks the public view.
What is fake social profiles?
A fake social profile is an account that presents itself as a business it does not belong to — its handle, name, imagery and posts — usually to run scam ads, message customers with fake offers, or lend credibility to a fake store. In TakedownCoop's case system, 'social profile' is its own target type.
What is fake social profiles?
A fake social profile is an account that presents itself as a business it does not belong to — its handle, name, imagery and posts — usually to run scam ads, message customers with fake offers, or lend credibility to a fake store. In TakedownCoop's case system, 'social profile' is its own target type.
TakedownCoop's free brand scan is where fake social profiles 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 honest limits of a public check
The profile check is deliberately modest, and its wording in the code is the product's honesty rule in miniature: it performs a public check at the exact-handle URL, and where a platform redirects to a login page or blocks the request, the verdict is 'could not be checked publicly' — never converted into a claim that a profile does or does not exist. For a takedown tool, that restraint is the credibility: the findings it does report can be trusted because the ones it cannot make are labelled.
Within those limits, the signals are practical. Your exact handle taken on a platform where you never registered is a finding. A profile using your imagery that links out to a lookalike domain ties the social case to the domain evidence from the same scan. And a profile your scan could not check is a to-do — verify it manually from a logged-in account — not a clean bill of health.
A worked example, end to end
A fictional bakery, Golden Crust at goldencrust.com, runs the scan before opening its first real Instagram account — and finds the exact handle already taken by an account posting its photos and a 'franchise opportunities' link to goldencrust-franchise.com. The scan's profile check found the account publicly; the domain check scored the franchise site 80. The bakery files the Meta packet from its verified Business Manager account and the registrar packet for the domain, and opens both cases the same week it opens its genuine profile.
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.
- Check your exact handle on every major platform — register the genuine ones you are missing
- Run the free scan and read the profile verdicts literally, including 'could not be checked'
- Manually verify any platform the public check could not reach
- Screenshot fake profiles and every outbound link they post
- File the platform packet from your verified business account and link the domain case
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 fake social profiles 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, fake social profiles is an incident; watched continuously, it becomes a routine.
Frequently asked questions
What does the profile check actually do?
A public, no-login check at the exact-handle URL for your brand name, reporting found, not found, or could-not-be-checked per platform.
The scan says 'could not be checked'. Is the profile fake or not?
Unknown — that is what the verdict means. Login walls and bot blocks are reported honestly; verify manually from a logged-in account.
Someone took my exact handle but posts nothing. Worth acting on?
It is a finding worth recording: handles are claimed ahead of campaigns, and a case opened now makes a later campaign faster to dismantle.
Which packet covers fake profiles?
The Meta channel covers Facebook and Instagram profiles and ads; other platforms are filed through their own IP routes with the same evidence block.
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