Opening a .onion
Pasting somehash.onion into Chrome or Safari does nothing — those browsers don't speak Tor. Pick one of these:
option 1
Brave — private window with Tor
Already have Brave? Easiest path, zero installs.
- Open Brave.
- File → New Private Window with Tor (⇧⌘N on macOS / Ctrl+Shift+N on Windows-Linux, then 'New private window with Tor').
- Paste the .onion URL.
gotchas
- .onion resolution works only in the Tor-mode window — a regular private window will fail.
- Brave's Tor mode does not give you the same fingerprint protection as Tor Browser proper. Fine for reading; not a strong anonymity guarantee.
option 2
Tor Browser — the real thing
Strongest anonymity. Download once, use forever.
- Download Tor Browser from torproject.org/download.
- Verify the signature if your threat model is real (instructions on the same page).
- Open it, wait for the 'Bootstrapped 100%' moment, paste the .onion URL.
gotchas
- First connection to a brand-new .onion takes 30 seconds to 2 minutes — Tor has to look up the hidden service descriptor.
- Tor Browser refuses to install unsigned extensions in the normal way. To add ouija-onion-resolver here, use about:debugging → 'Load Temporary Add-on'.
option 3
ouija-onion-resolver extension — type yourname.stacc instead
Memorable URLs that resolve to .onions via on-chain AllDomains lookup. Works alongside #1 or #2.
- Install the extension on Chrome, Brave, or Firefox: chromewebstore.google.com/detail/ouija-onion-resolver/ (or the Firefox add-on at addons.mozilla.org).
- Type yourname.stacc (or any registered AllDomains TLD) in the URL bar.
- Extension intercepts pre-DNS, reads the on-chain NFT owner, derives the matching .onion via the same identity-collapse math this site uses, and redirects the tab.
gotchas
- The redirect target is still a .onion, so the underlying browser has to be Tor-capable (Brave private+Tor or Tor Browser) for the hop to actually load.
- Tor Browser users: install via about:debugging because the AMO-signed version may lag the latest Chrome Store build.
Why bother?
The clearnet mirror at publish.ouija.social/sites/<onion> works in any browser, but it's served by us — we can see your IP, we can be served subpoenas, we can be DDoSed. Loading the same content over the actual .onion means:
- End-to-end encrypted to the hidden service — no CA in the middle.
- Your IP is hidden from the hidden service operator (us).
- The hidden service operator's IP is hidden from you (and adversaries).
- No single party can take the page down at the DNS or CA layer.
The convenience-hosted .onion still has a single point of failure (us), so for maximum properties self-host the HS yourself — the 4-command recipe uses the same burner mnemonic the site already gave you.