FAQ

Common questions about TargetHunt answered directly.

Quick answers about scanning scope, account setup, reports, safety controls, workspaces, and demos.

targethunt faq --answers concise

Scope

Domain

Reports

PDF

Access

Workspace

Live control surface
What can I scan?
What does the report include?
How do workspaces work?

Scanning

What can I scan?

You should scan only domains and applications you own or are explicitly authorized to test. TargetHunt keeps scans domain-bound.

  • Owned domains
  • Authorized testing
  • Scoped projects

Reports

What does a report include?

Reports include risk scoring, findings, standards mapping, evidence, clean checks, methodology, request estimates, and limitations.

  • Safe score
  • Evidence workbook
  • PDF output

Accounts

Do I need a workspace?

Yes. Accounts use workspaces to separate projects, scans, memberships, reports, and commercial controls.

  • Default workspace
  • Membership roles
  • Project access

Safety

Does TargetHunt keep raw scanner data?

The platform is designed to persist normalized evidence and avoid retaining raw secrets, auth material, raw bodies, and tool dumps.

  • Normalized evidence
  • Redacted metadata
  • Bounded runtime
Operator notes

Still have a specific question?

Send details about your target type, scan goals, and reporting needs, and the team can answer directly.

Product fit
Demo flow
Workspace setup
Report requirements

Get a clear answer before you scan.

Contact the team or book a demo if your workflow has special scope or reporting requirements.

Start scan