ZeroTrace OSINT
Exports — JSON, CSV, Markdown, PDF
Every result and every profile exports in four formats. The PDF is the deliverable shape.
The toolkit exports at three scopes:
- Per-result — the output of a single tool run.
- Selected findings — a chosen subset of a profile.
- Whole profile — the full case file.
At every scope, four formats are available: JSON, CSV, Markdown, and PDF. (PDF is profile-only.)
Per-result export
Every tool result has an export menu (Ctrl+Shift+E to open).
| Format | When to use |
|---|---|
| JSON | Machine-readable. Perfect for piping into a script, an enrichment system, or version-controlled investigation notes. |
| CSV | Table-shaped for spreadsheets. Best for tools that produce list-like output (subdomain discovery, port lists, breach matches). |
| Markdown | Human-readable report fragment. Drop it directly into your editor, your wiki, or a follow-up email. |
| Clipboard | Whichever format above, copied straight to clipboard. |
The export captures the full result envelope — input, output, sources, warnings, timestamp, the tool that produced it. No fidelity loss.
Selected-findings export
Inside a profile, select findings (click + Shift / Ctrl / Cmd) and export only those. Useful when:
- The profile holds a wider investigation than the report covers.
- You want a partial deliverable for an interim update.
- You want one format for one finding cluster (Markdown) and another for the rest (JSON).
The selection mechanism is the same as bulk operations — see Findings.
Whole-profile export
The profile detail page has a top-level Export button. It exports every finding in the profile, plus your notes, in the chosen format.
Whole-profile exports add metadata: profile name, profile description, created date, exported date, finding count, severity histogram. JSON exports include this as a wrapper object; Markdown exports include it as a header section; PDF exports use it on the cover page.
The PDF report
The PDF is the deliverable shape — the artefact you give to a client, an editor, an authorised stakeholder.
It contains:
- Cover page — profile name, description, finding count by severity, exported date.
- Executive summary — your notes, rendered from Markdown.
- Findings, grouped by severity — every finding on its own card with input, output, source attribution, tags, and status.
- Targets index — every unique entity (domain, IP, email, etc.) seen across the findings, with the count of findings each entity appears in.
- Source citations — full list of public sources the toolkit queried, with the count of findings each source contributed to.
The PDF is dark-themed by default; a light variant is available in export settings.
The PDF is generated locally. The toolkit never uploads your profile data anywhere to render the PDF — the output bytes are produced on your machine.
Per-tool details in JSON exports
JSON exports preserve every field the tool returned, including fields the UI elects to summarise. This is intentional. If you want to script against the result later — diffing two scans of the same target, for example — the JSON has everything.
The JSON envelope shape per finding:
tool— stable tool identifier.input— exact input used.value— full structured output.warnings— soft issues during the run.meta— duration, timestamp, sources queried, the user-agent string used.
This shape is stable across releases. Old exports remain readable.
CSV flattening
Some tools produce nested output (list of records, each with sub-fields). CSV flattens these to rows. Sub-fields become column-suffixed columns. Lists become semicolon-joined cells.
For tools where this flattening loses fidelity (deeply nested results), the JSON or Markdown export is the better choice.
Markdown for reports
The Markdown export is intentionally readable — section headers per finding, source attribution as italicised footers, severity badges as text. Drop it into any Markdown-aware editor and it renders cleanly.
If your editor supports table syntax, multi-row tool outputs (subdomain lists, port lists) render as tables. Otherwise they render as bullet lists.
What does not export
- Notes that you have not saved. Save the profile before exporting.
- In-progress batches. Cancel or wait for completion before exporting.
- Recent runs that are not pinned. Recent-runs is a tool-page convenience; only pinned findings reach the profile and the export.
Re-running an export
Exports are reproducible. The same profile exports identically twice in a row, modulo the export timestamp on the cover page. This makes the PDF defensible — anyone who runs the same export gets the same bytes.