Use case

Email and TLS posture review

Review mail routing, authentication policy, HTTPS, headers and certificate evidence without overstating risk.

Starting targetAuthorized domain, hostname, email address or URL
Useful depthsQuick, Balanced
Recommended planStandard for core review; Pro for configured enrichment and deeper correlation.

Likely evidence

  • MX, SPF and DMARC records
  • MTA-STS policy where permitted
  • TLS certificate and HTTP header context

Graph relationships

  • Domain uses mail exchanger
  • Certificate secures service
  • Policy applies to domain

Expected outputs

  • Mail and TLS posture summary
  • Reviewable findings
  • Evidence-linked report

Safety boundary

Evidence still needs judgment.

Expected negatives and unassessed components are not proof of a weakness.

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.