Brave can resolve Unstoppable Domains (“UD”) automatically, but only if these are enabled - Steps:
- Open Brave → go to
Settings→Privacy & Security→Security & Privacy. - Look for “Web3 / Decentralized Web” options. You need:
- “Resolve Unstoppable Domains” (sometimes under “Blockchain Domains” or “Web3 features”)
- Brave Wallet enabled (sometimes required for the UD resolver).
Without this, Brave will act like a normal browser and show “nothing to see here” or “site not found.”
Sites:
brave.brave - Brave’s official domain (shows Brave info/project).
community.brave - Community-oriented pages, sometimes hosting blogs or forums.
blog.brave - Often a decentralized version of Brave’s blog or updates.
wallet.brave - Demonstrates Brave Wallet features or tutorials on Web3 payments.
forum.brave - Some community members set up forums or discussion pages under this UD.
And https://brave.com/d/brave.brave should work?
.brave is actually a special domain extension used by the Brave browser’s decentralized web features, specifically Brave’s support for blockchain-based domains such as Unstoppable Domains or Handshake-integrated sites.
.brave domains aren’t part of the traditional DNS system, so they won’t resolve in every browser - mostly only in Brave browser or with certain crypto/blockchain-aware resolvers.
So sayeth ChatGPT.
None of those addresses worked. I saw that Brave no longer supports IPFS, is that why?
ChatGPT again:
The practical answer is:
- Yes: Brave abandoned its original integrated IPFS-browser architecture.
- No: Brave did not abandon decentralized domains/Web3 entirely.
- Instead, they pivoted from:
- “browser-native IPFS infrastructure”
- toward:
- “blockchain naming + wallet-centric Web3 integration.”
Regarding this URL:
‘https://brave.com/d/brave.brave’
That page is essentially Brave’s landing page for the .brave decentralized domain initiative. It promotes:
- Web3 identity
- decentralized hosting
- crypto addressing
- censorship-resistant websites
rather than the original browser-native IPFS browsing experience.
Re that URL address, I get:
ChatGPT again:
Brave CTO Brian Bondy explicitly wrote (at GitHub) that:
- maintaining embedded Kubo/IPFS nodes was costly
- usage was extremely low (“0.1% local node”)
- it increased attack surface
