How ant3r0s/email-osint-tool works
Project type and purpose
• This is a Python‑based CLI (command‑line interface) OSINT tool focused on extracting and analyzing intelligence from email domains.
• Its main use cases include domain extraction, DNS resolution, WHOIS lookups, SSL certificate checks, HTTP header analysis, geolocation, CMS detection, crawling/link extraction, Google dorks, and related reconnaissance functions.
File structure
• Top level:
• osint.py – single entry‑point script housing the CLI, menu logic, and all functional routines
• requirements.txt – lists dependencies (requests, beautifulsoup4, whois, dnspython, etc.)
• README.md, LICENSE – documentation and license
• There are no separate subdirectories; instead, logical modules and functions are grouped inside osint.py.
README for additional insights
• Reveals the tool’s feature set and external integrations:
• socket.gethostbyname, dnspython for DNS
• python‑whois library for WHOIS
• requests for HTTP/SSL/header analysis
• BeautifulSoup for HTML parsing
• ipinfo.io API for geolocation
• Comments hint at using additional external services (ViewDNS, HaveIBeenPwned)
a. Main components
1. User (CLI)
2. CLI/Menu Dispatcher
3. Functional Modules
– Domain Extractor
– DNS Resolver
– WHOIS Client
– SSL/Certificate Checker
– HTTP Header Analyzer
– Link Extractor & Crawler
– Google Dork Executor
– GeoIP Lookup
– CMS Detector
– Similar‑Domain Finder
4. External Services & Libraries
– socket, dnspython, whois library
– requests (HTTP/SSL calls)
– BeautifulSoup (HTML parsing)
– ipinfo.io API
– (Optional) ViewDNS, HaveIBeenPwned, WHOIS APIs
b. Relationships and interactions
• The User invokes commands in the CLI
• The CLI/Menu Dispatcher parses input and routes to the corresponding Functional Module
• Each module may:
– Call a Python library (e.g., socket.gethostbyname, whois)
– Send HTTP requests via requests to target domains or external APIs
– Parse HTML with BeautifulSoup
– Return structured results to the CLI
• The CLI formats and prints results back to the user
c. Architectural patterns and principles
• Single‑process, modular design (all logic in one script but logically separated)
• Separation of concerns: input parsing, core OSINT functions, output formatting
• Dependency on well‑established libraries for network, parsing, and API calls
d. Key technologies and libraries
– Python 3.x
– requests, beautifulsoup4
– python‑whois, dnspython
– socket (built‑in)
– External REST APIs (ipinfo.io, optional OSINT services)
Final recommendations
• Modules with the primary library or protocol they use (e.g., “WHOIS Client (python‑whois)”).
• Keep the data flow clear: show how user input travels through the system and how responses propagate back.