Three layers to check
Name: does the app recognize the namespace? Destination: is the record a URL, CID or address in the expected format? Action: can the tool open the website or perform the operation on the chosen network? If one layer is missing, the journey breaks.
A practical compatibility matrix
| Goal | What you need | What is not automatic |
|---|---|---|
| Open an HTTPS URL | An ordinary Web browser | The site must be online with valid HTTPS |
| Type a blockchain name | Compatible resolver, extension or access route | Not every extension is recognized |
| Open IPFS content | A node or gateway and retrievable content | A CID does not guarantee persistence |
| Use a name for payments | A wallet with supported resolver and network | Check the address; no automatic bridge |
| Have an email inbox | Compatible mail service and configuration | A domain alone does not create email |
| Sign a transaction | Authorized wallet/account on the correct network | Read permissions, action and any fees |
Traditional browsers and Web3 websites
A dapp published at an HTTPS URL can generally open like an ordinary page. Signing an action may require a compatible wallet. That is separate from entering a blockchain name into the address bar.
A gateway exposes distributed content through HTTP/HTTPS. The browser talks to the gateway, which retrieves the content. This is convenient but adds reliance on that service, its policies and availability. HTTPS certificates apply to the access route; they should not be assumed for every blockchain name.
Payments: name, network and asset
Before a payment, check that the sender’s wallet supports the domain’s resolver and displays the expected destination. The network and asset must be supported by the recipient. Registration on one network does not make every address usable on all other networks.
For example, Freename documentation specifies a resolver integration for use with MetaMask. Resolving the name is not a bridge. This guide does not initiate transfers: compatibility checks come before any operation.
Email, identity and accounts
An extension such as .dmail can be chosen for an identity or messaging project, but a name alone does not create an SMTP/IMAP mailbox. A compatible email or messaging service and its required configuration are separate.
Likewise, owning a name does not let you sign into every website. The site must implement a suitable login method. Connecting a wallet, signing a message and authorizing a transaction are different actions: read the request.
Private data and public content
Content published on a public network is not private simply because its name is hard to guess. Controlling the name does not mean controlling every content copy. Private areas require planned permissions, encryption and key management.
A smart contract cannot independently observe a physical delivery or the weather. External information requires sources and mechanisms, often called oracles, with their own trust assumptions. “On-chain” does not remove the need to evaluate input data.
A compatibility checklist
- Record the exact name, naming system and domain network.
- Check published records and the permissions of the account managing them.
- Review current support in the browser, resolver, gateway or wallet.
- Test on desktop and phone, including without your extensions.
- Provide an alternative HTTPS URL and clear instructions where needed.
- Repeat the checks after changes to records, applications or infrastructure.
Answers to common questions
Why does my domain work in an app but not in my browser?
The app may integrate a resolver that your browser does not use. Check the supported namespace and the provider’s intended route: gateway, extension or resolution configuration.
Does a gateway make everything decentralized?
No. It provides Web access to another network but introduces reliance on the gateway. File distribution and gateway access are separate concerns.
Is a payment domain a bank account or payment service?
No. It can be a name that compatible software resolves to an address. Custody, transfers, conversions and other services require separate systems.
Sources and further reading
Primary documentation consulted for this guide. Product, network and integration support can change: check current requirements before configuring a service.