shuffleDNS is a wrapper around massdns written in go that allows you to enumerate valid subdomains using active bruteforce as well as resolve subdomains with wildcard handling and easy input-output support.
Based on the work on
massdnsproject by @blechschmidt.
- Simple and modular code base making it easy to contribute.
- Fast And Simple active subdomain scanning.
- Handles wildcard subdomains in a smart manner.
- Optimized for ease of use
- Stdin and stdout support for integrating in workflows
|-d||Domain to find or resolve subdomains for||shuffledns -d hackerone.com|
|-directory||Temporary directory for enumeration||shuffledns -directory /hdd|
|-r||File containing resolvers for enumeration||shuffledns -r resolvers.txt|
|-nC||Don't Use colors in output||shuffledns -nC|
|-o||File to save output result (optional)||shuffledns -o hackerone.txt|
|-list||List of subdomains to process for||shuffledns -list bugcrowd.txt|
|-massdns||Massdns binary path||shuffledns -massdns /usr/bin/massdns|
|-retries||Number of retries for dns enumeration (default 5)||shuffledns -retries 1|
|-silent||Show only subdomains in output||shuffledns -silent|
|-t||Number of concurrent massdns resolves (default 10000)||shuffledns -t 100|
|-v||Show Verbose output||shuffledns -v|
|-version||Show version of shuffledns||shuffledns -version|
|-w||File containing words to bruteforce for domain||shuffledns -w words.txt|
shuffledns requires massdns to be installed in order to perform its operations. You can see the install instructions at https://github.com/blechschmidt/massdns#compilation.
If you place the binary in
/usr/local/bin/massdns, the tool will auto-detect the presence of the binary and use it. On windows, you need to supply the path to the binary for the tool to work.
The tool also needs a list of valid resolvers. The dnsvalidator project can be used to generate these lists. Either you can use a custom wordlist or use the commonspeak2 wordlists at commonspeak2-wordlist.
The installation is easy. You can download the pre-built binaries for your platform from the Releases page. Extract them using tar, move it to your $PATH and you're ready to go.
> tar -xzvf shuffledns-linux-amd64.tar
> mv shuffledns-linux-amd64 /usr/bin/shuffledns
> shuffledns -h
shuffledns requires go1.13+ to install successfully. Run the following command to get the repo -
> GO111MODULE=on go get -u -v github.com/projectdiscovery/shuffledns/cmd/shuffledns
shuffledns supports two types of operations.
1. Resolving Subdomains
To resolve a list of subdomains, you can pass the list of subdomains via the
> shuffledns -d example.com -list example.com-subdomains.txt -r resolvers.txt
example.com-subdomains.txtand returns the results. The tool uses the resolvers specified with -r option to do the resolving.
You can also pass the list of subdomains at standard input (STDIN). This allows for easy integration in automation pipelines.
> subfinder -d example.com | shuffledns -d example.com -r resolvers.txt
subfinderand resolves them with shuffledns returning only the unique and valid subdomains.
2. Bruteforcing Subdomains
shuffledns also supports bruteforce of a target with a given wordlist. You can use the
wflag to pass a wordlist which will be used to generate permutations that will be resolved using massdns.
> shuffledns -d hackerone.com -w wordlist.txt -r resolvers.txt
hackerone.comwith the wordlist
wordlist.txt. The domain bruteforce can also be done with standard input as in previous example for resolving the subdomains.
> echo hackerone.com | shuffledns -w wordlist.txt -r resolvers.txt
The -o command can be used to specify an output file.
> shuffledns -d hackerone.com -w wordlist.txt -o output.txt
> echo hackerone.com | shuffledns -w wordlist.txt -r resolvers.txt -silent | httprobe
> echo hackerone.com | subfinder | shuffledns -d hackerone.com -r resolvers.txt -silent | httprobe
A note on wildcards
A special feature of shuffleDNS is its ability to handle multi-level DNS based wildcards and do it so with very less number of DNS requests. Sometimes all the subdomains will resolve which will lead to lots of garbage in the results. The way shuffleDNS handles this is it will keep track of how many subdomains point to an IP and if the count of the Subdomains increase beyond a certain small threshold, it will check for wildcard on all the levels of the hosts for that IP iteratively.