Cannot use Internet while launching an amass command

[ludovicroland]

Hello,

I would like to try the amass tool in order to find subdomains.

Using the documentation, the basic command should be something like: amass enum -d example.com

On my case, I am not sure that the command works correctly. In fact:

1. nothing is prompted on the terminal after validating the command
2. my computer seems to "lost" its internet connection --> I am still connected on the Wifi but Internet is very slow ans it's nearly impossible to display an website on Chrome.

For the first point, I tried to use the -v option in order to activate a "verbose" mode. With no success, nothing is displayed in the terminal.

For the internet issue, I tried to use some options in order to reduce the number of requests per seconds like:

• -dns-qps 10
• -trqps 10
• -rqps 10

So I have something like that: amass enum -rqps 10 -trqps 10 -dns-qps 10 -v -d example.com but I still have both issues.

I have installed the tool using brew on a MAC. The command is the first command I launch directly after the installation of the tool. I do not try to configure something before the use of the tool.

I am using the version 4.2.0

Any help is welcomed in order to make the tool working correctly on my machine.

[pdelteil]

Hello,

Some documentation is outdated. Now you need to use https://github.com/owasp-amass/oam-tools to get the subdomains. Amass enum only populates 'the graph'.

New version is very confusing for me.

[babbangida]

Hi have you tried these step this will take you through different steps to help you maybe locate where the issue is let me know if it helps Ensure that you’re using the correct syntax for verbose mode. The -v flag should be placed after the enum subcommand:
amass enum -v -d example.com

If you still don’t see any output, try redirecting the output to a file for further analysis:
amass enum -v -d example.com > amass_output.txt

Check the contents of amass_output.txt to see if any subdomains were discovered.

Internet Connection
Verify that your internet connection is stable.
If you’re using a VPN, try disabling it temporarily.
Test other internet-dependent applications to ensure they’re working correctly.
Amass Configuration:
Amass doesn’t usually require additional configuration after installation.
However, ensure that you have the necessary permissions to run the tool.
Confirm that Amass is correctly installed by running:
amass -version

If you’re using a specific version (e.g., 4.2.0), make sure it’s compatible with your system.

Update Amass
Check if there’s a newer version of Amass available.
Update it using:
brew update
brew upgrade amass

Check Dependencies
Amass relies on external services (e.g., DNS servers, APIs) for subdomain discovery.
Ensure that your system can access these services without any restrictions.
Firewall or Security Software:
Check if any firewall or security software is blocking Amass from making requests.
Temporarily disable such software and try running Amass again 🙂