tag:blogger.com,1999:blog-2914337944584630860.post3008456550161732006..comments2009-11-14T22:14:54.350-08:00Jon Harthttp://www.blogger.com/profile/02857880233692933624noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2914337944584630860.post-65174388523590415382009-01-28T08:44:00.000-08:002009-01-28T08:44:00.000-08:00@LonerVamp: yeah, great point about SSL. It supports SSL right now, but does not look at the handful of fields that may contain other hostnames/IPs to probe. <BR/><BR/>Thinking about this, my code may be more appropriate as a patch to <A HREF="http://www.cirt.net/nikto2" REL="nofollow">Nikto</A>.Jon Harthttp://www.blogger.com/profile/03410754059921403771noreply@blogger.comtag:blogger.com,1999:blog-2914337944584630860.post-78715504820116538852009-01-27T12:37:00.000-08:002009-01-27T12:37:00.000-08:00You could also try throwing in an https/443 request and see where that takes you. Even sites that properly manage hosts can mismanage the SSL portion. The SSL cert may give away another site or a company name, etc.<BR/><BR/>Interestingly, if you expose to the outside world a site that is meant to only be viewed internally, if it is the one that comes up when an invalid host is sent. Eep!LonerVamphttp://www.blogger.com/profile/15357840241031190415noreply@blogger.com