If you don't want to deal with servers and complex configurations when performing recon but would like more features in an integrated solution, Findomain offers a subdomains monitoring service that provides directory fuzzing, port scanning, vulnerability discovery, and more. Monitor your target domains with several popular tools (including OWASP Amass, Sublist3r, Assetfinder and Subfinder) and receive alerts through Discord, Slack, Telegram, Email, or Push Notifications (Android/iOS/Smart Watch/Desktop) when new subdomains are found. The only thing you need to do is configure a file with your email address, webhooks, or Telegram information, and include your domains in another file. You will then have a fully-automated subdomain monitoring service that will keep you up to date with any new subdomains discovered, along with Host IPs, HTTP status, website screenshots, Open Ports, CNAME records, and more. User data is securely stored in a relational database -- you can request a dump of your data at any time. When you finish your payment, you will receive an email with the server credentials and documentation regarding configuration and other details. Note: Our private version is superior to the public version. By purchasing our private version, you keep this project alive and allow us to continue improving it. 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: The tool used to calculate the time was Linux's Summary: 84110 subdomains in 5.5 seconds. 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: Notes APIs marked with APIs marked with 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): 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.
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
time command.Enumeration Tool Search Time Total Subdomains Found CPU Usage RAM Usage Findomain real 0m5.515s 84110 Very Low Very Low --threads option.**********, require an access token to work. Search in the Findomain documentation for help on how to configure and use it.* 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.