We mostly use amass enum and forget the rest.
But did you know you can do something more?
Did you know that you can track scan requests?
Read more 👇
#bugbountytip #bugbounty #amass #recon #infosec #cybersecurity
But did you know you can do something more?
Did you know that you can track scan requests?
Read more 👇
#bugbountytip #bugbounty #amass #recon #infosec #cybersecurity
Where do the scans you normally do on amass get stored?
Well, every single scan you do with amass get's stored in the computer you run the scan on.
Therefore, if you run the same scan again it's possible for amass to keep track of the changes that's occurred.
Well, every single scan you do with amass get's stored in the computer you run the scan on.
Therefore, if you run the same scan again it's possible for amass to keep track of the changes that's occurred.
But how do you do this?
For example let's say that you've run amass enum -d tesla.com last month and you wish to see the changes in scan request on the same domain.
You can simply do amass track -d https://t.co/1oT7xWHZR8 and it'd show you fresh targets.
For example let's say that you've run amass enum -d tesla.com last month and you wish to see the changes in scan request on the same domain.
You can simply do amass track -d https://t.co/1oT7xWHZR8 and it'd show you fresh targets.
Fresh targets are likely to be vulnerably and we can possibly find juicy information from it.
That's a wrap!
If you enjoyed this thread:
1. Follow me @thebinarybot for more of these
2. RT the tweet below to share this thread with your audience
If you enjoyed this thread:
1. Follow me @thebinarybot for more of these
2. RT the tweet below to share this thread with your audience
https://twitter.com/973520902343180288/status/1562795715835105285
• • •
Missing some Tweet in this thread? You can try to
force a refresh
