← ClaudeAtlas

recon-osintlisted

Use at the start of any authorized red-team or pentest engagement to map the target's attack surface — passive OSINT (domains, subdomains, certs, DNS, ASN/IP ranges, leaked credentials, employees, tech stack) and active recon (port/service discovery, web asset enumeration). Produces a scoped attack-surface inventory feeding the domain-specific pentest skills. Authorized engagements only.
noahfranklin/gideon · ★ 2 · AI & Automation · score 70
Install: claude install-skill noahfranklin/gideon
# Reconnaissance & OSINT The first phase of every engagement: understand the target's real attack surface before touching it hard. Passive recon leaves no footprint on the target; active recon interacts and must stay strictly in scope. ## 0. Authorization gate - [ ] Written scope: in-scope domains, IP ranges/ASNs, cloud accounts, apps. - [ ] Explicit out-of-scope assets and third parties (never recon a provider you aren't cleared for). - [ ] Rules on active scanning (rate, hours, allowed tooling). - [ ] OSINT-on-people rules (many programs restrict employee targeting). ## 1. Passive OSINT (no target interaction) - **Domains & subdomains:** certificate transparency logs, passive DNS, subdomain enumeration from public sources; brand/typo domains. - **IP/ASN footprint:** ASN lookups, netblock ownership, cloud IP attribution. - **DNS records:** A/AAAA/MX/TXT/SPF/DMARC/CNAME; zone data from public sources. - **Tech fingerprinting:** frameworks, CDNs, WAFs, versions from public pages/headers. - **Exposure:** public code repos, cloud storage buckets, exposed dashboards, internet-scan datasets, paste sites. - **People & creds:** employees/roles, email formats, breach-corpus credential exposure (for spray/reuse testing when in scope). - **Documents/metadata:** public files and their metadata (authors, software, internal paths). ## 2. Active recon (in-scope interaction) - **Host discovery:** which in-scope hosts are alive. - **Port/service scanning:** TCP/UDP, service + version det