The onion service — part of the open core

🧅 The Onion Mirror

The Sanctuary publishes a v3 onion mirror: the same site you are reading now, reachable over Tor — no DNS lookups, no exit node, no tracking of who visits. It is the same nginx proxy that serves this page, published as a hidden service.

the address (stable — keys persist in the tordata volume) em7qyoc4bztqxskpls5ro7qoluel35jxfwmfmeus7a35ji4kfelqxeid.onion

How to visit

Open Tor Browser (or any Tor client), paste the address above into the URL bar, and press enter. The mirror answers over the Tor network — your traffic reaches the site through three hops of relays, and the site never sees your real IP or your DNS queries.

What it is — and what it is not

It is a mirror of this site. The container runs tor -f /etc/tor/torrc and publishes the internal nginx proxy as a v3 hidden service. It is outbound-only: no ports are opened on the host or router.

It is not a proxy. The torrc sets SocksPort 0 — the SOCKS proxy is disabled, so this container cannot be used to browse the wider web anonymously, and nothing on the box routes outbound traffic through it. It exists to let Tor users reach this site, not to anonymize traffic to anywhere else.

It is stable. The hidden-service keys persist in the tordata volume, so the address stays the same across restarts.

The onion service is listed under the Open — yours to run half of the open core: the deploy/tor/ Dockerfile, the torrc, and this page are all in the repository. Tor is the visitor's choice — the clearweb site remains the primary door, and nothing here changes what the site itself does.