Download the toolkit
A practical, evidence-first incident response helper for clearnet OSINT, breach exposure checks (where permitted),
and structured incident documentation. Built for quick triage โ without dark web crawling.
๐ป Installer (recommended)
Best for most customers. Installs shortcuts and makes repeat runs easy.
- Simple install + Start Menu shortcut
- Ideal for office PCs and recurring checks
- Works great with โRun (Recommended)โ wrapper
Tip: Use the installer if you want a smooth โclick-to-runโ experience.
๐งฐ Portable ZIP (call-out friendly)
No install. Ideal for engineers and quick on-site triage.
- Unzip โ run โ collect evidence
- Perfect for USB toolkit use
- Includes the โRun_Triageโ helper
Tip: Portable is the fastest โarrive โ run โ evidenceโ option.
๐ User Guide (PDF)
Clear steps for customers + technical users (EN + NL).
- How to fill in case details
- Which checks to enable (and why)
- Safety + privacy tips included
Want help? Use our contact page for support or deployment guidance.
๐ Quick start (how to use)
Installer route
- Download and run the installer.
- Open Start Menu โ Run (Recommended).
- Enter a Case Name (example: ACME-2026-02-26).
- Enter Customer/Company.
- Add emails/domains/usernames (comma-separated).
- Type YES to confirm consent.
- Run the checks you need and review the evidence pack.
Portable route
- Download the ZIP and extract it.
- Run Run_Triage.cmd (recommended).
- Follow the prompts and select checks.
- When finished, open the output folder and share only whatโs necessary.
Safety tip: Always enable Redact PII when sharing evidence externally.
โ What itโs for
- Incident triage: โWhatโs exposed and where?โ
- Breach & paste exposure checks (where legally allowed / API-based)
- Passive recon for domains (DNS / WHOIS / certificate transparency)
- Evidence-first reporting for documentation and follow-up actions
๐ซ What it does not do
- No dark web crawling and no .onion scanning
- No exploitation, โhackingโ, or intrusive scanning
- No downloading of leaked content by default (metadata/references only)
Use it for defensive triage with explicit customer consent and clear scope.
๐ Safety & privacy tips (worth doing every time)
- Consent first: confirm customer authorization and scope before running any checks.
- Prefer app-based MFA: avoid SMS MFA if SIM-swap risk is suspected.
- Check email rules: attackers often add forwarding rules after takeover.
- Evidence handling: store case folders securely and follow a retention policy.
- Redact PII: enable redaction when evidence may be shared outside the org.
you can mirror the files and update the buttons accordingly.
