← Go back

What Should a Takedown Evidence Packet Include?

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

The short answer

A complete packet identifies the genuine brand and domain, names the lookalike, explains how it was detected, states whether it resolved at scan time, and attaches the DNS and Certificate Transparency evidence with a priority score — then adds a filing checklist written for the specific channel receiving it. Evidence that a stranger can re-verify beats a complaint a stranger must take on trust.

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

What is a takedown evidence packet?

A takedown evidence packet is the self-contained bundle a brand owner files with a registrar, host, ad platform, marketplace or app store to get an impersonation removed. It is the core artefact TakedownCoop generates on Pro and Agency plans: one packet per channel, all built on the same evidence block.

What is a takedown evidence packet?

A takedown evidence packet is the self-contained bundle a brand owner files with a registrar, host, ad platform, marketplace or app store to get an impersonation removed. It is the core artefact TakedownCoop generates on Pro and Agency plans: one packet per channel, all built on the same evidence block.

TakedownCoop's free brand scan is where a takedown evidence packet 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.

One evidence block, six channel shapes

The evidence block is deliberately identical across channels — genuine brand, lookalike domain, detection kind, resolution status, DNS detail, CT evidence, priority — because consistency is what makes six filings look like one case. What changes per channel is everything around it: the registrar packet's subject speaks of impersonation and phishing, the marketplace packet's subject names counterfeit listings and their traffic source, and each checklist gives that channel's filing order.

Completeness is also an honesty test. The scan records what it could not check as 'could not be checked', and the packet inherits that discipline: a profile behind a login wall is reported as unchecked, not as confirmed or cleared. Abuse desks read packets from strangers all day; the one that admits its limits is the one whose positive claims get believed.

A worked example, end to end

A fictional pet-food brand, Wildgrain at wildgrain.pet, gets one scan with three hits: a resolving lookalike at priority 90, a dormant registration at 40, and a CT-only discovery at 35. The 90 generates three packets the same day — registrar, host and Meta — and although each packet's subject and checklist differ, the evidence block in all three is word-for-word the same: same genuine domain, same lookalike, same DNS detail, same certificate record. When the host's abuse desk compares notes with the registrar's ticket, the two filings corroborate each other exactly.

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.

  1. State the genuine brand and domain and the lookalike being reported
  2. Explain how the lookalike was detected and whether it resolved at scan time
  3. Include the DNS evidence and Certificate Transparency evidence verbatim
  4. Add the priority score and dated screenshots if the site resolves
  5. Finish with the filing checklist written for the channel receiving the packet

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 a takedown evidence packet 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, a takedown evidence packet is an incident; watched continuously, it becomes a routine.

Frequently asked questions

Why one packet per channel instead of one big complaint?

Each channel has its own route, subject framing and checklist. The evidence block stays identical; the packet around it is channel-correct.

What if part of the scan could not be checked?

The packet says so. TakedownCoop reports unchecked items as 'could not be checked' — never as confirmed and never as cleared.

Who files the packet?

The brand owner or their authorised agent. TakedownCoop prepares packets; it does not claim to submit them on your behalf.

Which plans include packets?

Packet generation is a Pro feature ($49/mo); Agency ($99/mo) adds multi-brand monitoring and per-client packets and verified pages.

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