Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve AltDNS output with Gobuster rather than AltDNS #14

Open
glen-mac opened this issue Jun 14, 2017 · 3 comments
Open

Resolve AltDNS output with Gobuster rather than AltDNS #14

glen-mac opened this issue Jun 14, 2017 · 3 comments

Comments

@glen-mac
Copy link

glen-mac commented Jun 14, 2017

I have found in the past that resolving the output of AltDNS with gobuster is much faster than allowing AltDNS to do it alone.

Anyone is welcome to do their own speed comparisons, but i think stripping the subdomains from the AltDNS output and feeding them to gobuster for final resolving could speed the process up quite a bit.

@glen-mac
Copy link
Author

Same goes for the enumall bruteforce

@anshumanbh
Copy link
Owner

I am using a custom Go script to resolve domains - https://github.com/anshumanbh/brutesubs/blob/master/scripts/wait-for-tools-start-altdns.sh#L20

Not sure what part you are referring to?

@RyanLongVA
Copy link

I think he's talking about the resolve feature, known as -r, within altdns (which takes a horrendous amount of time), and for enumall, if you want time consistency in this end too, removing the option to bruteforce (-w) definitely helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants