(Jan 13, 2015 07:51 PM)Nikey646 Wrote:  All network traffic when using a Tor Network goes through Tor-based servers. They then use a local DNS in those servers to convert .onion into IP Addresses like any normal DNS service, otherwise they will either lookup other domains, or re-direct you to your usual DNS.

This is my guess, and the most logical conclusion.

(Jan 13, 2015 07:58 PM)Shoot Wrote:  seems to clear it up a bit because you cant just make your own custom web extensions ( i google'd it ) the only ones you can have are premade.

i thought it was more like they did:
have a VPS and on this VPS ( in the public_html directory ) they have files called "example.onion" then using the web browser to compile the html using this code:

Code

Dim request As System.Net.HttpWebRequest = System.Net.HttpWebRequest.Create("http://192.168.1.1/example.onion")
      Dim response As System.Net.HttpWebResponse = request.GetResponse()

      Dim sr As System.IO.StreamReader = New System.IO.StreamReader(response.GetResponseStream())

      Dim sourcecode As String = sr.ReadToEnd()

      txtSrc.Text = sourcecode
      WebBrowser1.DocumentText = txtSrc.Text

that way it grabs the source of the custom file and the document text compiles the source but i could be wrong.

i did try it with a free host and it did work like that.