Skip to content
Log inDashboard

Web3 names

Names such as vitalik.eth are not part of the ordinary DNS: no registry behind the internet’s root knows them, so a normal resolver, and opdns by default, answers that they do not exist. With Web3 names on, opdns answers them through a gateway, a public service that reads the name’s record on its blockchain and serves the site it points to.

  1. In the dashboard, open the profile’s Settings page.

  2. Under Resolution, turn on Web3 names and save.

  3. Open http://vitalik.eth/ on a device using the profile.

The setting is per profile and off by default. Profiles that leave it off, and queries that identify no profile, keep answering these names as not existing, exactly as before.

Names How opdns answers Where it works
ENS: .eth and every name under it an alias to the same name at the eth.limo gateway: vitalik.eth → vitalik.eth.limo opdns and self-hosted nodes
Unstoppable Domains: .crypto, .nft, .wallet, .x, .bitcoin, .dao and their other names an alias to the name at an Unstoppable gateway only on a self-hosted node configured with a gateway
Handshake: names whose top-level label is not in the internet’s root asked of a Handshake resolver, after the root says the name does not exist only on a self-hosted node configured with a resolver

opdns runs no blockchain client: the gateway or the Handshake resolver does the lookup. Names that only make sense on your own network, such as .local, .lan, .home, .internal or home.arpa, are never sent to a Handshake resolver.

A Web3 name goes through your profile’s policy first, like any name: your lists, your denylist and parental controls can block it, and the gateway name it is aliased to (for example vitalik.eth.limo) is checked too. A blocked Web3 name is answered the way your profile answers any blocked name.

Turning Web3 names on sends the names you open to a third party:

  • for ENS, the eth.limo gateway’s DNS servers see the alias (name.eth.limo), and when the site opens, its web servers see the page you visit, as any website would;
  • for Handshake (self-hosted nodes only), the Handshake resolver set in the node’s configuration sees the name, never your address or network: the node sends it no client subnet.

The privacy policy, section 17 says the same. Leave the setting off if you do not use Web3 sites.

  • Certificates. No public certificate authority issues certificates for .eth names, so https://vitalik.eth/ may show a certificate warning in the browser. http://vitalik.eth/ or the gateway’s own address, https://vitalik.eth.limo/, avoid it.
  • DNSSEC. Web3 answers are never marked as validated: the alias is made by opdns and the blockchain record is read by the gateway.
  • Self-hosted nodes follow the same setting, through the gateways set in the node’s configuration: dns.web3_ens_gateway (eth.limo by default), dns.web3_unstoppable_gateway and dns.web3_hns_upstream (both off unless set).