Does ICP boundary node/canister routing currently support resolving Web3 TLDs (e.g. .dao, .crypto, etc.) for HTTPS access, or is that only for ICANN DNS-TLDs right now? What will happen if I setup website.dao as my custom domain for my frontend canister?

Hey @sardariuss Currently, there is no support for Web3 TLDs. The HTTP gateways only support the traditional ICANN DNS TLDs. If you setup a Web3 domain, it just won’t work: the HTTP gateways don’t have a certificate and also won’t know to which canister the traffic should be forwarded.

Are Web3 TLDs (.dao, .crypto) supported?

Developers

ilbert September 23, 2025, 4:25pm 4

Some work in this direction has also been done with the Chain Name System, see Technical Working Group: Naming System - #49 by bartosz

3 Likes

Topic		Replies	Views
Getting HTTPS to work for custom domain Developers	11	127	January 13, 2025
Boundary nodes - custom domains / canisters with IP addresses? Developers	2	801	October 7, 2022
Boundary nodes for API and web traffic Developers	1	50	January 15, 2025
Bitcorn labs presents: a url for daos/dapp on Icp: ic0.io Developers Discussing	12	211	December 19, 2024
Suggestion to Protect DAOs Developers sns	5	262	June 18, 2024

Are Web3 TLDs (.dao, .crypto) supported?

Related topics