add. new gather module cloud_lookup #12234
This module replace the previously pulls:
This module can be useful if you need to test the security of your server and your
More precisely, I use multiple data sources (in order ViewDNS.info, DNS enumeration and Censys)
Your Censys API SECRET.
Your Censys API UID.
You can use a custom string to perform the comparison.
This is the hostname [fqdn] on which the website responds. But this can also be a domain.
A proxy chain of format type:host:port[,type:host:port][...]. It's optional.
The target TCP port on which the protected website responds. Default: 443
Negotiate SSL/TLS for outgoing connections. Default: true
Number of concurent threads needed for DNS enumeration. Default: 8
The URI path on which to perform the page comparison. Default: '/'
Name list required for DNS enumeration. Default: ~/metasploit-framework/data/wordlists/namelist.txt
Set DNS enumeration as optional. Default: true
Specify the nameserver to use for queries. Default: is system DNS
Set to write leaked ip addresses in notes. Default: false
Specify a personalized User-Agent header in HTTP requests. Default: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0
Specify the HTML tag in which you want to find the fingerprint. Default: title
HTTP(s) request timeout. Default: 5
You can also enable the verbose mode to have more information displayed in the console.
For auditing purpose
If successful, you must be able to obtain the IP(s) address of the website as follows:
In this case 'A direct-connect IP address was found' is reported.
However, some disreputable administrators used a simple redircetion (301 and 302)
In this case 'A leaked IP address was found' is displayed but the bypass is NOT effective.
You can also use the 'REPORT_LEAKS' option for write that in the notes.
For some reason you may need to change the URI path to interoperate with other than the index page.
It looks like Travis is failing due to some EOL spaces. You can run