Open .onion links the way they are meant to be opened.

Chrome does not speak Tor. This extension points Chrome at a SOCKS5 listener you already run — the Tor daemon on 9050 or Tor Browser on 9150 — and routes only .onion hostnames through it. Everything else keeps going out directly, untouched.

Clicking the toolbar icon opens the tor.lt directory. Right-click it for routing and settings.

open tor.lt directory

routing: — search: —

;; tor routing proxy · pac

Route .onion through Tor

A PAC script sends *.onion to SOCKS5 and returns DIRECT for everything else.

proxy: —

Enable Tor routing Takes over Chrome's proxy setting for this profile while it is on. SOCKS5 hands the hostname to Tor instead of resolving it locally, so the address never reaches a clearnet DNS resolver.

SOCKS host

SOCKS port

;; presets

not tested

No Tor running?

macOS: brew install tor && brew services start tor gives you a SOCKS5 listener on 127.0.0.1:9050. Or just launch Tor Browser and use port 9150 — its listener is open while the browser is.

;; Chrome is not Tor Browser: routing hides the address from your resolver and reaches hidden services, but it does not give you Tor Browser's fingerprinting defences.

pac: inactive ;; only *.onion is proxied

;; onion search engines

Search engine

Used by the onion omnibox keyword and the “Search …” context menu.

—

Query template ;; %s is replaced by the encoded query

Preview

—

engine: — ;; addresses tracked by the tor.lt directory

;; behaviour pages · links

Guard .onion navigation With routing off, stop before the request leaves and show what happened instead of a blank ERR_NAME_NOT_RESOLVED. With routing on, explain SOCKS failures. Mark .onion links on pages Dotted underline plus a small tag, so a hidden service link is obvious before you click it.

Directory URL ;; opened by the toolbar icon

;; settings sync with your Chrome profile tor.lt