Configuration Reference

Documentation for reconFTW dev branch | Variables match reconftw.cfg

This guide provides a complete reference for reconFTW's configuration file (reconftw.cfg), covering every option with detailed explanations.


Configuration Files Overview

reconFTW uses several configuration files:

File
Purpose
Git Tracked

reconftw.cfg

Main configuration

✅ Yes

secrets.cfg

API keys and tokens

❌ No (gitignored)

custom_config.cfg

User overrides (optional)

❌ No

Load Order

  1. reconftw.cfg is loaded first (defaults)

  2. secrets.cfg is sourced if it exists (API keys)

  3. Custom config via -f flag overrides all


General Settings

Tool Paths

Shell Configuration

Version Information

Resolver Settings

When to change:

  • Set generate_resolvers=true for custom resolver validation (slower but more accurate)

  • Set update_resolvers=false if you maintain your own resolver list

Proxy Settings

Usage: Set PROXY=true to route web requests through Burp Suite or similar proxy.

Golang Configuration

Update Settings

Output Settings

Disk Space Check


API Keys and Tokens

Environment Variables (Preferred)

Set these in your shell or secrets.cfg:

secrets.cfg File

Create from the example:

Edit secrets.cfg:

Token Files

Create GitHub tokens file:


Module Toggles

OSINT Module

Subdomain Module

DNS_TIME_FENCE_DAYS

Filters Certificate Transparency (crt.sh) results to certificates issued within the last N days.

Why use this:

  • CT logs contain historical certificates, including expired and decommissioned domains

  • Old certificates often point to infrastructure that no longer exists

  • Setting to 90 days typically reduces noise by 20-40% while keeping relevant results

DEEP_WILDCARD_FILTER

Enables iterative wildcard detection at all subdomain levels, not just the root.

How it works:

  1. Extracts unique parent domains from resolved subdomains

  2. Generates random probe hostname for each parent (e.g., a1b2c3d4.api.example.com)

  3. If random probe resolves, parent is a wildcard

  4. Filters all subdomains under detected wildcard parents

  5. Repeats up to 5 iterations to catch nested wildcards

Why use this:

  • Enterprise targets often have deep wildcards (e.g., *.na45.salesforce.com)

  • Standard detection only checks *.example.com

  • Removes 50-80% false positives on enterprise infrastructure

  • Detected wildcards saved to subdomains/wildcards_detected.txt

EXCLUDE_SENSITIVE

Prevents scanning domains that match patterns in config/sensitive_domains.txt.

Excluded patterns include:

  • Government: *.gov, *.gob.*, *.gouv.*

  • Military: *.mil, *.defense.*

  • Educational: *.edu, *.ac.*

  • Financial: *.bank, *.banking.*

  • Critical infrastructure: *.nhs.*, *.hospital.*, *.police.*

Why use this:

  • Legal protection when scanning wildcard scopes

  • Prevents accidental contact with sensitive infrastructure

  • Patterns can be customized in config/sensitive_domains.txt

Permutation Settings

TLS Port Discovery

Web Detection Module

Host Module

Web Analysis Module

Vulnerability Module

Nuclei Configuration


Threading and Rate Limits

Thread Configuration

Rate Limits

PureDNS Limits

Adaptive Rate Limiting


Timeouts


Wordlists

Cloud Hunter Settings


DEEP Mode Settings

Behavior:

  • If subdomain count < DEEP_LIMIT, additional techniques run

  • If < DEEP_LIMIT2, even more intensive techniques run


Axiom Settings


Faraday Settings


AI Settings


Extra Features

Notification Settings

Diff/Incremental Mode

Cleanup Settings

Cache Settings

Log Rotation

Structured Logging

Asset Tracking

IPv6

Intrusive Mode


HTTP Options

Tool Flags


Color Configuration


Debug Settings


Configuration Examples

Stealth Configuration

Aggressive Configuration

Bug Bounty Configuration


Using Custom Config Files


Environment Variable Priority

Environment variables override config file settings:


Next Steps


Documentation Info Branch: dev | Version: v3.0.0+ | Last updated: February 2026 Variables documented match reconftw.cfg in the repository root.

Last updated