// why automate recon

Manual recon is the bottleneck

The reconnaissance phase is the most time-consuming part of a bug bounty engagement. Running Subfinder, piping results into httpx, then manually kicking off Nmap, then Nuclei, then FFUF — each step takes time to configure, execute, and collect. On a large scope with hundreds of subdomains, a full manual recon pass can take an entire day.

Automation solves this by chaining tools in a pipeline: each tool's output becomes the next tool's input, running sequentially or in parallel. The result is a structured finding set in 15–45 minutes instead of 4+ hours — and you can run it against multiple targets simultaneously.

PhantomRed runs this full pipeline automatically server-side. But if you want to build your own automation stack, here is the exact workflow, tool by tool.


// the recon stack

Tools in the automation pipeline

Each tool handles a specific phase of reconnaissance. Together they cover the full external attack surface.

Subfinder
SUBDOMAIN ENUM

Discovers subdomains using passive sources — certificate transparency logs, DNS records, threat intel APIs. Fast and non-intrusive.

Amass
SUBDOMAIN ENUM

Deep subdomain enumeration using both passive and active techniques. Slower than Subfinder but finds more targets on large scopes.

httpx
LIVE HOST DETECTION

Probes discovered subdomains to identify which are live, returning status codes, titles, and tech stack hints.

Nmap
PORT + SERVICE SCAN

Scans open ports, identifies running services, detects software versions, and runs default NSE scripts for quick vulnerability hints.

Nuclei
CVE + MISCONFIGURATION

Runs 9000+ community and official templates to detect CVEs, exposed panels, misconfigured headers, and known vulnerability patterns.

FFUF
PATH + PARAM FUZZING

Discovers hidden directories, backup files, API endpoints, and unlinked admin panels via wordlist-based fuzzing.

SQLMap
INJECTION TESTING

Tests discovered endpoints for SQL injection vulnerabilities using automated payload injection and response analysis.

theHarvester
OSINT

Collects email addresses, employee names, hostnames, and open ports from public sources like Google, LinkedIn, and Shodan.


// step-by-step pipeline

The automated recon pipeline, step by step

This is the exact workflow PhantomRed runs server-side. If you are building your own automation, follow these steps in order — each feeds into the next.

01

Subdomain enumeration

Start by discovering all subdomains in scope. Subfinder uses passive sources (cert transparency, DNS APIs). Amass adds active brute-forcing for deeper coverage. Pipe both into httpx to filter for live hosts only.

# Passive subdomain discovery subfinder -d target.com -o subdomains.txt # Pipe live hosts through httpx cat subdomains.txt | httpx -silent -o live_hosts.txt
02

Port and service discovery

Run Nmap against your live hosts to identify open ports, running services, and software version strings. The -sV flag detects service versions; -sC runs default NSE scripts for quick wins like anonymous FTP or open HTTP directories.

# Service version detection + default scripts nmap -sV -sC -iL live_hosts.txt -oN nmap_output.txt # Fast scan for top 1000 ports first nmap -F -iL live_hosts.txt -oN nmap_fast.txt
03

CVE and misconfiguration scanning with Nuclei

Nuclei runs community and official templates against your live hosts to detect known CVEs, exposed admin panels, default credentials, misconfigurations, and outdated software. This is often where the highest-impact findings come from without any manual effort.

# Run all templates against live hosts nuclei -l live_hosts.txt -o nuclei_findings.txt # Filter by severity — critical and high first nuclei -l live_hosts.txt -severity critical,high -o nuclei_critical.txt
04

Directory and path fuzzing with FFUF

FFUF discovers hidden paths — admin panels, backup files, config endpoints, unlinked API routes — that don't appear in normal browsing. Use a quality wordlist like SecLists' common.txt or raft-medium-directories.txt for best coverage.

# Directory fuzzing against a target ffuf -w /path/to/wordlist.txt -u https://target.com/FUZZ \ -mc 200,301,302,403 -o ffuf_paths.json # Parameter fuzzing ffuf -w params.txt -u https://target.com/page?FUZZ=test \ -mc 200 -o ffuf_params.json
05

SQL injection testing with SQLMap

Feed endpoints discovered in previous steps into SQLMap to test for SQL injection. Start with --batch to run non-interactively, and --level 2 for slightly deeper testing without being too noisy.

# Test a specific endpoint sqlmap -u "https://target.com/page?id=1" --batch --level 2 # Test from a file of URLs sqlmap -m endpoints.txt --batch --level 2 -o sqli_output/
06

AI triage and risk scoring

With dozens or hundreds of raw findings across tools, manual triage becomes a bottleneck. An AI layer can process all tool outputs, deduplicate related findings, assign severity-weighted risk scores, and produce a structured report — turning hours of triage into minutes.

# PhantomRed runs steps 01–06 automatically # and adds AI analysis on top of all findings # Submit target → get risk-scored report → phantomred.com/dashboard

// pro tips

Tips for effective recon automation

Always check scope boundaries first

Before running any scanner, read the program's rules of engagement carefully. Identify which subdomains, IP ranges, and endpoints are explicitly in scope. Never scan out-of-scope assets — it can get you banned or create legal liability.

Rate-limit your scans

Aggressive scanning can trigger WAFs, IP bans, or program disqualification. Use Nmap's -T3 timing, add --rate limits to FFUF, and avoid running multiple heavy scans against the same host simultaneously.

Use the right Nuclei template sets

Don't run every Nuclei template blindly — use severity filters (-severity critical,high) for initial passes. The -tags cve and -tags misconfig filters are high signal-to-noise for bug bounty work.

Save raw outputs for later analysis

Always write tool outputs to files with -o or -oN flags. Raw outputs are useful for re-analysis, sharing with a team, or feeding into AI triage tools. Structure your output directory by target and date.

Run Subfinder before Nmap

Subdomain enumeration expands your attack surface significantly before port scanning. Running Nmap directly against a root domain misses dozens of subdomains with their own open ports and services.

Let PhantomRed handle the pipeline

If you don't want to manage the toolchain locally — installations, wordlists, template updates, output parsing — PhantomRed runs the full pipeline server-side and delivers a structured, AI-analyzed report. Free tier includes 3 scans/month.


// faq

Frequently asked questions

The standard recon automation stack is: Subfinder or Amass for subdomain enumeration, httpx for live host detection, Nmap for port and service discovery, Nuclei for CVE and misconfiguration scanning, FFUF for path and parameter fuzzing, and SQLMap for SQL injection testing. PhantomRed chains all of these automatically in a single server-side workflow.
A full automated pipeline on a medium-sized scope (50–200 subdomains) typically takes 20–45 minutes. A manual execution of the same workflow takes 2–4 hours. Scan time varies based on number of live hosts, open ports, and Nuclei template count. PhantomRed runs the pipeline server-side so it doesn't consume your local resources.
Most bug bounty programs permit automated scanning against in-scope targets. Always read the program's rules of engagement before scanning. Some programs restrict certain scan types, limit request rates, or exclude specific subdomains. Never scan out-of-scope assets — it can result in a ban or legal action.
For general directory fuzzing, SecLists' raft-medium-directories.txt and common.txt are high-signal starting points. For API endpoint discovery, use api_endpoints.txt from SecLists. For parameter fuzzing, burp-parameter-names.txt works well. You can install SecLists via: git clone https://github.com/danielmiessler/SecLists.git
For the external recon and initial scanning phase, yes. PhantomRed runs Nmap, Nuclei, FFUF, and SQLMap server-side — no local installation, no wordlist management, no template updates. For manual exploitation, authenticated scanning, or custom toolchain integrations, you will still need local tools. PhantomRed is designed to handle the automated first pass so you can focus on manual testing.

// related guides

Dive deeper into the tools and workflows that power autonomous penetration testing.

How to Automate Bug Bounty Recon Nmap + Nuclei + FFUF Automation PhantomRed vs Burp Suite PhantomRed vs OWASP ZAP

// skip the setup

Run the full recon pipeline automatically

PhantomRed chains Nmap, Nuclei, FFUF, and SQLMap server-side. Submit a target and get a risk-scored report in minutes. Free tier — no credit card required.

Try PhantomRed Free → View Hunter Profile ↗