Browsers that support Web3 domains

"Supports Web3 domains" covers three different designs. A browser can carry the resolver itself and read the name from the chain on the reader's own device. It can send the lookup to a server run by the browser's maker, which reads the chain on the reader's behalf. Or it can pass the name to a public gateway and show whatever the gateway returns. All three put a page on screen; only in the first does the reader's own device decide what a name points to. Each entry below says which design the browser uses, where its maker states it.

At a glance

Browser	Resolves	Who answers the lookup	Platforms	Source
Theseus Navigator	Bitcoin Cash Domain Names (BCDN): .bch, .x, .p2p, .sia and the rest of the registry	The browser, on the device	Windows, Android	Published
LibreWeb	Freedom Names (.fn); short names backed by Bitcoin Cash	The browser's own node, on the device	Linux, Windows	Open
Brave	ENS (.eth), SNS (.sol), Unstoppable Domains (.crypto, .x, .nft, .dao, .wallet, .blockchain, .bitcoin, .zil and newer)	Brave's own servers	Windows, macOS, Linux, Android, iOS	Open
Opera	Unstoppable Domains (.crypto, .nft, .x, .wallet, .zil); IPFS	Not stated; IPFS through a gateway	Windows, macOS, Linux, Android, iOS	Closed
Osiris	None documented	—	Windows	Closed · discontinued
Puma Browser	ENS, Handshake, Unstoppable Domains; IPFS	Not stated	Android, iOS	Closed
Aloha Browser	ENS, Handshake, Unstoppable Domains	Not stated	Android, iOS, Windows, macOS, Linux	Engine open

As stated by each maker, 11 October 2026. A TLD list appears only where the maker publishes one; "not stated" means the maker does not say how the name is resolved.

1. Theseus Navigator

Theseus Navigator (also published as Theseus.X) is a Chromium-based browser built on Electron by Silent Mode. Its distinguishing choice is that the resolver is built into the browser itself: Ariadne's Thread keeps a copy of the registry, refreshes it from the Bitcoin Cash chain, and answers name lookups on the device. There is no daemon to install, no DNS setting to change and no root certificate to trust, and no resolver service decides on the reader's behalf what a name points to.

The names it opens are Bitcoin Cash Domain Names (BCDN), recorded on the Bitcoin Cash Name Registry (BCNR). Every dotted address is checked against that registry before anything else. A name found there opens from wherever its record points: content stored on chain, a site on the Sia storage network, or a server reached directly by IP, with the connection's TLS certificate pinned to a fingerprint published on chain. A name the registry does not hold falls through to ordinary DNS, so the same window also opens the regular web. A badge on every page states which registry answered — BCNR or ICANN — and which backend served the page.

Which Web3 domains Theseus resolves

Every TLD on the registry, with the list refreshed from the chain at every launch. Among the public TLDs are .bch, .x, .p2p, .sia, .bit, .nav, .dex, .cex, .neo, .asm, .nt and .test; the current list is published by the registry's tracker. Theseus does not resolve ENS, Unstoppable Domains or Handshake names.

How a Bitcoin Cash Domain Name works

Every TLD on the registry is a CashTokens certificate on the Bitcoin Cash chain, and so is every name under it: registering a name through Sirius.X mints the certificate to the buyer's wallet, and whoever holds it controls the name; nobody, the registry's operator included, can take it back. Its records say where the name points — content stored on chain, a site on Sia, a server's IP address with the fingerprint its TLS certificate must match, or a redirect. Ordinary DNS-style records (A, MX, TXT and the rest) can sit beside them in a manifest the owner signs off chain, so changing them costs no transaction. A name can be sold in a single transaction without an escrow: the certificate and the payment move together, so a seller cannot lose the name without being paid. A TLD's owner can set a flat price, require approval for each registration, freeze the TLD, or take it private. While the registry is in alpha, new TLDs are minted by its operator, and anyone can propose one on Sirius.X.

To start quickly, a resolver loads a snapshot of the registry instead of reading the whole chain. The tracker signs these snapshots and publishes them to Sia and to Nostr, each with a root hash that anyone can recompute; a snapshot that does not match is discarded and the list rebuilt from the chain. The Sirius.X documentation covers registration, records, hosting a name on Sia, on a server, or on both, and how to verify any of it independently.

What else is in it

• A Tor switch with pluggable transports, off by default.
• Fingerprinting defences for time zone, locale, language, geolocation and media-device labels.
• Cookies, cache, storage and history cleared on quit unless kept on purpose; camera and microphone denied by default; WebRTC limited to public addresses.
• A local password vault derived from a BIP-39 seed, filling only on request.
• A window.bcnr interface that lets pages resolve names and list the registry's TLDs.
• Extensions, including add-ons published under BCNR names.

On Android the same Ariadne's Thread resolver ships in the Ariadne app, which resolves these names on the phone and, through a local VPN, for every app on the device, without root. The Windows installer offers the equivalent system-wide resolver as an option, so other browsers on the machine can open the same names. The trade-off is the certificate: the system-wide resolver installs a local root certificate to serve these names over TLS, while Theseus on its own checks them against the chain and leaves the system's certificate store untouched. Without either, any browser can reach a name through the public gateway at navigate.st/bns/<name>/, which resolves it on a server and so asks the reader to trust that server.

Theseus is alpha software, and the registry currently runs on Bitcoin Cash's test network. The Windows builds are unsigned: the release page lists a SHA-256 checksum for every build, and checking it before running the installer is the step that replaces a signature. This site can be opened in it as coinspectrum.x, the same pages served from the Sia network.

Website: silentmode.st/theseus · Theseus.X: theseus.x · Windows: installer, portable · Android: Ariadne APK · Checksums: releases · Source: Theseus, Ariadne

2. LibreWeb

LibreWeb, by Melroy van den Berg, is a browser for a different kind of web rather than a new window onto the existing one. Pages are written in Markdown, with no HTML and no JavaScript, and a built-in editor makes publishing a page no harder than writing it. Names and content come from Freedom Names, the same author's peer-to-peer naming network, under the fn:// scheme: the browser starts a Freedom Names node on the reader's machine and resolves through it, with no server in between.

Freedom Names has two kinds of .fn name. A self-certifying name, such as blog.<key>.fn, belongs to whoever holds the matching key and needs no chain at all. A short bare name, such as blog.fn, is a CashTokens NFT on the Bitcoin Cash main chain: the earliest confirmed claim wins, enforced by the chain's consensus rather than by a registrar. Page content is stored by the nodes themselves and replicated across several peers, in place of IPFS. The same node runs a local DNS server for .fn, so other browsers on the machine can open those names once pointed at it. LibreWeb is open source under the MIT licence, written in C++ with GTK, and released for Linux and Windows, with macOS packaging in progress; its author describes it as a working alpha.

Website: libreweb.org · Download: releases · Source: github.com/libreweb/libreweb-browser · Names: Freedom Names

3. Brave

Brave is the browser that documents its Web3 name support most precisely. It resolves ENS (.eth), the Solana Name Service (.sol) and Unstoppable Domains — .crypto, .x, .nft, .dao, .wallet, .blockchain, .bitcoin and .zil, with newer Unstoppable TLDs added in later releases. ENS arrived in March 2021 and .sol in early 2023; .sol works on desktop, Android and iOS, the other two on desktop and Android.

For a TLD that ICANN does not use, Brave sends the name to the matching service by default; for one that ICANN does use, it asks DNS unless the reader opts in. Since February 2023 the lookups go through Brave's own servers rather than straight to a chain node. Brave also keeps the right to switch a TLD off over a namespace conflict or phishing risk, and has dropped two Unstoppable TLDs since. Its local IPFS node was removed in August 2024; IPFS content behind a name still loads, through a public gateway. Brave is open source under the MPL-2.0 licence, with a built-in wallet.

Website: brave.com · Download: brave.com/download · Source: github.com/brave/brave-browser · Name support: Brave crypto DNS

4. Opera

Opera, from Opera Norway, was the first mainstream browser to open Unstoppable Domains names: .crypto on Android in March 2020, on desktop and iOS in April 2021, and .nft, .x and .wallet from February 2023. It also opens ipfs:// and ipns:// addresses through an HTTP gateway, dweb.link by default and changeable in settings. Opera has published no full list of the TLDs it resolves.

Much of the crypto layer around that support has since gone. Opera stopped updating its separate Crypto Browser in March 2024, and removed the built-in crypto wallet from Opera One and Opera GX on 1 January 2026. The announcements say nothing about name resolution either way, and Opera has published nothing since on whether .crypto names still open. It is a Chromium-based browser and is not open source.

Website: opera.com · Download: opera.com/download · Android: Google Play · Source: closed

5. Osiris

Osiris, from the ACENT project, still appears on most lists of Web3 browsers. It was a desktop browser with a built-in wallet for Ethereum, TRON and ACENT's own token, ad and tracker blocking and a dApp store. No source, from its makers or anyone else, shows that it ever resolved a Web3 domain, and it is no longer developed. Its former website now forwards to an unrelated domain, which is why no link is given here: a download offered under the Osiris name today has no maker standing behind it.

Website: none (discontinued) · Source: closed

6. Puma Browser

Puma Browser, from Puma Technologies, is a mobile browser for Android and iOS. Its maker says it opens ENS, Handshake and Unstoppable Domains names and IPFS content typed straight into the address bar, most recently in a post of July 2026. Puma has carried IPFS since 2020 and previewed Handshake in 2021, when a name had to be typed with a trailing slash. It publishes no TLD list and does not say how names are resolved. It now presents itself as an AI browser with built-in language models and wallets, and is not open source.

Website: pumabrowser.com · iOS: App Store · Android: Google Play · Name support: Puma blog · Source: closed

7. Aloha Browser

Aloha Browser, from Aloha Mobile in Cyprus, runs on Android, iOS, Windows, macOS and Linux, with a free built-in VPN and ad blocking. Its maker lists Unstoppable Domains, Handshake and ENS among the names it opens; Handshake support arrived in 2022 and needed no configuration. The current store listings say only that it supports Web3 domains, and there is no published TLD list or account of how the lookup is made. Its Chromium-based engine, Aloha Core, is published as open source; the rest of the browser is not.

Website: alohabrowser.com · Download: alohabrowser.com/download · iOS: App Store · Android: Google Play · Engine source: github.com/AlohaBrowser/aloha-core

One name, two owners: .x

Web3 names have no common root, and the clearest case is .x. Unstoppable Domains sells names under .x, and Brave and Opera send .x to Unstoppable. The Bitcoin Cash Name Registry also has a .x, and Theseus sends it there. The same address can therefore belong to two different holders, and the page that opens depends on the browser it is typed into. Brave's stated policy anticipates this — it reserves the right to switch off a TLD over a namespace conflict — and Theseus answers it from the other side, by naming on every page the registry that answered. A reader moving a Web3 name between browsers should check which registry each one asks before trusting the result.

Questions