Findomain v0.9.3 - The Fastest And Cross-Platform Subdomain Enumerator

Host: KVM/QEMU (Standard PC (i440FX + PIIX, 1996) pc-i440fx-3.1)
Kernel: 5.2.6-arch1-1-ARCH
CPU: Intel (Skylake, IBRS) (4) @ 2.904GHz
Memory: 139MiB / 3943MiB

• Subdomains monitoring: put data to Discord, Slack or Telegram webhooks. See Subdomains Monitoring for more information.
• Multi-thread support for API querying, it makes that the maximun time that Findomain will take to search subdomains for any target is 20 seconds.
• Parallel support for subdomains resolution, in good network conditions can resolv about 2000 subdomains per minute.
• DNS over TLS support.
• Specific IPv4 or IPv6 query support.
• Discover subdomains without brute-force, it tool uses Certificate Transparency Logs and APIs.
• Discover only resolved subdomains.
• Discover subdomains IP for data analisis.
• Read target from user argument (-t) or file (-f).
• Write to one unique output file specified by the user all or only resolved subdomains.
• Write results to automatically named TXT output file(s).
• Hability to query directly the Findomain database created with Subdomains Monitoring for previous discovered subdomains.
• Hability to import and work data discovered by other tools.
• Quiet mode to run it silently.
• Cross platform support: Any platform, it's written in Rust and Rust is multiplatform. See the documentation for instructions.
• Multiple API support.

• Certspotter
• Crt.sh
• Virustotal
• Sublist3r
• Facebook**
• Spyse (CertDB)*
• Bufferover
• Threadcrow
• Virustotal with apikey**

$ git clone https://github.com/Edu4rdSHL/findomain.git -b develop # Only the develop branch is needed
$ cd findomain
$ cargo build --release
$ ./target/release/findomain

$ git pull
$ cargo build --release
$ ./target/release/findomain

• Linux
• Windows
• MacOS
• Aarch64 (Raspberry Pi)

1. cargo install findomain
2. Execute the tool from $HOME/.cargo/bin. See the cargo-install documentation.

1. Clone the repository or download the release source code.
2. Extract the release source code (only needed if you downloaded the compressed file).
3. Go to the folder where the source code is.
4. Execute cargo build --release
5. Now your binary is in target/release/findomain and you can use it.

$ pkg install rust make perl
$ cargo install findomain
$ cd $HOME/.cargo/bin
$ ./findomain

$ git clone https://github.com/Edu4rdSHL/findomain.git
$ cd findomain
$ cargo build --release
$ sudo cp target/release/findomain /usr/bin/
$ findomain

$ wget https://github.com/Edu4rdSHL/findomain/releases/latest/download/findomain-linux
$ chmod +x findomain-linux
$ ./findomain-linux

$ sudo pacman -S findomain

$ wget https://github.com/Edu4rdSHL/findomain/releases/latest/download/findomain-aarch64
$ chmod +x findomain-aarch64
$ ./findomain-aarch64

$ wget https://github.com/Edu4rdSHL/findomain/releases/latest/download/findomain-osx
$ chmod +x findomain-osx.dms
$ ./findomain-osx.dms

1. You downloaded a precompiled binary: If you are using a precompiled binary, then you need to download the new binary.
2. You are using it from BlackArch Linux: Just run pacman -Syu
3. You have cloned the repo and compiled it from source: You just need to go to the folder where the repo is cloned and run: git pull && cargo build --release, when finish, you have your executable in target/release/findomain.
4. You downloaded a source code release and compiled it: You need to download the new source code release and compile it again.
5. I used cargo install findomain: then just run cargo install --force findomain.

1. Open https://developers.facebook.com/apps/
2. Clic in "Create App", put the name that you want and send the information.
3. In the next screen, select "Configure" in the Webhooks option.
4. Go to "Configuration" -> "Basic" and clic on "Show" in the "App secret key" option.
5. Now open in your browser the following URL: https://graph.facebook.com/oauth/access_token?client_id=your-app-id&client_secret=your-secret-key&grant_type=client_credentials

6. You should have a JSON like:

{
  "access_token": "xxxxxxxxxx|yyyyyyyyyyyyyyyyyyyyyyy",
  "token_type": "bearer"
}

7. Save the access_token value.

$ findomain_fb_token="YourAccessToken" findomain -(options)

> set findomain_fb_token=YourAccessToken && findomain -(options)

1. Open https://account.spyse.com/register and make the registration process (include email verification).
2. Log in into your spyse account and go to https://account.spyse.com/user
3. Search for the "API token" section and clic in "Show".
4. Save that access token.

$ findomain_spyse_token="YourAccessToken" findomain -(options)

> set findomain_spyse_token=YourAccessToken && findomain -(options)

1. Open https://www.virustotal.com/gui/join-us and make the registration process (include email verification).
2. Log in into your spyse account and go to https://www.virustotal.com/gui/user/YourUsername/apikey
3. Search for the "API key" section.
4. Save that API key.

$ findomain_virustotal_token="YourAccessToken" findomain -(options)

> set findomain_virustotal_token=YourAccessToken && findomain -(options)

        --postgres-database <postgres-database>    Postgresql database.
        --postgres-host <postgres-host>            Postgresql host.
        --postgres-password <postgres-password>    Postgresql password.
        --postgres-port <postgres-port>            Postgresql port.
        --postgres-user <postgres-user>            Postgresql username.

• Discord.
• Slack.
• Telegram.

findomain_discord_webhook: Discord webhook URL.
findomain_slack_webhook: Slack webhook URL.
findomain_telegrambot_token: Telegram bot autentication token.
findomain_telegrambot_chat_id: Unique identifier for the target chat or username of the target channel.

1. If you only specify the -m flag without more arguments or don't specify one of the options Findomain sets:

• Database host: localhost
• Database username: postgres
• Database password: postgres
• Database port: 5432
• Database: Default PostgreSQL database cluster

1. Connect to local computer and local PostgreSQL server with specific username, password and database and push the data to both Discord and Slack webhooks

$ findomain_discord_webhook='https://discordapp.com/api/webhooks/XXXXXXXXXXXXXXX' findomain_slack_webhook='https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX' findomain -m -t example.com --postgres-database findomain --postgres-user findomain --postgres-host localhost --postgres-port 5432

2. Connect to remote computer/server and remote PostgreSQL server with specific username, password and database and push the data to both Discord and Slack webhooks

$ findomain_discord_webhook='https://discordapp.com/api/webhooks/XXXXXXXXXXXXXXX' findomain_slack_webhook='https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX' findomain -m -t example.com --postgres-user postgres --postgres-password psql  --postgres-host 192.168.122.130 --postgres-port 5432

3. Connect to remote computer/server and remote PostgreSQL server with specific username, password and database and push the data to Telegram webhook

$ findomain_telegrambot_token="Your_Bot_Token_Here" findomain_telegrambot_chat_id="Your_Chat_ID_Here" findomain -m -t example.com --postgres-user postgres --postgres-password psql  --postgres-host 192.168.122.130 --postgres-port 5432

4. Connect to local computer using the default values

$ findomain_discord_webhook='https://discordapp.com/api/webhooks/XXXXXXXXXXXXXXX' findomain_slack_webhook='https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX' findomain -m -t example.com

1. Make a simple search of subdomains and print the info in the screen:

2. Make a search of subdomains and print the info in the screen:

3. Make a search of subdomains and export the data to a output file (the output file name in it case is example.com.txt):

4. Make a search of subdomains and export the data to a custom output file name:

5. Make a search of only resolvable subdomains:

6. Make a search of only resolvable subdomains, exporting the data to a custom output file.

7. Search subdomains from a list of domains passed using a file (you need to put a domain in every line into the file):

8. Search subdomains from a list of domains passed using a file (you need to put a domain in every line into the file) and save all the resolved domains into a custom file name:

9. Query the Findomain database created with Subdomains Monitoring.

10. Query the Findomain database created with Subdomains Monitoring and save results to a custom filename.

11. Import subdomains from several files and work with they in the Subdomains Monitoring process: