A Golang command-line utility that uses Chrome Headless to capture website screenshots and gather web data.
Gowitness is a command-line website screenshot and reconnaissance tool written in Go that uses Chrome Headless to capture accurate, high-quality screenshots of web interfaces. It is designed to efficiently document web targets visually and collect associated data like HTTP headers, console logs, and cookies. The tool supports scanning from various inputs like URLs, CIDRs, and Nmap results, and outputs to structured formats like SQLite, JSONLines, and CSV, with a web-based viewer for analysis.
Security professionals and penetration testers who need to perform web reconnaissance, visually document targets, and analyze changes at scale. Developers or administrators monitoring web interfaces for security assessments or workflow automation may also use it.
Developers choose Gowitness for its fast, accurate screenshot capture using Chrome Headless, combined with flexible data collection and multiple output formats. Its unique selling point is the integration of a web-based viewer with a full API for reviewing captured data, making it efficient for security assessments and web monitoring workflows.
🔍 gowitness - a golang, web screenshot utility using Chrome Headless
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses Chrome Headless for accurate, high-quality captures, as emphasized in the README for doing one thing well—taking screenshots quickly and accurately.
Accepts various inputs like URLs, CIDRs, Nmap, and Nessus results, enabling scanning from multiple sources for reconnaissance workflows.
Captures and saves request logs, console logs, HTTP headers, and cookies, extending utility beyond screenshots for security assessments.
Supports outputs to SQLite, JSONLines, CSV, and includes a web-based viewer with API, as highlighted in the features for structured analysis.
Windows support is described as 'mostly working' in the README, indicating potential instability or incomplete functionality on some systems.
Relies on Chrome Headless, which can be resource-intensive and may not be suitable for environments without Chrome or with limited resources.
The README mentions 'many, many flags' and directs to a wiki for advanced documentation, suggesting complexity in mastering all features and commands.