01 / Research workflows

Analysis desk

Open the task that matches the material in front of you. Files, URLs, mail headers, logs, and checksums are examined here before any separate network lookup is considered.

FilesThe file page reads bytes selected from this device and does not execute them.

URLs and mailParsers inspect text and structure without opening the destination or performing DNS lookups.

ExportsDownloaded summaries keep findings and counts while omitting raw sensitive material.

File analysis

Organize a single local file first, then decide whether a separate authorized flow is needed.

Input
Single local file
Output
Hashes, type clues, indicator counts, share-safe summary
Boundary
No upload, no execution, no third-party request
Open file analysis

URL analysis

Inspect URL structure, IDN/Punycode, Safe Links, and defang/refang without visiting the target.

Input
URL or defanged URL
Output
Structure, IDN, Safe Links, sensitive keys, share-safe summary
Boundary
No target request or network validation
Open URL analysis

Email analysis

Parse headers or .eml text locally before moving links or observables into other tasks.

Input
Headers or .eml text
Output
Received chain, authentication header facts, links, share-safe summary
Boundary
No upload, no DNS verification
Open email analysis

IOC extraction

Extract observables from logs, alerts, and reports for clean handoff and review.

Input
Logs, alerts, reports
Output
Normalized observables, dedupe, defang/refang, redactions
Boundary
No third-party lookup; observations only
Open IOC extraction

Checksum comparison

Normalize hashes and compare checksums locally before sharing an investigation target.

Input
MD5/SHA values or checksum list
Output
Type detection, dedupe, expected/file/manifest compare
Boundary
No lookup by default
Open checksum comparison

What these pages do

Browser workParsing, hashing, normalization, and report assembly happen in the current page.

Application logsPasted values and selected file bytes are not sent to the application backend.

Separate lookupsA future network lookup must be a distinct, explicit action that names its destination and submitted fields.