search

owasp-amass / amass

In-depth attack surface mapping and asset discovery
https://owasp.org/www-project-amass/
Other
11.51k stars 1.84k forks source link

Rescan all previously searched -d specified domains when enum #1001

Open Nzoth9 opened 6 months ago

Nzoth9 commented 6 months ago

I noticed something strange while testing to adapt to the latest version of amass.

amass enum -d google.com -config $AMASS_CONFIG

and enter the new domain again, it will search for the Google domain.

amass enum -d new-domain.com -config $AMASS_CONFIG

aspmx2.naver.com (FQDN) --> a_record --> 125.209.209.251 (IPAddress)
documents.google.com (FQDN) --> cname_record --> writely.l.google.com (FQDN)
rate-limited-proxy-108-177-71-0.google.com (FQDN) --> a_record --> 108.177.71.0 (IPAddress)
notifications.google.com (FQDN) --> cname_record --> plus.l.google.com (FQDN)
shopping.google.com (FQDN) --> a_record --> 173.194.222.92 (IPAddress)
shopping.google.com (FQDN) --> aaaa_record --> 2404:6800:4008:c13::5c (IPAddress)
enterprise.google.com (FQDN) --> cname_record --> www3.l.google.com (FQDN)
fonts.google.com (FQDN) --> a_record --> 142.251.223.78 (IPAddress)
fonts.google.com (FQDN) --> aaaa_record --> 2404:6800:400a:80e::200e (IPAddress)
aspmx1.naver.com (FQDN) --> a_record --> 125.209.209.251 (IPAddress)
dai.google.com (FQDN) --> cname_record --> www3.l.google.com (FQDN)
fitbit.google.com (FQDN) --> aaaa_record --> 2607:f8b0:4006:81f::200e (IPAddress)
fitbit.google.com (FQDN) --> a_record --> 142.250.199.46 (IPAddress)
local.google.com (FQDN) --> cname_record --> maps.l.google.com (FQDN)
images.google.com (FQDN) --> cname_record --> images.l.google.com (FQDN)

What's going on? If I modify the domain option in config.ini and remove the -d option, the result is the same. I'm seriously concerned that I'm doing something wrong or that this update is weird.