Update FindFrontableDomains.py #13
Open
Conversation
This file contains hidden or 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
|
<3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added the --recursive option which will loop back over any domains find to check for sub-sub.domains.
eg if the domain sub.target.com is found, it will then carry out all the enumeration again for sub.target.com, leading to sub.sub.target.com being enumerated and checked for fronting - works a treat for a lost of targets and bit faster than using an output file from Run 1, as input into Run 2.
Also incorporated some great stuff from @PwnDexter to improve sublister stuff, and @m0rv4i for the checking the TLS version supported Microsoft domains (aspnet,azureedge,msecnd)