discuss .agent Namespace Collision: Discussion on Investment Risk

[bullishdomainer]

Been doing due diligence on .agent and wanted to put this in front of the community.

At least three separate parties I know of are claiming the same string across incompatible systems: ".agent"

Unstoppable Domains launched .agent on December 9, 2025 as a Web3 domain on Polygon and announced intent to apply for ICANN recognition in 2026. (Globe Newswire)

Handshake has had .agent on its decentralized naming system since 2020. (Namebase)

agentdomain.xyz is preparing an ICANN application for .agent as a community TLD for AI developers. They've applied for ICANN's Applicant Support Program and published a roadmap targeting Q2 2026 submission. (agentdomain.xyz)

What worries me is that namespace collisions between UD and Handshake have already gone to court. In 2022, UD sued Gateway Registry over Handshake's .wallet, which existed on HNS before UD created their version. Gateway shut down and UD eventually dropped the suit in 2023. (Domain Name Wire)

Then, there's the ICANN change for this round too. In 2012, competing TLD applicants could resolve disputes through private auctions where losers split proceeds. That's now banned for the 2026 round. All contention goes to either Community Priority Evaluation or an ICANN auction where ICANN keeps everything. (Domain Incite)

If UD and agentdomain.xyz both apply, they enter a contention set. If agentdomain.xyz qualifies for Community Priority Evaluation and wins, UD's application fails, and domains already sold on UD's platform would remain Web3-only with no path to DNS recognition.

Meanwhile, Handshake .agent continues operating independently of either outcome.

AI/agents is the hottest sector in tech. It's hard to imagine there won't be a ton of applicants for .agent at ICANN. In the 2012 round, .app received 13 different applications (Com Laude).

Hoping to gain perspective from other investors regarding the questions I keep coming back to:

• If you buy example.agent on UD today and they lose the ICANN application, what's your exit?
• What other companies are already or are likely preparing .agent applications?
• How are people here thinking about fragmentation risk on domains that exist across multiple systems?

How concerned are you about namespace fragmentation when investing in Web3/alternative TLDs?

Thanks in advance.

 

[bullishdomainer]

Been doing due diligence on .agent and wanted to put this in front of the community.

At least three separate parties I know of are claiming the same string across incompatible systems: ".agent"

Unstoppable Domains launched .agent on December 9, 2025 as a Web3 domain on Polygon and announced intent to apply for ICANN recognition in 2026. (Globe Newswire)

Handshake has had .agent on its decentralized naming system since 2020. (Namebase)

agentdomain.xyz is preparing an ICANN application for .agent as a community TLD for AI developers. They've applied for ICANN's Applicant Support Program and published a roadmap targeting Q2 2026 submission. (agentdomain.xyz)

What worries me is that namespace collisions between UD and Handshake have already gone to court. In 2022, UD sued Gateway Registry over Handshake's .wallet, which existed on HNS before UD created their version. Gateway shut down and UD eventually dropped the suit in 2023. (Domain Name Wire)

Then, there's the ICANN change for this round too. In 2012, competing TLD applicants could resolve disputes through private auctions where losers split proceeds. That's now banned for the 2026 round. All contention goes to either Community Priority Evaluation or an ICANN auction where ICANN keeps everything. (Domain Incite)

If UD and agentdomain.xyz both apply, they enter a contention set. If agentdomain.xyz qualifies for Community Priority Evaluation and wins, UD's application fails, and domains already sold on UD's platform would remain Web3-only with no path to DNS recognition.

Meanwhile, Handshake .agent continues operating independently of either outcome.

AI/agents is the hottest sector in tech. It's hard to imagine there won't be a ton of applicants for .agent at ICANN. In the 2012 round, .app received 13 different applications (Com Laude).

Hoping to gain perspective from other investors regarding the questions I keep coming back to:

• If you buy example.agent on UD today and they lose the ICANN application, what's your exit?
• What other companies are already or are likely preparing .agent applications?
• How are people here thinking about fragmentation risk on domains that exist across multiple systems?

How concerned are you about namespace fragmentation when investing in Web3/alternative TLDs?

Thanks in advance.

Globe Newswire fox40 .com/business/press-releases/globenewswire/9599170/agent-intends-to-officially-enter-the-icann-application-process-with-unstoppable-domains-and-sentient-foundation/

Namebase namebase .io/domains/agent

agentdomainxyz agentdomain .xyz/about

Domain Name Wire domainnamewire .com/2022/07/20/update-unstoppable-domains-sues-over-handshake-wallet-domain

Domain Incite domainincite .com/30251-big-twist-as-icann-bans-new-gtld-auctions

Com Laude comlaude .com/contention-resolution-for-dot-brands

 

[biggie]

Hi

secret.agent/007. will take care of it

imo…

 

[alcy]

ai.agent is cool

 

[bullishdomainer]

Hi

secret.agent/007. will take care of it

imo…

Heard he only invests in Bonds, though.

 

[bullishdomainer]

ai.agent is cool

Very. Unless someone else has ai.agent through another provider system?

 

[alcy]

Very. Unless someone else has ai.agent through another provider system?

I know little on web3 dn
but r u saying we cant even check if its regged? to whom is probably harder I guess

 

[bmugford]

In my view the only string that matters is the ICANN approved one.

It will operate as a normal domain. It will work in normal browsers, without the need for special software or settings.

And, I can almost guarantee that ICANN will not care about these existing quasi-extensions when it comes to delegating them.

Also, just like in the past any company that wins one of these competitive extensions will likely price all the good terms at "premium" prices.

Brad