search

owasp-amass / amass

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

output of enum -d is diffrent #963

Open ReekElderblood opened 11 months ago

ReekElderblood commented 11 months ago 
└─# amass --version
v4.1.0

┌──(root㉿kali)-[~/]
└─# amass enum -d att.com  
att.com (FQDN) --> mx_record --> mx0b-00191d01.pphosted.com (FQDN)
att.com (FQDN) --> mx_record --> mx0a-00191d01.pphosted.com (FQDN)
att.com (FQDN) --> ns_record --> a2-64.akam.net (FQDN)
att.com (FQDN) --> ns_record --> a4-64.akam.net (FQDN)
att.com (FQDN) --> ns_record --> a5-66.akam.net (FQDN)
att.com (FQDN) --> ns_record --> a1-187.akam.net (FQDN)
att.com (FQDN) --> ns_record --> a11-65.akam.net (FQDN)
att.com (FQDN) --> ns_record --> a22-67.akam.net (FQDN)

it is print this all but i only want to print domain nothing more or do i have to fitler it myslef

NotoriousRebel commented 10 months ago

Yeah they seemed to remove the -json flag as well for unknown reasons :/

ReekElderblood commented 10 months ago

what should I do if I want to have only a domain in my output?

NotoriousRebel commented 10 months ago

Just parse it yourself? Use the -oA flag to at least get output in text file format: amass enum -d att.com -oA att_results Can then just do cat att_results.txt | cut -d " " -f 1 | grep -i "att.com" | sort -u

guillaume-d commented 10 months ago

The same rationale and SQLite-based workaround as in https://github.com/owasp-amass/amass/issues/941#issuecomment-1653979385 seems to apply.