Program Overview & History
The Internet Corporation for Assigned Names and Numbers (ICANN) New gTLD Program represents one of the most significant expansions of the Internet's domain name system since its inception. This program enables organizations, businesses, and communities to apply for and operate their own generic top-level domains (gTLDs), fundamentally transforming how we navigate and organize the digital landscape.
What is the New gTLD Program?
The New gTLD Program is ICANN's initiative to increase competition, innovation, and choice in the domain name space by introducing new generic top-level domain extensions beyond the traditional .com, .org, and .net. This program allows qualified entities to apply for virtually any string as a TLD, subject to certain restrictions and evaluation criteria.
Key Program Objectives
- Enhance competition and consumer choice in the domain marketplace
- Enable innovation in domain name services and applications
- Provide opportunities for communities and organizations to establish their digital identity
- Support internationalized domain names for global accessibility
- Strengthen the security and stability of the DNS
Historical Context
The journey to expand the domain name system began in the late 1990s, but the formal New gTLD Program was launched following years of policy development within the ICANN community. The first application round opened on January 12, 2012, marking a historic moment in Internet governance.
Types of gTLD Applications
The program accommodates various types of applications, each serving different strategic objectives:
- Generic/Open TLDs: Open for public registration (.shop, .app, .online)
- Brand TLDs: Restricted to brand owner's use (.google, .amazon, .bmw)
- Geographic TLDs: Representing cities or regions (.nyc, .london, .africa)
- Community TLDs: Serving specific communities (.bank, .pharmacy, .eco)
- IDN TLDs: Non-Latin scripts for global accessibility (中国, العرب)
2026 Application Round Timeline
The next round of the New gTLD Program is scheduled to open April 1, 2026, following extensive policy development and community input. Understanding the timeline is crucial for proper preparation and strategic planning.
⚠️ Timeline Notice: These dates are based on current ICANN projections and are subject to change. We recommend preparing for the earliest possible dates while monitoring official ICANN announcements for updates.
Now through November 19, 2025 - Applicant Support Program
Application period open for qualified applicants from developing economies to receive financial assistance and support services.
December 2025 - Applicant Guidebook Release
Final Applicant Guidebook expected to be published, containing all requirements, procedures, and evaluation criteria for the 2026 round.
Q4 2025 - TAS Beta Testing Expected
Beta testing of the new TLD Application System (TAS) platform is anticipated in the second half of 2025, allowing early familiarization with the system before the April 2026 launch.
April 1 - June 30, 2026 - Application Window
Three-month application submission period for new gTLD proposals. All applications must be submitted through the TLD Application System (TAS).
August 2026 - Q1 2027 - Initial Evaluation
Comprehensive evaluation of all applications for technical, operational, and financial capability. Includes public comment period (July-November 2026).
Mid-2027 to Early 2028 - Contracting & Delegation
String contention resolution (mid-2027), ICANN auctions if needed (late 2027), followed by registry agreement execution and root zone delegation (early 2028).
Critical Preparation Milestones
To ensure readiness for the April 1, 2026 application window, prospective applicants should:
- Now: Complete feasibility studies and business planning
- Now: Secure funding commitments and technical partnerships
- Now - November 2025: Finalize application strategy and assemble response team
- October - November 2025: Participate in public comment on draft AGB (if available)
- December 2025: Review final Applicant Guidebook when released
- January - March 2026: Complete mock applications and gather documentation
- April 1 - June 30, 2026: Submit application during 3-month window
Eligibility & Requirements
Success in the New gTLD Program requires meeting stringent eligibility criteria and demonstrating comprehensive capabilities across technical, operational, and financial dimensions. Understanding these requirements is essential for any prospective applicant.
Eligibility Criteria
Any established corporation, organization, or institution from anywhere in the world can apply for a new gTLD. However, applicants must meet specific criteria:
- Must be a legally established entity (corporations, organizations, institutions)
- Cannot be an individual or sole proprietorship
- Must demonstrate technical and operational capability
- Must prove financial capability to operate a registry
- Must pass background screening checks
- Cannot be on any sanctions or prohibited lists
Technical Requirements
Core Technical Capabilities
- DNS Infrastructure: Robust, geographically distributed nameserver infrastructure
- Registry System: Shared Registry System (SRS) supporting EPP protocol
- DNSSEC Support: Full implementation of DNS Security Extensions
- IPv6 Compliance: Complete IPv6 support across all systems
- Data Escrow: Daily deposits with approved escrow providers
- RDAP Implementation: Registration Data Access Protocol services
- Zone File Access: Centralized Zone Data Service participation
Financial Requirements
Applicants must demonstrate sufficient financial resources to establish and operate a registry for at least three years:
- Application Fee: $227,000 USD (subject to change for 2026 round)
- Financial Statements: Audited financials for the most recent fiscal year
- Financial Projections: Detailed three-year budget and cash flow projections
- Funding Evidence: Proof of available funds or committed funding sources
- Continuing Operations Instrument: Letter of credit or bond to ensure registry continuity
- Registry Fixed Fees: $25,000 annual fee to ICANN plus transaction fees
Operational Requirements
Successful registry operation demands comprehensive operational capabilities:
- 24/7 Operations: Round-the-clock monitoring and support
- Customer Support: Multi-channel support for registrars and end-users
- Abuse Mitigation: Comprehensive policies and procedures for handling abuse
- Rights Protection: Implementation of mandatory rights protection mechanisms
- Registrar Management: Systems and processes for registrar accreditation and management
- Compliance Monitoring: Ongoing monitoring and reporting to ensure policy compliance
Application Process
The application process for a new gTLD is comprehensive and requires careful preparation. Understanding each phase helps ensure a complete and competitive application.
Pre-Application Phase
Before the application window opens, prospective applicants should complete extensive preparation:
- String Selection: Choose your desired TLD string and alternatives
- Business Planning: Develop comprehensive business and marketing plans
- Technical Planning: Select registry service providers and technical architecture
- Legal Review: Conduct trademark searches and legal clearances
- Team Assembly: Build your application team with necessary expertise
- Documentation: Gather all required supporting documentation
Application Submission
The application is submitted through ICANN's TLD Application System (TAS) and includes:
Application Components
- Applicant Information: Legal entity details, contact information, background
- String Information: Applied-for string, IDN tables if applicable
- Technical Plan: Detailed technical and operational capabilities
- Financial Information: Financial statements, projections, funding evidence
- Services Description: Registry services to be offered
- Community Designation: If applying as a community TLD
- Geographic Names: If the string represents a geographic term
- Protection Mechanisms: Plans for rights protection and abuse mitigation
Application Questions
The application contains approximately 50 questions covering:
- General business information and applicant background
- Technical and operational capability
- Financial capability and sustainability
- Registry services and policies
- Rights protection mechanisms
- String contention procedures preferences
- Community status and support (if applicable)
Evaluation Procedures
All applications undergo rigorous evaluation to ensure applicants meet the technical, operational, and financial requirements to operate a registry responsibly.
Initial Evaluation
The Initial Evaluation phase consists of two primary reviews:
String Review
- DNS Stability: Ensures the string won't cause technical instability
- String Similarity: Checks for visual similarity with existing TLDs
- Geographic Names: Verifies compliance with geographic name requirements
- Reserved Names: Confirms string isn't on prohibited lists
Applicant Review
- Technical Evaluation: Assessment of technical infrastructure and capabilities
- Operational Evaluation: Review of operational plans and procedures
- Financial Evaluation: Analysis of financial capacity and projections
- Background Screening: Criminal and financial background checks
Evaluation Scoring
Applications are scored on various criteria with passing thresholds:
- Technical/Operational questions are scored pass/fail
- Financial questions are scored pass/fail
- Optional points available for community priority
- All mandatory questions must pass for application approval
Extended Evaluation
Applications may enter Extended Evaluation if they:
- Fail to pass Initial Evaluation but can remediate issues
- Require additional technical review
- Need registry services evaluation
- Receive GAC Early Warning or Advice
Objection & Dispute Resolution
Four grounds for formal objection exist:
- String Confusion: Similar to existing TLD or another application
- Legal Rights: Infringes existing legal rights
- Limited Public Interest: Contrary to generally accepted legal norms
- Community Objection: Substantial opposition from targeted community
Investment & Costs
Operating a new gTLD requires significant financial investment beyond the initial application fee. Understanding the full cost structure is essential for business planning.
Application Phase Costs
Setup & Launch Costs
- Registry Infrastructure: $100,000 - $500,000
- Technical Integration: $75,000 - $200,000
- Pre-Delegation Testing: $25,000 - $50,000
- Marketing & Launch: $150,000 - $1,000,000+
- Registrar Onboarding: $50,000 - $150,000
- Sunrise & Claims Services: $30,000 - $60,000
Ongoing Operational Costs
Annual Operating Expenses
- ICANN Fees: $25,000 fixed + $0.25 per domain
- Registry Operations: $200,000 - $1,000,000
- Technical Infrastructure: $100,000 - $500,000
- Customer Support: $100,000 - $300,000
- Marketing & Promotion: $200,000 - $2,000,000+
- Compliance & Legal: $50,000 - $200,000
- Data Escrow: $15,000 - $30,000
- EBERO Coverage: $50,000 - $100,000
Revenue Projections
Revenue potential varies significantly based on TLD type and market strategy:
- Generic TLDs: 10,000 - 1,000,000+ registrations
- Brand TLDs: Internal use, no direct revenue
- Community TLDs: 5,000 - 100,000 registrations
- Geographic TLDs: 10,000 - 500,000 registrations
Wholesale pricing typically ranges from $5 - $30 per domain per year for standard registrations, with premium domains commanding higher prices.
Applicant Support Program
ICANN's Applicant Support Program (ASP) provides financial and non-financial assistance to eligible applicants from developing economies, helping to ensure global participation in the New gTLD Program.
Program Benefits
Financial Support
- 75-85% reduction in application fees ($170,250 - $192,950 discount)
- Reduced registry fixed fees during initial years
- Auction bid credits for string contention resolution
- Payment plan options for remaining fees
Non-Financial Support
- Pro Bono Assistance: Access to volunteer experts and consultants
- Application Guidance: Help with application preparation and documentation
- Technical Support: Assistance with technical requirements and planning
- Training & Resources: Educational materials and workshops
- Mentorship: Pairing with experienced registry operators
Eligibility Criteria
To qualify for the Applicant Support Program, applicants must meet specific criteria:
- Be from a developing economy (based on UN classifications)
- Demonstrate financial need through detailed documentation
- Show public interest benefit of the proposed TLD
- Meet all standard application requirements
- Not be applying for a brand TLD
- Submit ASP application during designated window
Application Timeline
The ASP application window opened on November 19, 2024, and runs for 12 months through November 19, 2025. This advance window allows successful ASP applicants time to prepare for the main application round in 2026.
Contention Resolution
When multiple qualified applicants apply for the same or confusingly similar strings, they enter a contention set that must be resolved before any can proceed to delegation.
Types of Contention
- Identical Strings: Multiple applications for exactly the same string
- Similar Strings: Applications deemed confusingly similar by evaluators
- IDN Variants: Different scripts representing the same meaning
Resolution Methods
Community Priority Evaluation
Community-based applicants can request priority evaluation. If they score 14+ points out of 16, they prevail over standard applicants.
Private Resolution
Applicants can negotiate privately to resolve contention through:
- Business combinations or joint ventures
- Financial settlements
- Withdrawal of applications
ICANN Auction of Last Resort
If private resolution fails, ICANN conducts an ascending clock auction where the highest bidder wins the right to the string.
Auction Proceeds
The 2012 round generated over $230 million in auction proceeds, which ICANN is using for:
- Internet infrastructure development
- Security and stability initiatives
- Capacity building in underserved regions
- Research and innovation grants
Pre-Delegation & Launch
After successfully passing evaluation and resolving any contention, applicants must complete several steps before their TLD is delegated into the root zone.
Registry Agreement Execution
Successful applicants must execute the Registry Agreement with ICANN, which includes:
- Consensus policy compliance obligations
- Technical and operational requirements
- Fee structure and payment terms
- Reporting and audit requirements
- Term length and renewal conditions
Pre-Delegation Testing
All new gTLDs must pass comprehensive technical testing:
- DNS Infrastructure: Nameserver configuration and performance
- DNSSEC Implementation: Proper signing and key management
- EPP Functionality: Registry-registrar protocol testing
- RDAP Services: Registration data access protocol
- Data Escrow: Successful deposit verification
- IDN Tables: If applicable, proper implementation
Launch Phases
Sunrise Period (Minimum 30 days)
Trademark holders can register domains matching their marks before general availability.
Trademark Claims (Minimum 90 days)
Notifications to potential registrants about existing trademark rights.
Limited Registration Period (Optional)
Qualified launch program for controlled initial distribution.
General Availability
Open registration for all eligible registrants on first-come, first-served basis.
Ongoing Obligations
Operating a gTLD registry involves continuous obligations to maintain compliance, security, and service quality.
Compliance Requirements
- Consensus Policies: Implement all ICANN consensus policies
- Monthly Reporting: Submit transaction reports and registry activity
- Financial Reporting: Annual financial statements and fee payments
- Audit Compliance: Participate in contractual compliance audits
- SLA Maintenance: Meet all Service Level Agreement requirements
Technical Obligations
Service Level Requirements
- DNS service availability: 100% (0 minutes downtime)
- DNS name server availability: ≥ 99% monthly
- RDAP availability: ≥ 99% monthly
- EPP service availability: ≥ 99% monthly
- DNS update time: ≤ 60 minutes
- EPP command RTT: ≤ 4000ms
Security Requirements
- Abuse Mitigation: Maintain procedures for addressing malicious conduct
- Security Audits: Regular security assessments and penetration testing
- Incident Response: 24/7 emergency response capabilities
- DNSSEC Operations: Maintain signing and key management
- Data Protection: Implement appropriate data security measures
Business Continuity
- Registry Continuity: Maintain 3-5 year operating funds
- Data Escrow: Daily deposits to approved escrow agent
- EBERO Designation: Emergency Backend Registry Operator coverage
- Transition Planning: Procedures for orderly transition if needed