-
-
Notifications
You must be signed in to change notification settings - Fork 878
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
Subdommain Recursive Search - How-To Examples #451
Comments
Hi, Hope its useful! Regards. |
@Hax0rG1rl anyway I've added an issue to improve the wiki with new scenarios and other things here #456 feel free to comment there any other ideas/needs you want |
Thanks! |
Hey, @Hax0rG1rl you can get a detailed info about what exactly is |
Hi,
Thanks for putting this together. Since your aim here is to make this package one shop for ppl wanting to automate stuff when assessing a domain or alike, here's what I would say can bring some more paid supporters to your side:
However, it would be beneficial if you could add some "best practices" / examples and quickly explain them for someone who wants to play here and start exploring more this advanced alternative, like if you are going down this path, then expect those:
using [one_quick_example_of_an_advenced_config], I, as a user, should have a machine with 2Tb of HDD, 8 GB RAM, wait one week, and burn 10k API requests because it is going deep to level 3 of subdomain guessing.
using [second_quick_example_of_an_advenced_config], I, as a user, should have a machine with 4Tb of HDD, 32 GB RAM, wait three weeks, and burn 80k API requests because it is going deep to level 6 of subdomain guessing.
If you feel this is a stupid idea, adding such potential scenarios, is fine, I don't take things personally :)
Thanks!
The text was updated successfully, but these errors were encountered: