Many ReconNinja modules work without any API keys. Keys are only required to unlock specific integrations or raise rate limits.

All of these work out of the box with no API keys:

• WHOIS (--whois)
• Wayback Machine (--wayback)
• SSL analysis (--ssl)
• Subdomain enumeration (--subdomains)
• Port scanning (RustScan, Nmap, Masscan)
• Directory brute-force (--ferox)
• WAF detection (--waf)
• CORS scanner (--cors)
• DNS zone transfer (--dns-zone)
• JS extraction (--js-extract)
• Cloud bucket enumeration (--cloud-buckets)
• GitHub OSINT without token (60 req/hr limit)
• Email security (--email-security)
• Breach check domain level (--breach-check)
• GraphQL scanner (--graphql)
• JWT scanner (--jwt-scan)
• ASN / BGP map (--asn-map)
• Supply chain scan (--supply-chain)
• K8s / Docker probe (--k8s-probe)
• DB exposure scan (--db-exposure)
• SMTP enumeration (--smtp-enum)
• SNMP scan (--snmp-scan)
• LDAP enum (--ldap-enum)
• DevOps scan (--devops-scan)
• GreyNoise community tier (--greynoise)
• Typosquat detection (--typosquat)
• AI with Ollama (--ai --ai-provider ollama)
• All v8 modules except those that call external APIs

Use a .env file in the repo root (already in .gitignore):

# .env
SHODAN_KEY=your_key_here
VT_KEY=your_key_here
GROQ_KEY=your_key_here
GITHUB_TOKEN=your_token_here

Then reference them in your shell:

reconninja -t example.com \
  --shodan --shodan-key $SHODAN_KEY \
  --vt --vt-key $VT_KEY \
  --ai --ai-provider groq --ai-key $GROQ_KEY \
  --github-osint --github-token $GITHUB_TOKEN \
  -y

• All-Flags — all flags that accept API keys
• AI-Analysis — AI provider key setup