← Go back

How Should You Take Evidence Screenshots for a Takedown?

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

The short answer

Capture the fake as a stranger would meet it: the full page with its URL visible, the date established, and the harmful act on screen — the login form, the payment ask, the discount claim. Three packet checklists demand them (registrar: 'dated screenshots of the live site if it resolves'; host: the same; Meta: the scam ad beside your genuine Page; Google Ads: screenshots with timestamps). Take them before you file, because live fakes change or vanish.

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

What is evidence screenshots?

Evidence screenshots are dated visual captures of an impersonation in the act, taken by the brand owner to accompany a packet. They complement the scan's machine evidence: DNS and Certificate Transparency prove the infrastructure exists; screenshots prove what a customer actually saw when they arrived there.

What is evidence screenshots?

Evidence screenshots are dated visual captures of an impersonation in the act, taken by the brand owner to accompany a packet. They complement the scan's machine evidence: DNS and Certificate Transparency prove the infrastructure exists; screenshots prove what a customer actually saw when they arrived there.

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

Shoot what the reviewer cannot see from their desk

A reviewer at a registrar or host can re-run DNS in seconds — what they cannot recover is the page as it existed when you found it, especially after your filing prompts the operator to change it. That is why the checklists insist on dating and timing: a screenshot with a visible date and time, showing the address bar, is a contemporaneous record; an undated crop is an assertion. Capture the widest honest frame — full page, URL, the offer or form — and capture the journey too: the ad, the click, the landing page, in sequence.

The Meta checklist adds the comparison shot: the scam ad or profile next to your genuine Page. Side-by-side captures do the reviewer's pattern-matching for them — same logo, same imagery, different account — and they double as your internal record of exactly how the brand was worn. Store the originals with the case, unedited; cropped copies can illustrate, but the evidence is the untouched file with its date.

A worked example, end to end

A fictional tea brand, Sorrel & Sage at sorrel-sage.com, finds its clone live on a Monday at 09:40. Before filing anything, the owner captures five dated frames: the Google ad with its destination URL, the landing page full-screen with the address bar visible, the checkout asking for card details, the fake's 'about' page using the brand's market photos, and the Meta variant beside the genuine Page. The registrar and host packets filed that afternoon carry the set. On Thursday the clone changes its name and logo; the case's Monday frames are the only record of what customers were actually shown.

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. Screenshot before you file — live impersonation content is perishable
  2. Include the URL and an on-screen date or timestamp in every frame
  3. Capture the harmful act: login form, payment ask, false claim
  4. Take the comparison shot — fake beside your genuine Page or store
  5. Store originals unedited in the case; use copies for illustration

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

Frequently asked questions

Which checklists require screenshots?

The registrar and host checklists ask for dated screenshots of the live site; Meta's asks for the scam ad or profile next to your genuine Page; Google Ads asks for screenshots with timestamps.

Full page or close-ups?

Full page with the URL visible first; close-ups can follow. The wide frame is what proves context and date.

The fake is already down. Are my screenshots still useful?

Yes — they are the contemporaneous record of what ran, and they belong in the case and any escalation or processor report.

Can I annotate the screenshots?

Annotate copies if it helps a reviewer; keep the originals untouched in the case as the evidence of record.

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