Performance Tuning
Optimize reconFTW for your target size, hardware, and time constraints.
Quick Tuning Profiles
Copy-paste these configurations based on your scenario:
Small Target (< 100 subdomains)
# In reconftw.cfg - Small target, thorough scan
# Enable DEEP mode (more thorough)
DEEP=true
DEEP_LIMIT=500
DEEP_LIMIT2=2000
# Moderate threads (don't overwhelm small infra)
HTTPX_THREADS=50
FFUF_THREADS=40
NUCLEI_RATELIMIT=100
# Enable all checks
NUCLEICHECK=true
FUZZ=true
CORS=true
XSS=true
SQLI=true
# Time estimate: 1-2 hoursMedium Target (100-1,000 subdomains)
Large Target (1,000-10,000 subdomains)
Massive Target (10,000+ subdomains)
Understanding DEEP Mode
DEEP mode runs additional checks when target size is below threshold.
How It Works
What DEEP Mode Enables
Permutations
Basic
AI + Regex permutations
Fuzzing
Top dirs only
Full wordlist
JS Analysis
Extract endpoints
Full secret scanning
Nuclei
Critical/High only
All severities
Parameter discovery
Skip
Full discovery
Configuring DEEP Limits
Thread Optimization
By Tool
HTTPX_THREADS
50
10
200
HTTP probing
FFUF_THREADS
40
10
100
Directory fuzzing
NUCLEI_RATELIMIT
150
30
500
Vuln scanning (req/sec)
DALFOX_THREADS
200
50
500
XSS testing
TLSX_THREADS
1000
200
2000
TLS analysis
RESOLVE_DOMAINS_THREADS
150
50
300
DNS resolution
By Hardware
1 CPU / 1GB RAM
0.5x
HTTPX_THREADS=25
2 CPU / 4GB RAM
1x (default)
HTTPX_THREADS=50
4 CPU / 8GB RAM
2x
HTTPX_THREADS=100
8+ CPU / 16GB+ RAM
3-4x
HTTPX_THREADS=200
Memory Considerations
High-memory tools:
nuclei- Keep under 200 ratelimit on low-memory systemsffuf- Reduce threads on large wordlistskatana- Can be memory-intensive on large sites
Rate Limiting Strategies
Adaptive Rate Limiting
Manual Rate Limiting
When to Reduce Rates
429 errors
Reduce ratelimit by 50%
Connection timeouts
Reduce threads
WAF blocks
Use --adaptive-rate, reduce to 30 req/sec
Server errors (5xx)
Reduce threads AND ratelimit
Timeout Configuration
Wordlist Optimization
Subdomain Wordlists
subdomains.txt (default)
~100K
Standard scans
subdomains_n0kovo_big.txt
~1M
DEEP mode / thorough
Custom small list
~10K
Fast scans / CI/CD
Fuzzing Wordlists
Small (~5K)
Fast
5-10 min/target
Medium (~20K)
Moderate
20-40 min/target
Large (~100K+)
Slow
1-2 hours/target
Recommended Wordlists
Module-Specific Tuning
Nuclei Optimization
Subdomain Enumeration
Fuzzing
Axiom Scaling
Fleet Sizing
< 100 subs
3-5
30 min
100-1000
5-10
1-2 hours
1000-10000
10-20
2-4 hours
10000+
20-50
4-8 hours
Cost Optimization
Fleet Configuration
Time Estimates
By Mode
-p (passive)
5-10 min
10-20 min
20-40 min
-s (subs)
15-30 min
30-60 min
1-2 hours
-r (recon)
30-60 min
1-3 hours
3-6 hours
-a (all)
1-2 hours
2-5 hours
5-12 hours
Speed vs Thoroughness
Parallelization
reconFTW includes built-in parallelization to speed up reconnaissance by running independent operations concurrently.
Enabling Parallelization
Parallelization Phases
Subdomain enumeration is organized into phases with dependencies:
Configuration Variables
Performance Impact
Small (<100)
15 min
8 min
~2x
Medium (100-1K)
45 min
20 min
~2.2x
Large (1K-10K)
3 hours
1.5 hours
~2x
Parallel Functions Reference
parallel_passive_enum()
Run passive sources in parallel
4
parallel_active_enum()
Run active DNS checks in parallel
3
parallel_postactive_enum()
TLS and analytics after resolution
2
parallel_brute_enum()
Brute force (resource limited)
2
parallel_web_vulns()
Web vulnerability checks
4
parallel_injection_vulns()
Injection testing
4
parallel_osint()
OSINT gathering
4
When NOT to Use Parallelization
Low-memory systems (< 4GB RAM): Use sequential mode
Rate-limited targets: Parallel can trigger blocks faster
Axiom mode: Already distributed, parallelization adds complexity
Debugging: Sequential is easier to troubleshoot
Common Tuning Scenarios
"I need results in 30 minutes"
"Overnight scan, make it thorough"
"Bug bounty, new program rush"
"Red team, need to stay quiet"
Monitoring Performance
Check Progress
Resource Monitoring
TL;DR Quick Config
Documentation Info Branch:
dev| Version:v3.0.0+| Last updated: February 2026
Last updated