You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using fierce to enumerate subdomains, we are presented with the corresponding IP addresses as the results roll in, and at the end, the subnets where hostnames were found.
On Oct 8, 2017 7:17 PM, "aesthese" ***@***.***> wrote:
When using Fierce to enumerate subdomains, we are presented with the
corresponding IP addresses as the results roll in, and at the end, the
subnets where hostnames were found.
Like this:
[...]
192.30.253.125 live.github.com
192.30.253.124 live.github.com
192.0.2.1 ns1.github.com
192.0.2.2 ns2.github.com
Subnets found (may want to probe here using nmap or unicornscan):
192.0.2.0-255 : 2 hostnames found.
192.30.253.0-255 : 23 hostnames found.
This would be extremely useful in subbrute as well!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#64>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAf2NyHDljjAwa68cBVHGtxlm7o1KB8Rks5sqYJGgaJpZM4Px8dz>
.
Thanks for the quick reply! Printing the record data gets quite cluttery. What I like about the way fierce does it, is that the output is so clean, and it shows me what IP ranges to inspect further.
When using
fierce
to enumerate subdomains, we are presented with the corresponding IP addresses as the results roll in, and at the end, the subnets where hostnames were found.Like this:
This would be extremely useful in subbrute as well!
The text was updated successfully, but these errors were encountered: