Amass recently released version 5. I strongly encourage to use that instead
Amass version 5 is a major refactoring and code cleanup of the amass sources. I saw they also finally realized and fixed some issues in the process as well. I strongly encourage using that unless you REALLY need some features provided by Subscout. I don't plan on really working on this anymore as the old Amass codebase (which this is based on) is an absolutely horrible mess. Should I one day grow dissatisfied with Amass ever again, maybe I'll revive this (and likely re-fork amass in its current version)
Subscout is a fork of OWASP Amass primarily focussed on flexible, performant active subdomain enumeration
Mostly out of frustration. Unfortunately, the Amass maintainers seem less and less invested in the project. Long-standing performance- and stability-issues remain unaddressed and many merge requests to fix bugs or improve funtionality don't even have any comment by the maintainer despite being open for years.
Version 3.21.2
- It doesn't crash on marshalling output like Amass sometimes does (race condition which remains unaddressed in Amass)
- It supports enumeration over Tor
- It is possible to set trusted resolvers in the config file
- Queries per second per resolver are configurable (Amass hardcodes these at 25 queries per second per resolver)
- SRV records are not queried by default as they may drastically increase the enumeration runtime for some scopes while most often not yielding any extra results
You're better off using Amass instead. No work has been done on everything but subdomain enumeration whatsoever
Clone this repository and run go build ./cmd/subscout
See the User's Guide for additional information.