Through WebRTC you can get a list of all local (behind NAT) interfaces in the system.
Jsfiddle.net/GZurr javascript code
sampleIt works only in browsers that support WebRTC, currently it is
Firefox and Chrome .
')
This can be used to obtain a more accurate fingerprint of the browser or, for example, expose the characters sitting behind the VPN to
CALCULATE BY IIP AND CAPTURE E ** LNIKFor ease of use, I made a js-sniffer, which can be inserted into the page and it is convenient to view the result of its work:
zhovner.com/jsdetectorJust paste the code on the page:
<script src="//zhovner.com/jsdetector.js?name=test"></script>
Where test needs to be replaced with a word for which the result of the sniffer will be available:
zhovner.com/jsdetector/testFrom noteworthy in the script - the definition of addresses of user resovlera.
The script generates several random subdomains of the type RANDOM.detect.zhovner.com and accesses them via HTTP.
The * .detect.zhovner.com zone is delegated by the wildcard to the NS server, which logs resolver requests, and when accessing sites, returns the source address from which the resolver came.
It should be borne in mind that the SSL certificate is valid only for the root domain, but not for * .detect.zhovner.com, so if you embed the script on https-sites, you will see a warning about the content that is not downloaded via HTTPS.
UPD:Still, it turns out, you can detect neighboring hosts on the network
dl.dropboxusercontent.com/u/1878671/enumhosts.html