Use case

Supplier and third-party research

Collect public company, domain, software and infrastructure context before a supplier decision.

Starting targetCompany name or known public domain
Useful depthsBalanced, Deep Research
Recommended planPro for regular due diligence; Custom for contract capacity and procurement needs.

Likely evidence

  • Public company and domain records
  • Web, certificate and mail posture
  • Software, cloud and public-code context

Graph relationships

  • Company associated with domain
  • Domain connected to service
  • Software observed on public surface

Expected outputs

  • Public-footprint summary
  • Candidate relationship graph
  • Review report and export

Safety boundary

Evidence still needs judgment.

Shared infrastructure and related domains remain candidates until corroborated.

This workflow is explanatory, not a scan profile or guarantee of discovery. Target compatibility, registry readiness, configuration, scope and budget determine the exact plan.

Start with a target

Turn this workflow into an explainable investigation.

Create an account to plan your first evidence-backed investigation, or talk to us about team and workflow requirements.