Recent Shifts in the Web3 Domain Space – Driven by ICANN's 2026 Round?
The domain name landscape has seen a whirlwind of updates and changes lately, and while I don't have hard data to back it up, my gut feeling is that...
The domain name landscape has seen a whirlwind of updates and changes lately, and while I don't have hard data to back it up, my gut feeling is that much of this momentum traces back to ICANN's upcoming 2026 new gTLD round (application window opening April 30, 2026, for about 15 weeks). This next wave of generic top-level domains (gTLDs) is creating ripple effects across both traditional DNS and blockchain-based naming systems. Let's break down some key developments in the space.
Handshake Community – Namebase Still in Limbo
In the Handshake ecosystem, Namebase (the main marketplace for buying/selling HNS names) has been stuck for quite some time. I initially thought it was just the new owners upgrading the platform after the sale from Namecheap (announced in January 2026), but it turns out there were issues leading to a pause in user activity starting February 1, 2026, for migration to the new entity and a full rebuild. The buyers haven't been publicly identified, and the platform remains in a transitional state. I'm hoping for some resolution soon and plan to do a dedicated video on the whole saga once things clarify. It's frustrating for the community, as Namebase was a key on-ramp for Handshake users.
Unstoppable Domains – Heavy Pivot Toward Traditional Web2
Unstoppable Domains has pivoted hard into traditional DNS domains since becoming an ICANN-accredited registrar. They're actively pursuing ICANN gTLD status for several of their Web3-native extensions (e.g., [.privacy](https://unstoppabledomains.com/blog/categories/announcements/article/privacy-icann) with partners like Women in Web3 Privacy, [.hub](https://www.globenewswire.com/news-release/2026/01/05/3212830/0/en/Unstoppable-Domains-and-Hub-Culture-today-announced-their-intent-to-submit-hub-for-ICANN-s-upcoming-generic-top-level-domain-gTLD-application-round.html) with Hub Culture, .robot, .twin, .agent, and more), aiming for "dual recognition" so those TLDs resolve natively in browsers while keeping onchain features like crypto payments and ownership.
Not all are going this route—some partner TLDs have chosen not to apply, leading to [refund offers](https://unstoppabledomains.com/blog/categories/announcements/article/web3-refunds) for registrations. Recent statements suggest their DNS business now dominates revenue, with Web3 development taking a relative backseat for non-ICANN strings (they label new ones as either "applying to ICANN" or "Web3-only"). This feels like a pragmatic shift toward mainstream adoption and revenue.
ENS (.eth) – Protecting the Brand While Advocating for Clarity
ENS (Ethereum Name Service) continues building the Web3 layer on top of traditional ICANN domains through integrations like .box, .art, and others. They've confirmed plans to apply for .ens as a closed ".brand" TLD in the 2026 round—not for public registrations or to replace .eth, but to protect the ENS brand, enhance security/trust, and experiment with features (e.g., wallet.ens). Earliest delegation could be around 2028, with the option to open it later if the community wants.
ENS also submitted a thoughtful public comment letter to ICANN, calling for better procedures around name collisions with existing blockchain namespaces (including Handshake/HNS and others). They want clearer rules for how pre-existing alt-systems interact with new gTLDs.
My Take – Insights from ICANN Hanoi and the Road Ahead
I attended the ICANN Hanoi meeting last year [](https://skyinclude.com/blog/icann-hanoi/), and it was truly eye-opening. The buzz was all about the 2026 round—tons of follow-ups on registering a TLD, plus new scholarship-style programs like the Applicant Support Program to lower fees for eligible applicants.
On the Handshake side, some folks floated applying for .hns, but I see it as extremely challenging. Porting existing .hns second-level domains (SLDs) over would require someone to cover ongoing ICANN fees, maintain middleware, and handle integrations. There's no clean way to keep the same decentralized hns.id/.hns experience intact under ICANN rules—it's just not compatible without major compromises.
I feel Unstoppable Domains is learning this reality (perhaps later than some of us in the pure decentralized space, or at least disclosing it later). Ultimately, I don't see a straightforward path for full bridging without significant trade-offs in decentralization, fees, or control.
What do you think? Is the 2026 ICANN round accelerating consolidation toward hybrids, or pushing pure Web3 projects further away?