How arhmfaculty/emailpicker--email-recon-tool works
Project type and purpose
• EmailPicker is a standalone, command-line Python tool for OSINT email reconnaissance.
• Its purpose is to harvest e-mail addresses from search engines and certificate transparency logs, optionally using proxies and multithreading to scale.
File structure
• The project consists of two files at the root:
• EmailPicker.py (the entire application)
• README.md (documentation)
• No separate “frontend” or “backend” folders: all logic lives in EmailPicker.py.
• Configuration and dependency management happen in-code (via argparse and requests), no external config files.
README for additional insights
• The tool:
• Queries Google, Bing, DuckDuckGo, LinkedIn, crt.sh
• Optionally rotates through a proxy list
• Runs fetch-and-parse steps in parallel threads
• Applies regex filtering to each page’s HTML
• Writes results to stdout or a file
• No persistent database; output is a simple text file.
Diagramming the architecture
a. Main components to represent:
• User / CLI – origin of commands
• Arg Parser – processes flags (-d, -t, -p, -o)
• Recon Controller – orchestrator that kicks off the workflow
• Thread Manager – spawns/coordinates worker threads
• Proxy Manager (optional) – fetches & rotates HTTP proxies
• Fetcher Module – issues HTTP requests to external services
• External Services – Google, Bing, DuckDuckGo, LinkedIn, crt.sh
• HTML Parser & Email Extractor – regex-based email filtering
• Output Writer – writes to console or file
b. Relationships and interactions:
• User → CLI → Arg Parser → Recon Controller
• Recon Controller → Thread Manager
• Thread Manager → Worker Threads (each thread uses Proxy Manager → Fetcher → Parser → Output Writer)
• Fetcher → External Services (outbound HTTP calls)
• Parser → filtered email list → back to Recon Controller → Output Writer
c. Architectural patterns/design principles:
• Pipeline/Producer-Consumer: threads fetch pages and produce email results into a shared collector.
• Modular layering: separation between input (CLI), orchestration, network I/O (Fetcher + Proxy Manager), parsing, and output.
• Optional component injection: proxy support is toggled via a flag.
d. Key technologies & libraries:
• Python 3.x runtime
• argparse (CLI parsing)
• requests (HTTP/HTTPS calls)
• threading (concurrency)
• re (regex email extraction)