What brand TLD owners told us at ICANN 86 — and why August 12th matters

The Brand Registry Group (BRG) held its membership meeting at ICANN 86 in Seville with one unmistakable message: the 2026 new gTLD application window is a once-in-a-generation opportunity, and brands that haven’t started their application process yet are running out of time.

We attended the session and came away with concrete insights from brand TLD operators at Fox, Amazon, and Sky — companies that have been living inside their own namespaces for a decade. Here’s what they shared.

---

The tipping point isn’t one thing — it’s FOMO

Stuart Fuller of Mark Monitor described what’s finally moving brands off the fence: “There’s an underlying theme — the fear of missing out. We’ve waited 14 years to get here, and we don’t know when the next round will come.” More importantly, he noted that brands coming forward in 2026 are arriving with specific use cases and cross-functional buy-in across security, marketing, legal, and IT — not just a defensive IP instinct.

“How do we explain to our stakeholders that we decided not to make a decision?”

— Stuart Fuller, SVP Commercial, Mark Monitor

---

What Fox and Amazon actually use their .brand for

Cruz Gore (Fox) and Matthew Crossman (Amazon) gave candid examples of day-to-day value from their brand TLDs — including some use cases that weren’t on their radar when they first applied.

• Phishing prevention
  Fox mandates .fox links in all internal employee communications, giving InfoSec a clear, enforceable standard for what’s legitimate.
• Avoiding premium domain costs
  When a Fox business unit requested a coveted 3-letter .com at $5,000+/year, Cruz pointed them to the .fox equivalent — free, available immediately.
• Internal infrastructure and APIs
  Amazon’s engineering and security teams have embraced brand TLDs for internal services and API endpoints — a use case that emerged from stakeholder conversations, not the original plan.
• Branded URL shorteners
  Fox uses go.fox on broadcasts. Zara runs go.zara across all social media. Every shortened link is immediately verifiable as authentic — unlike bit.ly or similar third-party services.
• Authenticated email for C-suite
  Sky uses .sky email addresses for senior executives. When an email ends in .sky, recipients know it can only have come from Sky — a meaningful defense against executive impersonation.
• All new internal sites on .brand
  Fox now routes all new internal website requests through .fox by default, streamlining domain management and eliminating back-and-forth over availability.

---

What’s different about 2026 vs. 2012

In 2012, brands were working from theory. In 2026, there are years of documented use cases, established policy processes, and a clear playbook. Matthew Crossman described the current moment as a “sweet spot” — mature enough in governance and operations, but still wide open for innovation. As he put it, the value of a controlled, trusted namespace as a signal to customers and to AI agents “is only becoming increasingly relevant.”

Stuart also flagged a new cohort of applicants: fintech, MarTech, and legal tech companies that didn’t exist in 2012, built digital-first, and see a brand TLD as an obvious extension of their infrastructure strategy.

---

The AI factor: .brand TLDs as trust infrastructure

Jennifer Gore, BRG Executive Director, introduced a forward-looking framing that every brand should internalize: as AI agents increasingly navigate the web autonomously, there’s no longer always a human in the loop evaluating whether a domain is legitimate. Brand TLDs — where the authenticated brand owner controls the entire namespace — become structural trust signals in a way that open registries simply cannot replicate.

AI also accelerates the threat side: automated typosquatting, phishing domain generation, and multinational impersonation attacks are becoming faster and cheaper to launch. A brand TLD doesn’t eliminate the risk, but it fundamentally shifts the economics against attackers within your own namespace.

“Stop thinking about it being just a website. Email exchange is probably one of the best use cases in the current climate.”

— Nisha Parkash, Head of Domain Management, Sky Group

---

The “say yes and figure it out later” principle

Nisha Parkash from Sky made a point that resonated through the room: Sky took four years to fully build out .sky after receiving the TLD. The anxiety about “what do I do with it” is real — but it shouldn’t be the reason to miss the round. Once you don’t apply, you lose all ability to shape your own digital landscape. Every opportunity to use your brand online ends at whatever someone else controls.

---

Practical obstacles to watch

The session didn’t shy away from the hard parts. Three barriers came up repeatedly:

Internal buy-in takes longer than you expect. Even at Fox, with an experienced team and a clear track record, getting a single additional business unit through the decision process has taken months. The application is not a one-day form — it requires legal review, executive sign-off, and vendor selection.

Payment logistics are a real constraint. The application fee must be paid to ICANN by August 19th. Some organizations are discovering that onboarding ICANN as a new vendor in their procurement system takes 90 days — meaning they needed to start that process in May. Working backwards from the deadline, rather than forward from today, is the approach that’s resonating with brands.

Trademark and string eligibility issues need early review. Geographical terms, string similarity conflicts, and trademark status can all create complications. Getting ahead of these — ideally with guidance from an experienced application service provider — avoids last-minute surprises.

---

This post is based on the BRG membership session at ICANN 86, featuring Cruz Gore (Fox), Matthew Crossman (Amazon), Stuart Fuller (Mark Monitor), Nisha Parkash (Sky), and BRG Executive Director Jennifer Gore, moderated by Krupa Shaw (Identity Digital).