Added DNSDumpster functionality #26
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey Mike,
I found that on engagements I'd often use the subbrute tool but forget to check DNSDumpster. DNSDumpster has proven to be a useful resource that has results bruteforcing has not yielded for me.
Because of that I've added some hacky functionality that gets the results from dnsdumpster.com and adds it to the beginning of subbrutes output when a user specifies the
--dnsdumpsteroption.Note, this functionality also does output these domains when using the regular
--outputfunctionality, but it does not yet have the ability to save the results to JSON.Cheers man,
Shubs