domaindetails.com
Technical Guides
10 min read

ICANN Specification 13 Explained

Understanding brand TLDs, closed generics, and registry restrictions

What is ICANN Specification 13?

ICANN Specification 13 ("Specification 13" or "Spec 13") is a provision in the Registry Agreement between ICANN and new gTLD registry operators. It was introduced as part of the 2012 New gTLD Program to define the requirements and restrictions for single-registrant brand TLDs whose label matches the applicant's trademark (e.g., .google, .bmw, .apple).

Specification 13 establishes the framework under which registry operators can restrict domain registrations to the brand owner and their authorized affiliates, typically for brand protection purposes.

Note that closed generic strings (such as .book, .shop, or .app when operated in a closed manner) were explicitly carved out of Specification 13 in the 2012 round and are governed under separate policy considerations that remain contentious in ongoing ICANN policy development.

Key Components of Specification 13

Eligible Registration Policies

Under Spec 13, a registry operator can elect to apply "Eligible Registration Policies" that restrict registrations to:

  • The registry operator itself (single registrant model)
  • Affiliates of the registry operator (subsidiaries, related companies)
  • Trademark licensees who have permission to use the brand

Reserved Names Requirement

Registry operators using Spec 13 must reserve all second-level domain names from the Top-Level Reserved Names List and other ICANN-required reservations. These names cannot be registered or activated, even by the registry operator itself.

Periodic Reporting

Registries operating under Spec 13 must provide ICANN with periodic reports demonstrating compliance with their stated registration policies. This includes:

  • Documentation of the relationships between registrants and the registry operator
  • Evidence that all registrants meet eligibility criteria
  • Verification of trademark licenses where applicable

Brand TLDs

What is a Brand TLD?

A Brand TLD (also called Brand Top-Level Domain) is a top-level domain operated exclusively by and for a specific brand or company. These TLDs typically operate under Specification 13 and restrict registrations to the brand owner and their authorized affiliates.

Examples of Brand TLDs

.google

Used exclusively by Google and its services (e.g., maps.google, docs.google)

.amazon

Amazon's brand TLD for company websites and services

.apple

Apple Inc.'s exclusive TLD for products and services

.bmw

BMW's automotive brand TLD

.microsoft

Microsoft's brand TLD for company and product sites

.nike

Nike's brand TLD for athletic products and services

Benefits of Brand TLDs

  • Complete Brand Control: No third parties can register domains
  • Enhanced Trust: Users know all domains are authentic company properties
  • Marketing Innovation: Creative marketing campaigns and memorable URLs
  • Phishing Prevention: Eliminates cybersquatting and phishing risks
  • Simplified Management: Centralized DNS and security policies
  • Brand Differentiation: Unique digital identity separate from .com competitors

Closed Generic TLDs

Understanding Closed Generics

A "closed generic" TLD is a generic term (not a brand name) that is operated in a closed or restricted manner under Specification 13. This has been one of the most controversial aspects of the New gTLD Program because generic terms traditionally represent categories or industries that should be accessible to multiple parties.

The Controversy

During the 2012 gTLD round, several companies applied for generic TLDs with the intention to operate them as closed registries. This raised concerns about:

  • Public Interest: Should one company control access to a generic industry term?
  • Competition: Does closure of generic terms limit competition and innovation?
  • Community Objections: Many applications faced community objections from industry groups
  • Governmental Advisory Committee (GAC) Advice: Multiple governments opposed closed generics

Examples and Outcomes

.amazon (Geographic Term)

Amazon.com's application for .amazon faced objections from South American countries who argued the Amazon River and region represent geographic and cultural significance. After years of dispute, ICANN ultimately approved .amazon for Amazon.com in 2019.

.book, .author, .read (Amazon)

Amazon applied for multiple book-related generic TLDs with Spec 13 restrictions, raising concerns about single-company control over generic publishing terms.

.hotel (Hotels.com)

Initially proposed as restricted, ultimately operated as an open TLD after industry feedback.

Policy Development for Future Rounds

The SubPro (Subsequent Procedures) Working Group has addressed closed generics extensively. Recommendations for future rounds include:

  • Presumption that generic terms should be operated as open TLDs accessible to all qualified applicants
  • Narrow exceptions requiring exceptional justification and public interest commitments
  • Enhanced evaluation of applications seeking closed generic operation
  • Greater community and governmental input in closed generic decisions

Public Interest Commitments (PICs)

What are PICs?

Public Interest Commitments (PICs) are voluntary commitments made by registry operators to address community concerns and protect the public interest. PICs become binding contractual obligations incorporated into the Registry Agreement with ICANN.

Types of PICs

Registration Policies

Commitments about who can register domains and under what conditions (e.g., verification requirements for .bank, .insurance)

Use Restrictions

Limitations on how domains can be used (e.g., .kids must maintain child-safe content)

Security Requirements

Enhanced security measures like DNSSEC, two-factor authentication, or encryption requirements

Content Policies

Restrictions on harmful content like malware, phishing, or illegal activities

Community Safeguards

Commitments to serve and protect specific communities (e.g., geographic, cultural, or professional)

PIC Dispute Resolution Policy (PICDRP)

ICANN established the PIC Dispute Resolution Policy to enforce PICs. If a registry operator violates their Public Interest Commitments:

  • Affected parties can file complaints with designated dispute resolution providers
  • Independent experts review evidence and determine if violations occurred
  • Remedies can include requiring the registry to comply or imposing sanctions
  • Persistent violations may result in contract termination

Examples of PICs in Practice

  • .bank and .insurance: Registrants must be verified financial institutions or insurance companies
  • .pharmacy: Only licensed pharmacies verified by regulatory authorities can register
  • .law: Registrants must be qualified legal professionals or law firms
  • .kids: All content must be appropriate for children under 13

Registry Services Evaluation Process (RSEP)

What is RSEP?

The Registry Services Evaluation Process (RSEP) is ICANN's mechanism for evaluating proposed new registry services or significant changes to existing services. Any registry operator wanting to offer services beyond those specified in their Registry Agreement must submit an RSEP request.

When RSEP is Required

Registry operators must submit RSEP requests for:

  • New registry services not previously approved
  • Material changes to registration policies (including moving to/from Spec 13)
  • Changes to IDN tables or character sets
  • Introduction of new DNS resolution services
  • Significant modifications to backend infrastructure affecting stability or security

RSEP Evaluation Criteria

ICANN evaluates proposed services based on:

  • Security and Stability: Impact on DNS security and operational stability
  • Competition: Effects on competition in domain name registration and use
  • Registrant Protection: Safeguards for domain registrants' interests
  • Technical Feasibility: Whether the service can be implemented reliably

RSEP and Specification 13

For registries operating under Spec 13, any changes to registration eligibility policies require RSEP approval:

  • Transitioning from closed to open registration
  • Expanding or restricting the list of eligible registrants
  • Modifying verification procedures for eligible registrants
  • Changing the relationship requirements between registrants and registry

RSEP Timeline

The RSEP process typically takes 30-90 days but can extend longer for complex requests:

  1. Registry submits detailed service description
  2. ICANN performs preliminary review (15 days)
  3. Public comment period if needed (30 days)
  4. Technical and security evaluation
  5. ICANN decision and approval or rejection

How Brand TLDs Differ from Open TLDs

AspectBrand TLD (Spec 13)Open TLD
Registration AvailabilityRestricted to brand and affiliatesOpen to public registrants
Registrar AccessMay bypass registrars entirelyMust use ICANN-accredited registrars
PricingInternal cost allocationMarket-based pricing
Sunrise PeriodNot requiredMandatory trademark protection period
WHOIS/RDAPLimited data publicationStandard registration data publication
Compliance ObligationsSpec 13 reporting requirementsStandard registry compliance
PurposeBrand protection and marketingRevenue generation and public service

Future of Specification 13

As ICANN prepares for the next gTLD application round, Specification 13 continues to evolve based on lessons learned:

  • Brand TLDs: Generally accepted and expected to continue with similar frameworks
  • Closed Generics: Likely to face stricter scrutiny and higher justification requirements
  • Community TLDs: Enhanced provisions for community-operated restricted TLDs
  • Transition Mechanisms: Clearer processes for moving between open and closed status
  • Public Interest: Stronger emphasis on demonstrating public benefit for restricted generics

Key Takeaways

  • Specification 13 enables registry operators to restrict registrations to specific entities
  • Brand TLDs use Spec 13 to maintain exclusive control and protect their brand identity
  • Closed generics remain controversial due to public interest and competition concerns
  • Public Interest Commitments (PICs) add binding obligations to protect users and communities
  • RSEP provides oversight for changes to registry services and registration policies