Owning a .brave Domain: My Web3 Experiment
In a nutshell
- Owned a
.bravedomain to test Web3 decentralized ownership—pay once, own forever. - Couldn't add it to my server due to Let's Encrypt incompatibility.
- NextDNS revealed multiple authorities over
.brave, confirming its decentralized status. - Brave browser prompted me to use Infura, which resolved the domain to my IPFS site.
.braveis claimed by various resolvers; access requires choosing one like Infura.- Web3 ownership is still experimental and not yet mainstream.
Full article
I bought a domain name with the .brave TLD. They said it's a Web3 decentralized true ownership domain name; pay once and own it, not renting it.
I tried to add the domain name to my remote server, but letsencrypt.org certificate authority integration failed because the .brave TLD is not supported by them yet.
So, I'm not sure what I can do with that TLD. I tried to use NextDNS resolver to resolve that domain name pointing to my IPFS website, but instead, it showed a different result. That means the .brave TLD is really decentralized, and more than one company claims authority over that TLD.
When I tried the Brave browser itself, I received a message that it's my choice to use Infura servers to resolve it; then it successfully resolved and directed me to my IPFS website in the web browser.
My observation is: the .brave domain name I bought has been claimed by other domain name resolvers as well. So, to browse that website, I need to choose a specific resolver server like Infura.
Welcome to the decentralized world—actually Web3. The ownership part of Web3, I think, is still highly experimental and not mainstream.
