Since the purpose of this blog was to show how to create a website and mirror it on various hidden services, below is a list of mirrors of the current blog that have been compiled.

Github Pages Instance

This page is hosted by github and is part of the repo we originally created. This does require that the the NoIP.com be set up to point to your github pages instance

GCE VM Instance

This is the Live instance hosted in our VM.

Mnemonic Redirects

Since most of the Hidden have hashes as names, It is convenient to have these mnemonic redirects. For example, to get the hash for the onion v2 service simply navigate to /onion.v2/ and you will get redirected to /bithxedusrw236ji.onion.sh/ so you now have the full onion hash.

Expanded Reverse Proxies

While on clearnet, it is usefull to be able to verify if the hidden services are still functioning. For this we use some reverse proxy settings in lighttpd. Now we can simply bracket our hidden services address in slashes (/) and determine if its up based on if it resolves.

Onion v2 Instance

These are the instances that reference the Onion (version 2) hidden service hosted on my VM. If the VM goes down, the live onions will go down. The archives and google cache will survive.

Onion.ws Inproxy

The Onion.ws Tor2Web inproxy will bridge traffic from clearnet to Tor. If either the onion.ws server or my VM goes down, then the live link won’t be available. The archive links will survive.

The Onion.link Tor2Web inproxy will bridge traffic from clearnet to Tor. If either the onion.link server or my VM goes down, then the live link won’t be available. The archive links will survive.

Onion.sh Inproxy

The Onion.sh Tor2Web inproxy will bridge traffic from clearnet to Tor. If either the onion.sh server or my VM goes down, then the link won’t be available. Be aware that this inproxy uses SNI TLS which some browsers do not support.

Onion v3 Instance

These are the instances that reference the Onion (version 3) hidden service hosted on my VM. If the VM goes down, the live onions will go down. The archives and google cache will survive.

Onion.ws Inproxy

The Onion.ws Tor2Web inproxy will bridge traffic from clearnet to Tor. If either the onion.ws server or my VM goes down, then the live link won’t be available. The archive links will survive.

I2P eepsite Instance

These are the instances that reference the I2P (eepsite) hidden service hosted on my VM. If the VM goes down, the live eepsite will go down. The archives and google cache will survive.

I2P.xyz Inproxy

The I2P.xyz I2P Inproxy (Russian) will bridge traffic from clearnet to I2P. If either the i2p.xyz server or my VM goes down, then the live link won’t be available. The archive links will survive.

I2P Short Form

These are the instances that reference the I2P (eepsite) short form hidden service hosted on my VM. The short form requires a type of I2P dns service. If the I2P dns service or the VM goes down, the live eepsite will go down. The archive links will survive.

Freenet Instance

These are the instances that reference the Freenet (freesite) site. Freesites are distributed across the network as soon as they are inserted. The freesite will persist even if my VM goes down, so long as it is routinely accessed by someone. Sites that fall into disuse are eventually garbage collected.