← Go back

How Do You Export an Evidence Timeline as JSON or CSV?

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

The short answer

From the scan's timeline view, in either of the two formats the feature offers: JSON for systems and CSV for people. The timeline carries the sequence the case system records — scan evidence, packet builds, submissions, provider responses, rechecks and resolutions, each with its basis — and exporting it turns your takedown history into a document a processor, insurer or client can audit.

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

What is the evidence timeline export?

The evidence timeline is the ordered event record behind a scan and its cases, exportable as JSON or CSV on Pro and Agency plans. The pricing page lists 'Evidence timeline export (JSON + CSV)' as a Pro feature; the application serves both formats from the timeline endpoints for a scan.

What is the evidence timeline export?

The evidence timeline is the ordered event record behind a scan and its cases, exportable as JSON or CSV on Pro and Agency plans. The pricing page lists 'Evidence timeline export (JSON + CSV)' as a Pro feature; the application serves both formats from the timeline endpoints for a scan.

TakedownCoop's free brand scan is where the evidence timeline export 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 record, two audiences

CSV is the human format: rows a claims handler, a client or a board member can open in a spreadsheet and read top to bottom — what happened, when, in what order, with what outcome. JSON is the machine format: the same events structured for another system to ingest, whether that is an agency's internal tooling, a processor's dispute platform or your own archive. Offering both is a small design decision with a practical point — evidence that cannot travel to the person asking for it might as well not exist.

What makes the export worth sending is its grading. Because attestations and verifications are kept apart in the case data, the exported timeline does not flatten them: a reader can see which events the holder reported and which the re-scan observed. That is the difference between a narrative and a record, and it is why the timeline — rather than a folder of screenshots — is the artefact the product builds toward.

A worked example, end to end

A fictional tour operator in Belize, Caye Life at cayelife.com, has its card processor ask how a chargeback spike was handled. The operator exports the campaign timeline as CSV: the June scan with its 90-point hit, both packets built, the registrar ticket, the provider response recorded as attestation, the recheck, and the resolution recorded as verification. The processor's reviewer reads one file, top to bottom, and the dispute file closes without a single request for more documentation. The same timeline exports as JSON for the operator's own records system.

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. Keep case events complete as you go — the export is only as good as the record
  2. Export CSV for people: processors, insurers, clients, boards
  3. Export JSON for systems: tooling, archives, dispute platforms
  4. Check that attestation and verification bases survived the export before sending
  5. Re-export after every major event so the timeline you hold is current

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

Frequently asked questions

Which plans include the timeline export?

Pro ($49/mo) and Agency ($99/mo) — it is listed in the Pro feature set on the pricing page.

JSON or CSV — which should I send a processor?

CSV, unless they ask for structured data. People review spreadsheets; systems ingest JSON.

What events does the timeline contain?

The scan and case sequence: evidence, packet builds, submissions, provider responses, rechecks, resolutions and reappearances, with their bases.

Does the export include my screenshots?

The timeline exports the event record. Screenshots live in the case as the visual evidence the events refer to.

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