Read a name and a URL
In www.example.com/guide, .com is the TLD, example the registered second-level name, www a subdomain, and /guide a website path. The https:// scheme specifies how to access the resource.
In project.coagent, used here as an illustrative example, .coagent is an extension within its Web3 naming system. This is not a statement of availability or a promise of recognition by public DNS.
DNS: locate a destination
A DNS resolver looks up records for a name. A/AAAA records can specify IP addresses; CNAME can reference another name; MX records identify mail servers. The browser then connects to the service hosting the website. A registrar handles registration, a DNS provider publishes records, and hosting stores content: these can be different providers.
The same DNS domain can serve a static page, a shop or a dapp interface. Renewals, transfers and terms depend on the registry and service agreement.
Blockchain: name, registry and resolver
A registry associates a name with control information; a resolver supplies records that compatible applications can interpret, such as a wallet address or a content reference. Each naming system has its own rules and support: an ENS integration does not imply support for every Web3 domain.
A blockchain namespace does not automatically become part of the public DNS root within the ICANN system. Identical text can have different meanings in separate registries: always identify the naming system and network.
Register, mint and receive
- Choose the name. Check availability, terms and registration type on the relevant platform.
- Complete registration. A purchase or reservation may happen before minting.
- Check the wallet and network. The receiving wallet specified for minting will hold the domain on-chain.
- Approve minting. The token is created or assigned under the system’s rules. Verify the result in the correct registry or explorer.
- Configure records. Holding a name does not automatically configure a website, payment service or email.
A wallet is an interface to an account: the token is recorded on the blockchain, not “inside” a phone file. With a non-custodial wallet you control the keys; a custodial service also depends on its custody arrangements.
Owner wallet versus payment address
Do not confuse the account holding the domain with the payment address stored in a record. They may match or be configurable separately, depending on the system. Before a transfer, check the resolved name, full address, network and supported asset.
A readable name does not convert tokens or automatically bridge funds between networks. Support in the sender’s wallet is separate from the recipient owning a domain.
DNS and blockchain can work together
DNSLink uses TXT records to point a DNS name to IPFS content or an IPNS name. ENS supports DNS integrations for names meeting the relevant requirements, including DNSSEC. These are technical bridges, not a universal merger of naming systems.
You can keep an accessible HTTPS address while adding a verifiable component or a Web3 name for compatible applications. Document both routes for your visitors.
Answers to common questions
Is a Web3 TLD the same as an ICANN TLD?
No. An extension in a blockchain namespace is not automatically delegated in the public DNS root. Tools must recognize that naming system.
Do all Web3 domains have no renewal fees?
No. Conditions vary by system and name type. Check duration, renewal terms, network fees and separate hosting or service costs before purchase.
Does transferring a domain also transfer the website?
Not automatically. The name token, website files, hosting accounts and records are separate components. A complete transfer must specify what is included.
Sources and further reading
Primary documentation consulted for this guide. Product, network and integration support can change: check current requirements before configuring a service.