Hi HN, I’m the creator of TypoGuard. I built this specialized engine to help protect brands against typosquatting and phishing domains before they are used in

Hi HN, I’m the creator of TypoGuard. I built this specialized engine to help protect brands against typosquatting and phishing domains before they are used in active attacks. The Core Logic: Unlike basic permutation tools, TypoGuard uses a multi-factor risk scoring system (High Risk >= 8 points). The scoring is based on: Domain Metadata: Real-time WHOIS age (domains ≤ 30 days are flagged), MX record presence, and SSL status. Advanced Permutations: Beyond character swaps, the engine handles Phonetic & Vowel swaps, Dictionary Affixing, and TLD variants. Homoglyph Detection: Identifying Unicode lookalikes (IDN). Wildcard DNS Shield: To avoid noise, I implemented logic to detect and filter out parking pages that resolve every random subdomain. Infrastructure & Automation: The system is designed for passive monitoring rather than just manual lookups: Backend: Built with FastAPI and PostgreSQL. Asynchronous Processing: I use Celery with Redis to handle the heavy lifting of scanning thousands of domain permutations. Automated Reporting: A Celery Beat scheduler manages periodic scans and generates automated email reports. You don't need to manually check the dashboard; the system alerts you only when a high-risk threat is detected. Deployment: The entire stack is containerized with Docker Compose, running behind an Nginx reverse proxy. Why not open-source? The project is currently a closed SaaS as I’m focusing on the Phase 3 roadmap, which includes a Public REST API and enterprise SIEM integrations (Splunk/Sentinel). However, I’m very open to discussing the underlying algorithms, the risk scoring weights, or the infrastructure challenges. I'd love to get your feedback on the scanning logic or the reporting workflow! Thanks!