amass
amass copied to clipboard
In-depth attack surface mapping and asset discovery
@superuser5 wrote: Would be awesome to be able to put constraints on searches to the known values (IP ranges / cert info / string in whois record ) and with...
In the config.ini file, it's possible to set up a path like `output_directory =$HOME/amass` and the environment variable `$HOME` will be automatically expanded as `/home/johndoe`. But if you put something...
It is not technically POSIX compliant or common to use single-dash short options (ex: `-o`) for multi-character option flags (ex: `-foo`). Please use long options for multi-character option flags (ex:...
Tested carefully :heavy_check_mark:
Reference: https://networksdb.io/api/docs The current does not work at all, due to some changes of API response by NetworksDB (the old API endpoints are still being kept, but may be removed...
I am getting the error when using `amass track -d example.com` System: `Ubuntu 20.04.2 LTS` Go version: `1.16.3 linux/amd64` Amass version: `v3.12.2` ``` panic: interface conversion: interface {} is string,...
New data source: [DomainTools](https://www.domaintools.com/)
Added `-nocerts` and `-noaxfr` flags to the `enum` subcommand to disable certification name grabbing and zone transfers when active mode is enabled.
Hello, I get the following error messages in the amass.log file when using amass with cloudflare API : Cloudflare: HTTP status 400: Invalid request headers (6003)
It would be helpful to add an option to enumerate potential top level domains. Compare the description of the following [project (tld-scan)](https://github.com/Ethermat/tld-scan): _The core idea is to perform a TCP...