Reconnaissance & OSINT Automation
Passive and active reconnaissance, subdomain enumeration, DNS analysis, technology fingerprinting, and OSINT data correlation for authorized security assessments
Masriyan · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Masriyan/Claude-Code-CyberSecurity-Skill --skill Reconnaissance & OSINT Automation技能说明
name: Reconnaissance & OSINT Automation description: Passive and active reconnaissance, subdomain enumeration, DNS analysis, technology fingerprinting, and OSINT data correlation for authorized security assessments version: 3.0.0 author: Masriyan tags: [cybersecurity, reconnaissance, osint, enumeration, dns, subdomain, fingerprinting]
Reconnaissance & OSINT Automation
Purpose
Enable Claude to conduct comprehensive reconnaissance and open-source intelligence gathering during authorized security assessments. Claude performs passive and active recon using its native analysis capabilities and orchestrates the included scripts for automation at scale.
Authorization Required: Always confirm written authorization for the target scope before proceeding. Unauthorized reconnaissance is illegal in most jurisdictions.
Activation Triggers
This skill activates when the user asks about:
- Subdomain enumeration or discovery
- DNS reconnaissance, zone transfers, or DNS record analysis
- OSINT gathering on a domain, organization, or person
- Technology fingerprinting or stack identification
- Port scanning, service detection, or banner grabbing
- Google dorking or advanced search query generation
- WHOIS, certificate transparency, or Shodan queries
- Attack surface mapping or perimeter discovery
Prerequisites
pip install requests dnspython python-whois beautifulsoup4 shodan
Optional enhanced capabilities:
nmap— Active port scanningamass— Advanced subdomain enumerationtheHarvester— Email and domain harvesting- Shodan API key — Internet-wide device search
- Censys API key — Certificate and host search
Core Capabilities
1. Passive Reconnaissance (No Direct Target Contact)
When the user asks for passive recon or OSINT:
- WHOIS Analysis — Query domain registration records for registrant, registrar, nameservers, and dates. Flag privacy-protected registrations and registrar patterns.
- Certificate Transparency Logs — Search crt.sh for all certificates issued to the domain and subdomains. Extract SANs (Subject Alternative Names) to discover hidden subdomains.
- DNS Records (Passive) — Enumerate A, AAAA, MX, NS, TXT, SOA, SRV, and CNAME records using public resolvers. Analyze SPF, DKIM, and DMARC for email security posture.
- Search Engine Dorking — Generate targeted dork queries to discover exposed files, login portals, and configuration leaks:
site:target.com filetype:pdf— Exposed documentssite:target.com inurl:admin— Admin panelssite:target.com ext:env OR ext:config— Config files"@target.com" site:linkedin.com— Employee enumeration"target.com" site:pastebin.com— Credential leaks
- Shodan/Censys Queries — Search for internet-exposed services, open ports, banners, and vulnerabilities associated with the target's IP ranges.
- Git/Code Repository Search — Search GitHub/GitLab for leaked credentials, API keys, and internal information:
org:targetorg api_keyfilename:.env target.com"target.com" password
2. Subdomain Enumeration
When the user asks to enumerate subdomains:
- Certificate Transparency — Extract all SANs from crt.sh/Censys certificates (most effective passive method)
- DNS Brute-Force — Run subdomain_enum.py against the common wordlist in
resources/ - Wildcard Detection — Query random subdomains to detect wildcard DNS responses and filter false positives
- Resolution Validation — Resolve all candidates to IP addresses; discard NXDOMAINs
- HTTP Probing — Check which subdomains respond on ports 80/443; identify web applications
- Infrastructure Grouping — Group discovered subdomains by IP/ASN to map cloud vs. on-prem assets
Output format for subdomain findings:
Target: example.com
Discovery Method: CT Logs + DNS Brute-Force
Discovered: 47 subdomains
LIVE SUBDOMAINS:
admin.example.com → 203.0.113.10 [HTTP 200] [nginx/1.18]
dev.example.com → 203.0.113.11 [HTTP 302 → /login]
api.example.com → 203.0.113.12 [HTTP 200] [cloudflare]
internal.example.com → 10.0.0.5 [No public response — internal?]
INFRASTRUCTURE CLUSTERS:
203.0.113.10-15 → AS12345 (Company Hosting)
Cloudflare CDN → 7 subdomains proxied
3. Active Port Scanning & Service Detection
When the user asks to scan ports or detect services:
- Define scan scope (host, subnet, CIDR range) and confirm authorization
- Select scan technique: SYN scan (requires root), connect scan (no root), or stealth options
- Run top-1000 ports first, then targeted service ports
- Perform service version detection (
-sV) on all open ports - Run OS fingerprinting (
-O) if authorized - Grab banners from discovered services
- Flag services with known vulnerabilities based on version data
Provide Nmap commands ready to run:
# Quick discovery
nmap -sn 203.0.113.0/24
# Top 1000 TCP ports with service detection
nmap -sV -sC --top-ports 1000 -oA scan_results 203.0.113.10
# Full port scan with script engine
nmap -sV -sC -p- -T4 -oA full_scan 203.0.113.10
4. DNS Reconnaissance
When the user asks for DNS analysis:
- Enumerate all record types: A, AAAA, MX, NS, TXT, SOA, SRV, CNAME, PTR
- Zone Transfer Attempt (AXFR) — Try against all discovered nameservers:
dig AXFR @ns1.example.com example.com - Email Security Analysis:
- SPF: Check for
~all(softfail) or?all(neutral) — both are weak - DMARC: Missing DMARC = zero enforcement;
p=none= monitoring only - DKIM: Check selector existence and key strength
- SPF: Check for
- Reverse DNS — PTR lookups on all discovered IPs to find additional hostnames
- DNS History — Check SecurityTrails or PassiveDNS for historical DNS records that may reveal old infrastructure
Flag these misconfigurations:
- Zone transfer allowed → Exposes full DNS zone
- No DMARC record →