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

brute force is too slow! #72

Open
marcelo321 opened this issue Dec 23, 2019 · 3 comments
Open

brute force is too slow! #72

marcelo321 opened this issue Dec 23, 2019 · 3 comments

Comments

@marcelo321
Copy link

Hello,

I shortened the wordlist to 1k subdomains and run the script again at 100 threads and still 15 minutes and keeps going...

that means that if i try the main wordlist of 130k subdomains it would take +5,40 hours

Is there any way to speed up this? what about the resolvers.txt? can i update it somehow? what type of resolvers and where should i look for them?

@TheRook
Copy link
Owner

TheRook commented Dec 24, 2019 via email

@RaduNico
Copy link

Hello,

I've tried using the -t option to check some basic subdomains - all 1 letter subdomains in the range a-z0-9. I ran subbrute for about 2 hours and it produced no output. Would using a custom list of domain names help?

Radu

@3x1l3l4bs
Copy link

Hi @RaduNico I am not a developer member of this project but I'm an avid penetration tester and i would highly suggest using a custom word list as it helps to narrow down the results also since this is a brute force tool the time it takes can be affected by many factors such as your internet speed, CPU/GPU power etc and you said you tried a-z0-9 that means your cpu and/or GPUs is trying to find every possible combo of every letter in the English language and every number 0-9 which is a lot of strain on any normal computer

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

4 participants