michenriksen/aquatone is a Backend project on GitHub, written primarily in Go. It has 6.0k stars. A Tool for Domain Flyovers
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Aquatone is a tool for visual inspection of websites across a large amount of hosts and is convenient for quickly gaining an overview of HTTP-based attack surface.
Installation
Install Google Chrome or Chromium browser -- Note: Google Chrome is currently giving unreliable results when running in headless mode, so it is recommended to install Chromium for the best results.
Download the latest release of Aquatone for your operating system.
Uncompress the zip file and move the aquatone binary to your desired location. You probably want to move it to a location in your $PATH for easier use.
Compiling the source code
If you for some reason don't trust the pre-compiled binaries, you can also compile the code yourself. You are on your own if you want to do this. I do not support compiling problems. Good luck with it!
Usage
Command-line options:
-chrome-path string
Full path to the Chrome/Chromium executable to use. By default, aquatone will search for Chrome or Chromium
-debug
Print debugging information
-http-timeout int
Timeout in miliseconds for HTTP requests (default 3000)
-nmap
Parse input as Nmap/Masscan XML
-out string
Directory to write files to (default ".")
-ports string
Ports to scan on hosts. Supported list aliases: small, medium, large, xlarge (default "80,443,8000,8080,8443")
-proxy string
Proxy to use for HTTP requests
-resolution string
screenshot resolution (default "1440,900")
-save-body
Save response bodies to files (default true)
-scan-timeout int
Timeout in miliseconds for port scans (default 100)
-screenshot-timeout int
Timeout in miliseconds for screenshots (default 30000)
-session string
Load Aquatone session file and generate HTML report
-silent
Suppress all output except for errors
-template-path string
Path to HTML template to use for report
-threads int
Number of concurrent threads (default number of logical CPUs)
-version
Print current Aquatone version
Giving Aquatone data
Aquatone is designed to be as easy to use as possible and to integrate with your existing toolset with no or minimal glue. Aquatone is started by piping output of a command into the tool. It doesn't really care how the piped data looks as URLs, domains, and IP addresses will be extracted with regular expression pattern matching. This means that you can pretty much give it output of any tool you use for host discovery.
IPs, hostnames and domain names in the data will undergo scanning for ports that are typically used for web services and transformed to URLs with correct scheme. If the data contains URLs, they are assumed to be alive and do not undergo port scanning.
Example:
$ cat targets.txt | aquatone
Output
When Aquatone is done processing the target hosts, it has created a bunch of files and folders in the current directory:
aquatone_report.html: An HTML report to open in a browser that displays all the collected screenshots and response headers clustered by similarity.
aquatone_urls.txt: A file containing all responsive URLs. Useful for feeding into other tools.
aquatone_session.json: A file containing statistics and page data. Useful for automation.
headers/: A folder with files containing raw response headers from processed targets
html/: A folder with files containing the raw response bodies from processed targets. If you are processing a large amount of hosts, and don't need this for further analysis, you can disable this with the -save-body=false flag to save some disk space.
screenshots/: A folder with PNG screenshots of the processed targets
The output can easily be zipped up and shared with others or archived.
Changing the output destination
If you don't want Aquatone to create files in the current working directory, you can specify a different location with the -out flag:
It is also possible to set a permanent default output destination by defining an environment variable:
export AQUATONE_OUT_PATH="~/aquatone"
Specifying ports to scan
Be default, Aquatone will scan target hosts with a small list of commonly used HTTP ports: 80, 443, 8000, 8080 and 8443. You can change this to your own list of ports with the -ports flag:
Aquatone is designed to play nicely with all kinds of tools. Here's some examples:
Amass DNS enumeration
Amass is currently my preferred tool for enumerating DNS. It uses a bunch of OSINT sources as well as active brute-forcing and clever permutations to quickly identify hundreds, if not thousands, of subdomains on a domain:
There are plenty of other DNS enumeration tools out there and Aquatone should work just as well with any other tool:
Sublist3r
Subfinder
Knock
Fierce
Gobuster
Nmap or Masscan
Aquatone can make a report on hosts scanned with the Nmap or Masscan portscanner. Simply feed Aquatone the XML output and give it the -nmap flag to tell it to parse the input as Nmap/Masscan XML:
$ cat scan.xml | aquatone -nmap
Credits
Thanks to EdOverflow for the can-i-take-over-xyz project which Aquatone's domain takeover capability is based on.
Thanks to Elbert Alias for the Wappalyzer project's technology fingerprints which Aquatone's technology fingerprinting capability is based on.
How active is development on michenriksen/aquatone?
The most recent commit recorded on michenriksen/aquatone was 4.5 years ago, based on the GitHub push timestamp. The repository has 904 forks — one of the better signals of community interest.
How many stars does michenriksen/aquatone have?
michenriksen/aquatone has 6.0k GitHub stars — refresh the page for the live number, or check github.com/michenriksen/aquatone. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What else is in the Backend space?
michenriksen/aquatone is tracked by TopGit under the Backend category, alongside 6 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What language is michenriksen/aquatone written in?
michenriksen/aquatone is written primarily in Go. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is michenriksen/aquatone associated with?
GitHub's repository topics for michenriksen/aquatone: "chrome-headless", "chromium", "golang", "osint", "reconnaissance", "security". TopGit's editorial category is Backend.
Where do I read more about michenriksen/aquatone?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/michenriksen/aquatone is the definitive source.
Why is michenriksen/aquatone categorized under Backend?
TopGit places michenriksen/aquatone in the Backend category based on its GitHub topics and description (tagged: "chrome-headless", "chromium", "golang"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Want a second opinion on aquatone?
Ask an AI that can read this page — one click and you get its take on aquatone.