How jabinjawad/knalyzer works
Main Components
• User Interface (Interactive Console): This is where users interact with the tool. The CLI is responsible for accepting user input (e.g., domain or IP addresses, menu selections) and displaying analysis results.
• Core Analysis Engine: This central component handles the workflow, parses user commands, and coordinates between the specialized analysis modules.
• Module Subsystems:
• WHOIS Module: Fetches registration data from WHOIS servers.
• DNS Module: Retrieves records such as A, CNAME, NS, TXT, MX, and DMARC.
• SSL Inspection Module: Analyzes SSL certificate validity and details.
• IP Geolocation and Provider Module: Collects geolocation and network information (IP info, hosting provider, Cloudflare or CDN details).
• Subdomain Discovery Module: Detects and lists subdomains associated with a domain.
• Technology Detection Module: Examines underlying technologies (e.g., web servers, hosting stacks, CDN information).
• PDF Report Generator: Compiles and formats the analysis results into a downloadable PDF report.
• Recommendation Engine: Provides suggestions for improving security and performance based on the analysis.
• External Service Integrations: These represent the external APIs or services that provide the raw data (e.g., DNS lookup services, whois servers).
Relationships and Data Flow
• The user interacts with the CLI, which sends commands to the Core Analysis Engine.
• The Core Engine acts as an orchestrator by invoking the independent modules based on the user’s choice. Each module is responsible for specific data collection and processing tasks.
• After modules complete their tasks, the Core Analysis Engine aggregates and formats the data.
• The PDF Report Generator module is then optionally invoked to create a report.
• External service integrations (such as whois servers, DNS providers, and IP information services) are depicted as external systems that the individual modules communicate with.
Architectural Patterns and Design Principles
• Modular / Layered Architecture: Each core functionality (WHOIS, DNS, SSL, etc.) is separated, which makes it easier to extend or modify components independently.
• Command Processing Pattern: The CLI passes commands to the Core Analysis Engine, which acts as a controller managing the flow.
• External API / Service Integration: Modules are designed to interface with various external data sources.
• Maintainability and Extensibility: The structure shows clear boundaries between modules, making it straightforward to add new analysis capabilities or update existing ones.
Relevant Technologies & Frameworks
• Although the file tree doesn’t reveal language-specific frameworks, the README implies this is a compiled executable (an .exe). The underlying implementation may use any programming language capable of network requests and PDF generation.
• The external integrations likely utilize standard network libraries for HTTP requests (and perhaps a DNS resolution library).