Case Study / Impersonation An imposter site, dead in days, not months.
A pixel-for-pixel clone of a pre-IPO mining company's website went online with the company's real street address and a working contact form collecting enquiries meant for the real business. It had been live for months before anyone noticed. When we found it, nobody quietly de-indexed it. The host pulled the whole site down and banned the operator.
Hard removal
The site taken down at the host, not de-indexed from search
Banned
The operator's account terminated, more than the one clone
Days
From engagement start to offline, after months undetected
- MonthsThe clone was live and collecting enquiries through a working contact form, using the company's real street address. Nobody knew it existed.
- Day oneWe built the evidence package covering the copied assets, the false address use and the harvesting form, then filed it against the host's and registrar's own abuse policies.
- Days laterThe host removed the entire site and terminated the operator's account. It wasn't a de-indexing or a demotion, and it wasn't a takedown of one page.
- SinceIt has never come back, and the operator lost the account they would have rebuilt it on. The company is monitored now. The next one surfaces in hours.
Dates and the removal outcome come from the engagement record. Registrar and host correspondence and the evidence package are on file. Client specifics under NDA.
How to read this
There's a real gap between hiding a fake site and deleting one. De-indexing leaves it live for anyone with the link, and the operator just spins up another. A hard removal at the host takes the site off the internet, and banning the account takes away the place they would have rebuilt it.
The first row is the part to fix. The takedown was fast. The months nobody noticed were slow, and that gap makes the whole argument for monitoring.
The problem
Someone matched the company's site pixel for pixel and ran it with the real street address and a working contact form that harvested enquiries meant for the real business. It sat live for months, in front of investors and customers, during a pre-IPO window.
What we did
We documented the copied assets, the false use of the address and the harvesting form. Then we took it to the host and registrar under their own abuse policies, instead of sending a letter and hoping, because documentation is the whole difference between a takedown that takes days and one that takes months.
Where it landed
The host removed the entire site and banned the operator's account. That's no de-indexing, which would have left the clone live for anyone holding the link. It has never reappeared, and the company is now monitored, so the next attempt surfaces in hours rather than months.
What does your situation need?
Every engagement starts from its own point and has its own scope, so these results belong to this one engagement and don't promise your case will run on the same timeline. See how we help businesses if you want to see the options, or pick the specific service below.
The takedown took days. Nobody noticing took months. We fix the second part.
How we measured it. Removal outcome, dates and account termination come from the engagement record. Registrar and host correspondence and the evidence package are on file. Client specifics under NDA.
Every case study we publish is anonymized, and every figure on this page came out of the client's own account or a dated live check. We do not publish a number we cannot show you the source of.
Monitoring
This is the service behind the work on this page. It explains what we actually do, what you get, and what it costs.
See the service