A dot-brand is a top-level domain that matches a brand and is operated as controlled infrastructure—examples include .google and .bmw—rather than an extension sold to the public. A qualifying operator can create addresses such as product.brand, but ordinary customers normally cannot register names beneath it.
Dot-brand describes a category, not a retail ending
The placeholder .brand means “the brand name at the top level.” A company does not add the literal suffix .brand to its name. It applies for its protected string to become a TLD and, if successful, signs a registry agreement and operates that namespace. The ICANN definition describes this as using the brand name as the top-level domain instead of an ending such as .com, .org or .net.
That is a different scale of ownership. Registering brand.com gives control of one second-level name under Verisign's .com registry. Operating .brand gives the organization a delegated slice of the DNS root and responsibility for every name created beneath it.
Brand TLD vs ordinary domain
| Factor | Ordinary brand.com | Closed dot-brand |
|---|---|---|
| Position | Second-level name under .com | Top-level delegation in the DNS root |
| Acquisition | Retail registrar or aftermarket purchase | ICANN application and evaluation |
| Operator | .com registry plus chosen registrar | Brand registry operator and technical providers |
| Who can register | Anyone if the label is available | Operator, affiliates or trademark licensees under Specification 13 |
| Typical names | www.brand.com, shop.brand.com | home.brand, shop.brand, support.brand |
| Cost model | Annual retail renewal | Application, evaluation, registry infrastructure and compliance |
| Exit complexity | Transfer registrar or migrate domain | Registry-level transition or termination obligations |
What Specification 13 changes
ICANN's Specification 13 defines a qualifying .Brand TLD. In simplified terms, the string must correspond to a valid registered trademark used by the operator or an affiliate; the operator must use the mark in its ordinary business; and only the registry operator, its affiliates or trademark licensees can be registrants and control DNS records in the TLD.
That closed population creates the core trust proposition. If a brand consistently uses the namespace and explains it to customers, an address under the dot-brand can signal first-party control. The signal is contractual and operational, not magical: users still need to recognize the unfamiliar ending, applications must accept it and the organization must secure every service.
What organizations use brand TLDs for
- Short product paths: a product or campaign can sit directly before the brand ending.
- Authenticated communications: a controlled namespace can help users distinguish official properties when adoption is consistent.
- Regional or service organization: labels can represent markets, departments or support functions.
- Namespace governance: the owner sets naming policy rather than competing for labels under a public TLD.
- Long-term brand infrastructure: a portfolio can be organized around the company-controlled root.
Many brand operators still keep their established .com. Familiarity, inbound links, email habits and universal acceptance do not move automatically. A dot-brand rollout is usually an information-architecture and migration program, not a one-line redirect.
The 2026 application round
As of this page's July 16, 2026 update, ICANN's next-round application window is open. The official preparation page states that submissions opened April 30, 2026 and are scheduled to close August 12, 2026. It also states that eligible applicants are legal entities and that the round supports .Brand applications alongside general, community, geographic, reserved-name and IDN types. Check the current ICANN applicant guidance for live dates and requirements.
This is not a registrar checkout. An applicant needs governance, financial and technical planning; a registry services design; abuse handling; DNSSEC and data-service operations; evaluation materials; and the capacity to comply throughout the registry agreement. Organizations normally assemble legal, brand, security, DNS and procurement teams before deciding that the benefit exceeds the long-term responsibility.
When a dot-brand is—and is not—a fit
| Stronger case | Weaker case |
|---|---|
| Globally protected, durable brand | Early-stage name that may change |
| Many products, regions or authenticated services | One website and a small domain portfolio |
| Dedicated registry, security and compliance resources | No owner for long-term DNS governance |
| Clear customer-education and migration plan | Expectation that users will understand it automatically |
| Multi-year infrastructure strategy | Short campaign or vanity goal |
Trust, SEO and universal acceptance
A dot-brand is a generic TLD for DNS and search purposes; it does not receive an automatic ranking bonus. Its potential benefit comes from first-party control, clear naming and user recognition. A badly explained address can still lose clicks to the familiar .com, and a technically valid new TLD can still meet old validation forms that reject unfamiliar endings.
Before moving a high-traffic property, test browsers, email providers, mobile apps, payment flows, identity systems and partner allowlists. Map every old URL to one new URL and follow a controlled domain-migration process. The domain-extension migration guide covers redirects, canonicals, sitemaps and monitoring.