When ICANN delegated the first brand TLDs in 2013 and 2014, the operators were pioneers navigating genuinely new territory. A decade later, brand TLDs are established infrastructure, with a substantial body of operational experience, technical documentation, and strategic precedent. Organisations considering a brand TLD application in the 2026 round are not making a bet on an unproven concept: they are choosing whether to invest in a class of digital infrastructure whose use cases, operational requirements, and strategic value are well understood.
The use case landscape has evolved considerably from the early days of brand TLD deployment. Initial deployments were heavily focused on defensive registration, securing the namespace to prevent third-party registration and squatting. Over time, operational practice has matured into more active and more diverse use patterns, as operators have developed internal expertise, registry infrastructure, and strategic clarity about how brand TLDs fit into their digital operations.
The most strategically significant use case for brand TLDs is authentication. A brand TLD creates a controlled namespace that only the brand operator can populate: no third party can register a domain under .brandname. This structural exclusivity is the foundation of an authentication strategy: consumers, business partners, and regulators who know that a brand operates exclusively on its brand TLD can use the TLD as a verification signal. A communication or website from brandname.com cannot be verified by its domain structure alone; a communication from secure.brandname, where .brandname is a controlled namespace, carries structural authentication value that shared TLDs cannot provide.
Anti-phishing and anti-fraud applications follow from this authentication property. Financial institutions, healthcare organisations, and other high-target-value entities are frequent targets of domain-based phishing campaigns. The brand TLD provides a structural countermeasure that complements, rather than replaces, technical security measures: it creates a verifiable signal that can be used in consumer education campaigns, regulatory communications, and technical authentication protocols.
Beyond consumer-facing applications, brand TLDs have found significant adoption as internal infrastructure. Email systems, intranet environments, back-office applications, and machine-to-machine communications can all be run on the brand TLD's namespace, providing a controlled, brand-consistent infrastructure that does not depend on shared TLD registration and the associated risks of third-party interference, expiry, or policy changes.
For multinational organisations, the brand TLD provides a namespace that is consistent across all jurisdictions without the country-code TLD fragmentation that otherwise requires managing registrations across dozens of national registries. A single brand TLD namespace can serve all markets, with second-level domains structured to reflect market, function, or product lines as required by the organisation's operational architecture.
A brand TLD is a top-level domain (the rightmost part of a domain name) that is operated by the brand owner as a closed registry. It appears to the right of the final dot: .brandname. A premium domain registration is a second-level domain (a registration under an existing TLD such as .com, .brand.com, or .co.uk) that the brand owner purchases or registers. The structural difference is fundamental: a brand TLD owner controls the entire namespace under the TLD and can create unlimited second-level domains, while a premium domain owner has a single domain name that can be subdomained but cannot create new top-level structures.
Yes. While brand TLDs are closed registries (meaning the operator controls who can register domains under the TLD) the operator can grant delegated registrations to authorised partners, distributors, dealers, or franchisees. This enables a controlled partner namespace: authorised partner domains can be provisioned under the brand TLD, extending the authentication and trust infrastructure to the distribution network while maintaining the brand operator's control over who participates in the namespace.
ICANN's Registry Agreement includes change of control provisions that require ICANN approval for material changes in ownership or control of a gTLD registry operator. In an M&A transaction, the acquirer must obtain ICANN's consent to the transfer of the registry agreement to the acquiring entity. ICANN evaluates the proposed transferee against the same criteria applied to original applicants: financial capability, technical competence, and operational suitability. The change of control process adds a regulatory dimension to M&A due diligence for transactions involving brand TLD operators.
%402x.svg){kind=icon}
%402x.svg){kind=small}
%402x.svg){kind=icon}
