The complete solution for domain recognition. Supports screenshotting, port scanning, importing data from other tools, subdomain monitoring, and more. Be alerted on your findings through services such as Discord, Slack, and Telegram. Multiple API Keys for sources and much more.

The following table demonstrates features that are available in the premium version (but not the free version) of Findomain. It aims to gives you an idea of why you should use Findomain and what it can do for you. The domain used for the test was aol.com. The details of the BlackArch virtual machine used in the test are outlined below:

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 was Linux's time command.

Summary: 84110 subdomains in 5.5 seconds.

• 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 15 seconds (in case of API's timeout).
• Parallel support for subdomains resolution, in good network conditions can resolv about 3.5k of 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 analysis.
• 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.
• Possibility to use as subdomain resolver.
• Subdomain wildcard detection for accurate results.
• Support for subdomain discover using bruteforce method.
• Support for configuration file in TOML, JSON, HJSON, INI or YAML format.
• Custom DNS IP addresses for fast subdomains resolving (more than 60 per second by default, adjustable using the --threads option.

See Subdomains Enumeration: what is, how to do it, monitoring automation using webhooks and centralizing your findings for a detailed guide, including real-world examples, of how to get the most out of the tool.

Findomain uses Certificate Transparency logs and well-tested APIs to find subdomains. This method makes the tool much faster and more reliable than alternatives. If you want to know more about Certificate Transparency logs, read https://www.certificate-transparency.org/

Findomain makes use of multiple publicly-available APIs to perform the search. The following is a list of APIs that we are using at the moment:

• Certspotter
• Crt.sh Database (favorite) or Crt.sh HTTP API
• Virustotal
• Sublist3r
• Facebook **
• Bufferover
• Threatcrowd
• Virustotal with apikey **
• AnubisDB
• Urlscan.io
• SecurityTrails **
• Threatminer
• C99 **
• CTSearch

Notes

APIs marked with **, require an access token to work. Search in the Findomain documentation for help on 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 API. Search in the Findomain documentation for help on how to configure and use it.

More APIs?

If you know other APIs that should be added, comment here.

We offer ready-to-use binaries for the following platforms (64-bit only):

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

If you need to run Findomain on another platform, continue reading the documentation.

If you have a problem or a feature request, open an issue.

This project exists thanks to all the people who contribute. See the contributors list.