Locked Findomain v0.9.3

[dEEpEst]

What Findomain can do?

It table gives you a idea why you should use findomain and what it can do for you. The domain used for the test was aol.com in the following BlackArch virtual machine:

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

The tool used to calculate the time, is the time command in Linux.

Enumeration Tool	Search Time	Total Subdomains Found	CPU Usage	RAM Usage
Findomain	real 0m5.515s	84110	Very Low	Very Low

Summary: 84110 subdomains in 5.5 seconds.

Features

• 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.

How it works?

It tool doesn't use the common methods for sub(domains) discover, the tool uses Certificate Transparency logs and specific well tested APIs to find subdomains. It method make it tool the most faster and reliable. The tool make use of multiple public available APIs to perform the search. 

APIs that we are using at the moment:

• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
   **
• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
   *
• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
• This is the hidden content, please

  • Sign In
  • or
  • Sign Up
   **

Notes

APIs marked with **, require an access token to work. Search in the Findomain documentation how to configure and use it.

APIs marked with * can optionally be used with an access token, create one if you start experiencing problems with that APIs. Search in the Findomain documentation how to configure and use it.

Download: 

This is the hidden content, please

• Sign In
• or
• Sign Up