← Go back

How Does Takedown Case Tracking Work, From Evidence to Resolution?

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

The short answer

Each impersonation target becomes a case that moves through six states — evidence collected, packet built, submitted, provider response, resolved, and reappeared — with every transition recorded on a timeline. Submitted and provider-response states are labelled holder attestations, because you report them; resolution only counts when a re-scan verifies the target is actually gone.

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

What is takedown case tracking?

Case tracking is TakedownCoop's end-to-end record for one target — a lookalike domain, fake store, social profile or scam ad. It exists because takedowns are not single messages but sequences stretched over weeks: filings, replies, silences, rechecks and returns, each of which needs a home that is not someone's inbox.

What is takedown case tracking?

Case tracking is TakedownCoop's end-to-end record for one target — a lookalike domain, fake store, social profile or scam ad. It exists because takedowns are not single messages but sequences stretched over weeks: filings, replies, silences, rechecks and returns, each of which needs a home that is not someone's inbox.

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 takedown case tracking, 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 takedown case tracking in the order an impersonator would exploit it — live doors first — while the scan states plainly which checks it could not perform.

Six states that tell the truth about a takedown

The state list is short because each state makes a different claim. 'Evidence collected' and 'packet built' are the product's own acts, recorded from the scan and the generator. 'Submitted' and 'provider response recorded' are labelled, in the state definitions themselves, as holder attestation — the system records that you say you filed and that a provider replied, without pretending the product witnessed either. 'Resolved' can carry either basis, and the record says which.

The sixth state is the honest one most trackers omit: 'reappeared'. Takedowns end, and then sometimes un-end — monitoring finds the target back, and the case re-opens with its history intact rather than spawning an amnesiac duplicate. Together the six states mean a brand can answer, at any moment, the only questions that matter: what do we have, what did we file, what did they say, what is verified gone, and what came back.

A worked example, end to end

A fictional software studio, Brightstack at brightstack.io, runs one campaign through the full lifecycle: the scan hit becomes a case (evidence collected, Monday), the registrar packet is generated (packet built, Tuesday), the owner files it and marks the case submitted with the ticket number (Wednesday), the registrar's reply is recorded as a provider response (the following week), and after the seven-day recheck the re-scan finds the domain no longer resolving — resolved, basis: verification. Four months later monitoring flags the name resolving again, and the case shows reappeared, with the entire first campaign one click above the new filing.

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. Open a case for every target — domain, store, profile, ad — not one case per campaign
  2. Record ticket and case IDs the moment a channel returns them
  3. Mark submissions and provider replies as what they are: your attestations
  4. Let resolution be set by re-scan verification wherever possible
  5. When a target returns, re-open its case — never start a duplicate

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 takedown case tracking: walk the street, knock with evidence, keep watch.

Frequently asked questions

What are the six case states?

Evidence collected; takedown packet built; submitted (holder attestation); provider response recorded (holder attestation); resolved; and reappeared — re-opened.

Why label two states as attestations?

Because the product did not witness your filing or the provider's reply — you did. The record distinguishes what you attest from what re-scans verify.

What target types can a case track?

Four: lookalike domain, fake store, social profile and scam advertisement.

Can I export a case history?

Yes — the evidence timeline exports as JSON or CSV, one of the Pro features built for processors and insurers.

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