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 massdns project by @blechschmidt.

• Resources
• Features
• Usage
• Installation Instructions
  • Prerequisite
  • Direct Installation
    • From Binary
    • From Source
• Running shuffledns
  • 1. Resolving Subdomains
  • 2. Bruteforcing Subdomains
  • A note on wildcards
• License

• 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

shuffledns -h

This will display help for the tool. Here are all the switches it supports.

shuffledns requires massdns to be installed in order to perform its operations. You can see the install instructions at massdns project.

If you place the binary in /usr/bin/massdns or /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.

You also need to provide wordlist, 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

In order to update the tool, you can use -u flag with go get command.

shuffledns supports two types of operations.

To resolve a list of subdomains, you can pass the list of subdomains via the list option.

> shuffledns -d example.com -list example.com-subdomains.txt -r resolvers.txt

This will run the tool against subdomains in example.com-subdomains.txt and 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

This uses the subdomains found passively by subfinder and resolves them with shuffledns returning only the unique and valid subdomains.

shuffledns also supports bruteforce of a target with a given wordlist. You can use the w flag 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

This will run the tool against hackerone.com with 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

The subdomains discovered can be piped to other tools too. For example, you can pipe the host discovered by shuffledns to the httprobe tool by @tomnomnom which will then find running http servers on the host.

> echo hackerone.com | shuffledns -w wordlist.txt -r resolvers.txt -silent | httprobe

http://docs.hackerone.com
http://www.hackerone.com
http://info.hackerone.com

or

> echo hackerone.com | subfinder | shuffledns -d hackerone.com -r resolvers.txt -silent | httprobe

http://docs.hackerone.com
http://www.hackerone.com
http://info.hackerone.com

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.

shuffleDNS is made with 🖤 by the projectdiscovery team. Community contributions have made the project what it is. See the Thanks.md file for more details.