IVRE (Instrument de veille sur les réseaux extérieurs) or DRUNK (Dynamic Recon of UNKnown networks) vs Recog: Side-by-Side Comparison (2026)

IVRE (Instrument de veille sur les réseaux extérieurs) or DRUNK (Dynamic Recon of UNKnown networks)

Threat hunters and red teamers with in-house infrastructure will extract real value from IVRE because it bundles passive DNS, active scanning, and data aggregation into a single framework you control entirely, eliminating vendor lock-in on recon workflows. The 3,964 GitHub stars reflect active use in offensive security circles, and the free pricing means you pay only for the infrastructure you run it on. This is not for teams expecting a managed SaaS experience or those who need hunting automation built in; IVRE requires familiarity with command-line tools and willingness to integrate data sources yourself.

Recog

Security teams running manual threat hunts or building custom detection workflows will extract the most from Recog because its fingerprinting approach identifies obscured services and hardware that signature-based tools consistently miss. The 742 GitHub stars and active community fork activity signal real adoption in IR and red team environments, not just a proof-of-concept framework. Skip this if you need automated scanning at scale or point-and-click ease; Recog demands operational knowledge to tune probes and interpret results, which is exactly why experienced hunters prefer it.