Sublist3r VS ssimap

You cannot hide anything on the internet anymore, the full IPv4 range is scanned regularly by multiple entities. If you open a port on a public IP it will get found.

If it's a obscure non-standard port it might take longer, but if it's on any of the standard ports it will get probed very quickly and included tools like shodan.io

The reason why I'm repeating this, is that not everyone knows this. People still (albeit less) put up elastic and mongodb instances with no authentication on public IP's.

The second thing which isn't well known is the Certificate Transparency logs. This is the reason why you can't (without a wildcard cert) hide any HTTPS service. When you ask Let's Encrypt (or any CA actually) to generate veryobscure.domain.tld they will send that to the Certificate Transparency logs. You can find every certificate which was minted for a domain on a tool like https://crt.sh

There are many tools like subdomain.center, https://hackertarget.com/find-dns-host-records/ comes to mind. The most impressive one I've seen, which found more much more than expected, is Detectify (which is a paid service, no affiliation), they seem to combine the passive data collection (like subdomain.center) with active brute to find even more subdomains.

But you can probably get 95% there by using CT and a brute-force tool like https://github.com/aboul3la/Sublist3r

Sublist3r

sublist3r = https://github.com/aboul3la/Sublist3r

Try following this step too - click here

For those asking what tool I was using, its called sublist3r (https://github.com/aboul3la/Sublist3r). It uses open source intelligence gathering (public info) as well as brute force to try and enumerate subdomains.

That said, keep in mind that not everything is going to find its way indexed in Google. If it's subdomains you're after, you can use tools like Sublist3r or Sudomy to pull data from multiple sources (not just DNS).

In a real-world scenario. You're likely to come across a target with more than one domain, each having it's own subdomains. There's plenty of tools that you can use to discover these. Again, PyRCON offers some options for this but I like tools such as sublist3r and publicly available records such as security trials.

Kali has sublist3r

The downside is, wildcard DNS fills the results with false positives because every subdomain will return an IP address. There was an issue raised for sublister a few years ago (still open) that raised this exact issue: https://github.com/aboul3la/Sublist3r/issues/118

Happy to help. I believe wireshark can automatically decrypt SSL if it listens to the key exchange upon first connection. Just to clarify, if your requests are being made by localhost to a bound port, people on your network can't sniff that kind of thing with wireshark, since the request/response never leaves the local computer. Other avenues of discovery might try looking in /robots.txt or recursively searching all hrefs (if you have an href somewhere on your site that links to the pages that should be hidden). An example of which you can find in my ssimap project.

I posted once about SSI injection. I went on to learn python and made a script that automates it, although it doesn't use escape characters at all, so it will only be able to exploit the vulnerability if it's 100% vulnerable with no efforts to mitigate the vulnerability at all. I've been working on a monero mining pool and have been loving python, also wrote this downloader to get anime from wcostream quickly. That was a fun project because the file location is obfuscated by javascript, so I had to learn a little javascript along the way. As for hacking, I still haven't succeeded in any bug bounties but I understand networking and HTTP requests on a much more intricate level than a did a few years ago. I'll get there someday, it's a long journey.