recon-a-domain-passively

Builds an attributed asset inventory of a domain's internet-facing estate using only passive data sources.

38|2|Updated Aug 2, 2026
One-click install
npx skills add https://github.com/UseOSINT/Skills --skill recon-a-domain-passively-useosint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recon-a-domain-passively
Source: https://github.com/UseOSINT/Skills/tree/main/skills/recon-a-domain-passively
Command: npx skills add https://github.com/UseOSINT/Skills --skill recon-a-domain-passively-useosint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Mapping an organization's domains, subdomains, infrastructure, and ownership without alerting the target is hard to do rigorously — investigators either enumerate endlessly with no attribution, or accidentally send traffic to the target and lose the passive claim. This Skill provides the ordering, inventory schema, and stopping criteria for a defensible passive reconnaissance engagement. ## Core Features & Use Cases - Ordered six-stage workflow: registration and DNS baseline, subdomain expansion via Certificate Transparency and passive DNS, resolution and inventory, third-party scan-data infrastructure mapping, archived content and code review, then owner attribution. - Asset inventory schema: a reference-defined row format capturing source, first-seen date, resolution, ASN, services, tech stack, and a separate confidence grade for liveness versus ownership. - Explicit stopping rule and completeness worksheet: five saturation and coverage criteria that decide when the map is done, plus written limitations for gaps like wildcard certificates. - Use Case: During M&A technical diligence on a company, run the workflow against its apex domain to produce a prioritized inventory of hosts, exposed services, SaaS vendors, and a sibling domain discovered through certificate-subject search — all without touching the target's servers. ## Quick Start Ask the agent to passively recon example.com and produce an attributed asset inventory with confidence grades and sources.

Frequently Asked Questions about recon-a-domain-passively

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map a domain's subdomains and infrastructure passively?▼

Start with WHOIS and DNS records, then expand names through Certificate Transparency logs and passive DNS, resolve candidates, and enrich with third-party scan data from platforms like Shodan. None of these sources send traffic to the target, keeping the reconnaissance passive.

What is the difference between passive and active reconnaissance?▼

Passive reconnaissance uses only third-party datasets such as CT logs, archives, and scan platforms, never contacting the target. DNS resolution, wordlist brute-forcing, and HTTP probing sit on a spectrum toward active, so the permitted boundary must be defined in writing before starting.

How do I know when subdomain enumeration is complete?▼

Completeness is judged by criteria, not exhaustion: two consecutive new sources produce no new assets, every name is resolved or classified, naming-convention gaps are explained, and every discovered vendor has been chased. Wildcard certificates or DNS records must be stated as limitations.

Why attribute assets separately from confirming they are live?▼

A host can be a confirmed live service but an unconfirmed asset of the target — shared hosting, CDN addresses, and bundled certificates attach infrastructure that is not the target's. Grading liveness and ownership separately prevents the most common reporting error in domain recon.

Is passive OSINT collection on domains legal?▼

Passive collection from third-party datasets is lawful research in most jurisdictions; the boundary is traffic to the target and access to non-public systems. Historical WHOIS data is personal data under GDPR, requiring a lawful basis and minimization, and engagements need written authorization for the scope.