Closed Ice3man543 closed 4 years ago
Closing this as its out of scope for this project!
Curious to know why this out of scope. Seems like a very useful feature to have for large domain exploration.
In addition, I think the current behavior is inconsistent:
in other words, as things work now there's no consistent way to filter all the subdomains in a non-top, wildcard domain.
What's the problem (or question)?
The tool currently performs wildcard elimination but only for root domains. For example, .luminate.com is not a wildcard while .store.luminate.com most certainly is. Therefore, we need to perform wildcard enumeration recursively and handle such edge cases in order to save time and resources.
Do you have an idea for a solution?
Apply Wildcard elimination logic recursively for each subdomain found.
How can we reproduce the issue?
Run ./subfinder -d luminate.com -nW