Where a Web3 name works, and where it does not
In wallets, well. In most browsers, not without help. Here is the honest map, and how people use a Web3 name alongside a normal domain.
In wallets, well. In most browsers, not without help. Here is the honest map, and how people use a Web3 name alongside a normal domain.
A Web3 name works wherever the software reading it knows how to look it up. Wallets that support the naming system do this well. Ordinary browsers mostly do not, because they look names up through the DNS — the system that has run the web for forty years — and a Web3 name is not recorded there.
That is not a defect waiting to be fixed next month. It is the consequence of the name being held on a blockchain instead of in a registrar’s database. The practical result is that a Web3 name sits next to a normal domain and does a different job, rather than replacing it.
Type the name into the send field and the wallet looks up the address behind it. This is the core use: a readable name instead of a forty-character address. Support varies by wallet and by naming system, so check the provider’s own list before relying on a particular app.
A few browsers include support for certain Web3 naming systems, and extensions add it to others. When it works, the name opens a site the way a normal domain would. When it does not, the browser treats it as a search term.
On an invoice, a profile, a stream overlay or a shop sign, the name works as a readable label whether or not the reader’s software can resolve it. For many holders that is most of the value.
Chrome, Safari, Firefox and Edge do not resolve Web3 names without help. Anyone who types yours into one of them, without an extension, will see search results rather than your site.
A Web3 name is not an email address and cannot receive mail. If you need email on your brand, that still requires a normal domain.
Search engines and most apps link to normal domains. A Web3 name shared in a chat or a post is usually shown as plain text rather than a clickable link.
Before a Web3 name goes on anything you cannot change — packaging, signage, a printed run — test it in the places your audience will actually use: their wallets, their phones, the browser they have. Ten minutes of testing costs less than a reprint.
The pattern that works for most businesses is simple. Keep a normal domain for the website and for email. Use the Web3 name where it is strongest: as the payment address, as the handle on profiles, and as the readable line on printed material. Point the Web3 name’s website record at the normal domain, so anyone whose software can open it lands in the same place.
Each ending page in our catalogue lists four example addresses and what someone would use each for. Most of them are payment or profile uses, because that is where the names work today.
Not on its own. Mainstream browsers resolve names through the DNS, and a Web3 name is not in it. Some browsers and extensions add support for certain naming systems; check what the provider lists for the ending you are buying under.
You can, but the people reading the card may not be able to open it. The safer pattern is a normal domain for the website and the Web3 name for payments and profiles, or both printed together.
That is where it works best, in wallets that support the naming system the name belongs to. Always confirm with a small test payment before giving the name out for anything large.
Probably, but we do not promise it, and you should not buy on that basis. Buy a name for what it does today.
With the practical limits clear, the catalogue shows which ending fits what you want the name to do.