Skip to main content

Domain intelligence CLI and MCP server — tech stack, email security, and signal intelligence from DNS.

Project description

recon

CI PyPI Python License OpenSSF Scorecard

Passive domain intelligence from public sources. recon reads public DNS, certificate transparency, and unauthenticated Microsoft and Google identity discovery endpoints to report what an organization appears to publish about its identity stack, email posture, SaaS footprint, and related domains.

It uses no credentials, no API keys, no paid feeds, and no active scanning. It is a local Python CLI, importable library, JSON producer, and stdio MCP server. It is not a hosted service, scheduler, vulnerability scanner, company research tool, or firmographic database.

Defensive use only. Use recon for legitimate posture review, IT architecture review, vendor diligence, and defensive hardening. See docs/legal.md for the intended-use policy.

Quick Start

Install or update with the platform script:

Windows (PowerShell):

powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/blisspixel/recon/main/scripts/install.ps1 | iex"

macOS or Linux:

curl -fsSL https://raw.githubusercontent.com/blisspixel/recon/main/scripts/install.sh | bash

Open a new terminal and verify the install:

recon doctor

Run a lookup:

recon contoso.com

Example output shape:

Contoso Ltd
contoso.com

Provider     Microsoft 365 via Proofpoint gateway
Tenant       a1b2c3d4-e5f6-7890-abcd-ef1234567890
Auth         Federated
Confidence   High (4 sources)

Services
  Email       Microsoft 365, Proofpoint, DMARC, DKIM, SPF strict
  Identity    Okta, Entra ID
  Cloud       Cloudflare, AWS Route 53

Insights
  Federated identity indicators observed
  Email security 4/5: DMARC reject, DKIM, SPF strict, BIMI
  Email gateway: Proofpoint in front of Exchange

Examples use Microsoft's fictional company names. Tenant IDs, services, and domains in examples are fabricated. No real company is depicted.

For detailed install, update, uninstall, and first-run workflows, read docs/getting-started.md.

What recon Is Good For

Need Use recon for Use something else when
Fast external stack context Passive DNS, identity-endpoint, CT, SaaS, and posture indicators You need authenticated tenant inventory or asset-management truth
Defensive review or vendor diligence Hedged observations and evidence traces you can verify You need vulnerability scanning, exploit checks, or host-level facts
Automation-friendly output Stable JSON, batch mode, delta mode, and local MCP tools You need dashboards, scheduling, or report generation built in

recon reports observations, not verdicts. A missing DMARC record is a missing record. A Microsoft 365 tenant indicator is an observed indicator. The operator decides what those facts mean in context.

Common Commands

recon contoso.com                              # default panel
recon https://www.contoso.com/path             # normalize URL to apex
recon mail.contoso.com                         # reduce sub-host to apex
recon mail.contoso.com --exact                 # keep that literal host
recon contoso.com --explain                    # reasoning and provenance
recon contoso.com --full                       # services, domains, posture
recon contoso.com --json                       # structured lookup record
recon batch domains.txt --json                 # batch JSON array
recon batch domains.txt --ndjson               # one record per line
recon batch domains.txt --summary              # aggregate-only cohort summary
recon delta contoso.com                        # diff against cached snapshot
recon mcp install --client=cursor              # wire MCP into a client
recon mcp doctor                               # live MCP handshake check

Built-in posture profiles: fintech, healthcare, saas-b2b, high-value-target, public-sector, and higher-ed. Custom profiles live in ~/.recon/profiles/*.yaml.

Generated command and flag reference: docs/cli-surface.md.

How recon Works

recon reads:

  • DNS records: MX, TXT, SPF, DMARC, DKIM, BIMI, CNAME, NS, SRV, and CAA.
  • Certificate transparency: SAN names, issuers, issuance timing, and bounded related-domain hints.
  • Identity discovery: unauthenticated Microsoft and Google endpoints.

By default, the only request the queried domain's own servers see is the standards-based MTA-STS policy fetch at mta-sts.<domain>. Google CSE and BIMI VMC direct probes are opt-in behind --direct-probes.

The engine then maps observables to fingerprint slugs, derived signals, graph motifs, and optional Bayesian posteriors. Sparse public evidence stays sparse: the result widens uncertainty or lowers confidence instead of inventing a clean answer.

Long-form explanation: docs/how-it-works.md. Formal model: docs/correlation.md.

JSON and Automation

recon <domain> --json emits a stable single-domain lookup object. Batch and delta modes emit different shapes, so route by mode or by record_type.

recon contoso.com --json
recon batch domains.txt --json
recon batch domains.txt --ndjson
recon delta contoso.com --json

Read these before building an integration:

docs/surface-inventory.json, docs/cli-surface.md, and recon://surface-inventory are generated discovery context and drift guards, not stable runtime API contracts. ADR-0007 records the promotion gate for any future stable subset.

MCP Server

The default install includes a local stdio MCP server for MCP-compatible tools. Start with manual approvals and an empty autoApprove list. Treat connected agents as untrusted input.

recon mcp install --client=claude-desktop
recon mcp install --client=cursor --dry-run
recon mcp doctor

The installer writes the right per-client config shape and preserves sibling MCP servers. Full setup, tool list, read-only versus stateful guidance, and troubleshooting live in docs/mcp.md. Per-client scaffolds live in agents/.

Limitations

The public channel has a ceiling:

  • Internal-only workloads are invisible.
  • SaaS products without DNS verification records may not appear.
  • Email gateways can hide the downstream mailbox provider.
  • CT logs can be stale, partial, rate-limited, or absent.
  • Fingerprints are rule-based indicators, not proof of active use.

Read docs/limitations.md before using recon output for a high-stakes decision. Read docs/data-handling-policy.md before committing any validation artifact.

Documentation

Current Maintainer Focus

The next work is not a runtime expansion. The CT-enabled C3 validation track is closed as a bounded, private, aggregate-only partial CT pass, and fingerprint or motif growth has no active public-source-backed candidate. The current focus is external write-up readiness: keep citation metadata current, prove the public reproduction path, and map paper claims to public, synthetic, or aggregate-only evidence without adding commands, schema fields, network sources, or catalog rules. The detailed plan lives in docs/external-writeup-plan.md.

Development

uv sync
pre-commit install
uv run python scripts/release_readiness.py --allow-dirty
uv run python scripts/check.py

python scripts/check.py is the local CI mirror. It runs lint, type checks, coverage-gated tests, generated-artifact checks, validation hygiene, and ratchets. Do not push on --fast alone.

House rules: no AI attribution, no em-dashes or emojis, no real-company data in public examples or validation artifacts, no dead code, and no placeholders. Contributor details: CONTRIBUTING.md.

License

Apache 2.0. Free to use, build on, fork, and share. See LICENSE for the full terms.

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

recon_tool-2.2.15.tar.gz (2.1 MB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

recon_tool-2.2.15-py3-none-any.whl (582.9 kB view details)

Uploaded Python 3

File details

Details for the file recon_tool-2.2.15.tar.gz.

File metadata

  • Download URL: recon_tool-2.2.15.tar.gz
  • Upload date:
  • Size: 2.1 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.13

File hashes

Hashes for recon_tool-2.2.15.tar.gz
Algorithm Hash digest
SHA256 f1207ef6c833ece02cceecadcf1d5167dbdd80bb94b97e7606aaa938149c2541
MD5 bd7be9d4039664b4c197e754af03237f
BLAKE2b-256 6a48c2e9eda729f5bef08e80a1092e8b5a7be9a5ba735174a49323d506a2bf24

See more details on using hashes here.

Provenance

The following attestation bundles were made for recon_tool-2.2.15.tar.gz:

Publisher: release.yml on blisspixel/recon

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file recon_tool-2.2.15-py3-none-any.whl.

File metadata

  • Download URL: recon_tool-2.2.15-py3-none-any.whl
  • Upload date:
  • Size: 582.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.13

File hashes

Hashes for recon_tool-2.2.15-py3-none-any.whl
Algorithm Hash digest
SHA256 f6ce947228a4318b8ceff45e971cf5a82fe678b6025b968a700dd2c25046f937
MD5 74f8f52a2f86f5ebd5fd1815b040ba16
BLAKE2b-256 29b106da1b29691959d5e0fc5d880feb925d3083d67fa376818244620bdcfa46

See more details on using hashes here.

Provenance

The following attestation bundles were made for recon_tool-2.2.15-py3-none-any.whl:

Publisher: release.yml on blisspixel/recon

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page