How New gTLDs Are Approved by ICANN?

The Complete Inside Story of the New gTLD Approval Process
From Application to Delegation — Every Stage, Every Requirement, and Every Policy Decision Behind How ICANN Opens New Internet Namespaces

Until 2013, the internet had just 22 generic Top-Level Domains (gTLDs). You know most of them — .com, .net, .org, .edu, .gov. These few extensions handled the domain names of billions of websites for nearly three decades.

Then ICANN launched the New gTLD Program — one of the biggest expansions in internet history. Since 2013, over 1,200 new domain extensions have been added to the internet: .app, .shop, .africa, .bank, .tech, .law, .google, and hundreds more.

How does a new domain extension get created? Who decides? What do applicants have to prove? And how long does the whole thing take? The new gTLD approval process is one of the most complex, multi-layered policy procedures in internet governance — and this guide walks you through every step of it.

💡  Quick Context:  A new gTLD is a generic Top-Level Domain string that did not previously exist — applied for by businesses, governments, community groups, or brand owners through ICANN’s New gTLD Program. ICANN launched the first application round in 2012 and received 1,930 applications. Round 2, opening in 2026, represents the next wave of internet namespace expansion.

What Is a gTLD — And Why Does It Matter?

A gTLD (generic Top-Level Domain) is the string that appears to the right of the last dot in a domain name. In “example.com”, the gTLD is .com. In “store.shop”, it is .shop. In “careers.google”, it is .google.

Unlike country-code TLDs (ccTLDs) like .uk or .ng, which are assigned to specific nations, gTLDs are not geographically tied. They can be used by anyone, anywhere — though some are restricted to specific applicant types (called sponsored or restricted gTLDs).

Types of New gTLDs

• Open / Generic — available for registration by anyone (e.g., .shop, .tech, .online, .store)
• Community — reserved for a specific defined community (e.g., .catholic, .kiwi, .arab)
• Geographic — tied to a city, region, or geographic entity (e.g., .nyc, .london, .africa)
• Brand — registered exclusively by a corporation for their own use (e.g., .google, .apple, .bmw)
• IDN (Internationalized) — in non-Latin scripts such as Arabic, Chinese, Cyrillic, Devanagari

Scale of Expansion:  Before the New gTLD Program: 22 generic TLDs. After Round 1 (2012-2013): 1,930 applications received, resulting in 1,200+ new extensions delegated into the Root Zone by 2024. Round 2 (2026): expected to produce hundreds more new extensions across all categories.

ICANN’s Role in the New gTLD Approval Process

ICANN — the Internet Corporation for Assigned Names and Numbers — is the sole global authority responsible for approving new gTLDs. This responsibility flows directly from ICANN’s core mandate to coordinate the internet’s naming and numbering systems for the stability and security of the global internet.

ICANN’s role in the new gTLD approval process spans every stage — from developing the policy framework and applicant guidebook, to evaluating applications, resolving objections, and ultimately delegating the approved string into the DNS Root Zone through its IANA functions.

Specifically, ICANN:

• Develops and maintains the Applicant Guidebook — the definitive policy and procedural document governing the entire process
• Opens, manages, and closes the application window
• Coordinates the evaluation of every application across multiple evaluation panels
• Manages the Dispute Resolution and Objection processes
• Signs the Registry Agreement with approved applicants
• Delegates the approved gTLD string into the DNS Root Zone via IANA functions
• Monitors and enforces registry operator compliance through ongoing contractual oversight

The New gTLD Approval Process: Every Stage Explained

The new gTLD approval process follows a structured, multi-stage pathway defined in ICANN’s Applicant Guidebook. Here is every stage — with policy details and typical durations:

Policy Development & Applicant Guidebook   [2-5 years pre-launch] Before any applications open, ICANN’s Generic Names Supporting Organization (GNSO) develops the policy framework through a multi-year, multi-stakeholder consensus process. The resulting policies are encoded in the Applicant Guidebook (AGB) — a detailed document covering eligibility, technical requirements, evaluation criteria, objection grounds, and registry agreement terms. The AGB underwent over 20 public comment periods before Round 1 launched.

Application Window Opens   [3-4 months] ICANN announces and opens the application window — the defined period during which organizations can submit applications for new gTLD strings. For Round 1, the window was open from January 12 to April 12, 2012. Round 2 opened its application submission window in 2026. Applications include a non-refundable application fee (US$185,000 for Round 1; revised for Round 2), a detailed technical and operational plan, financial capability documentation, and a community or brand justification.

Application Reveal & Initial Evaluation   [1-6 months] After the window closes, ICANN publicly reveals all received applications. This transparency allows potential objectors and competing applicants for the same string to identify conflicts. Initial evaluation then assesses whether each application meets basic completeness and eligibility requirements. Applications that pass initial evaluation proceed to the full evaluation stages.

String Contention — Identical / Similar Strings   [Variable — months to years] When multiple applicants apply for the same or confusingly similar strings (e.g., two applicants both want .app), ICANN’s String Contention process determines resolution. Contention sets can be resolved through private auction (with proceeds going to an ICANN fund supporting internet development), negotiated agreement between applicants, or community priority evaluation when at least one applicant is a community-based organization.

Extended Evaluation Panels   [3-9 months per panel] Applications undergo evaluation by three independent expert panels: (a) Administrative & Legal evaluation — organizational eligibility, legal standing, and financial capability; (b) Technical & Operational evaluation — DNS infrastructure plan, registry system capability, DNSSEC support, abuse mitigation; (c) Community Priority evaluation — for community-based applications asserting priority over generic competitors in the same contention set.

Objection Process   [6-18 months] During evaluation, any eligible party may file a formal objection against an application on four grounds: (a) String Confusion Objection — the new string is confusingly similar to an existing TLD or string; (b) Legal Rights Objection — the string infringes existing trademarks or legal rights; (c) Limited Public Interest Objection — the string is contrary to generally accepted legal norms or morality; (d) Community Objection — a substantial portion of the community the string targets objects to the application. Objections are heard by independent dispute resolution providers (ICDR, ICC, WIPO, or AAA).

Applicant Background Screening   [1-3 months] ICANN conducts a background screening on all applicants — checking for criminal history, sanctions, or other issues that would disqualify a registry operator. This is a contractual requirement to ensure that entities operating new internet namespaces meet minimum suitability standards for managing critical internet infrastructure.

Registry Agreement Negotiation & Signing   [3-6 months] Once an application passes all evaluation stages and clears the objection process, ICANN and the applicant negotiate and execute the Registry Agreement — the binding contract that governs how the new gTLD registry must be operated. Key obligations include: DNSSEC deployment, WHOIS/RDAP data accuracy, abuse mitigation, service level agreements for DNS resolution, compliance reporting, and Registrar Accreditation Agreement alignment.

Pre-Delegation Technical Testing   [1-3 months] Before the string is delegated into the Root Zone, ICANN’s IANA team conducts Pre-Delegation Testing (PDT) — a technical verification that the applicant’s DNS infrastructure, DNSSEC configuration, and registry systems meet operational standards and are ready for live internet delegation. The applicant must pass all PDT requirements before delegation proceeds.

Root Zone Delegation   [Days — after PDT passed] The final step: ICANN’s IANA team inserts the new gTLD string into the DNS Root Zone — the master directory of the internet’s naming system. From this moment, the new gTLD is live on the internet and registrations can proceed under the terms of the Registry Agreement. The registry operator typically runs a Sunrise period (for trademark holders) and a Landrush period before General Availability opens.

New gTLD Program: Key Facts & Statistics

Fact	Detail
Round 1 application window	January 12 – April 12, 2012 (3-month window)
Round 1 applications received	1,930 applications from 60+ countries
Round 1 application fee	US$185,000 (non-refundable base fee)
Strings delegated (Round 1)	1,200+ new gTLD strings delegated into Root Zone by 2024
Most applied-for category	Generic commercial strings (.app, .shop, .cloud, .site)
Brand gTLD applications	~600 brand gTLD applications in Round 1 (e.g., .google, .bmw, .apple)
Community priority process	Required when community applicant competes with generic applicants for same string
Total objections filed (Round 1)	~350 formal objections across all four objection grounds
Typical total duration (Round 1)	3 to 8+ years from application to full registry operation
Round 2 launch	Application submission window opened 2026 — second ever gTLD expansion round
Governing policy document	ICANN Applicant Guidebook (AGB) — available at icann.org/en/system/files/files/agb
Post-delegation oversight	ICANN Contractual Compliance team monitors all registry operators continuously

Key Policies Governing the New gTLD Approval Process

The new gTLD approval process is not arbitrary — it is governed by a detailed, community-developed policy architecture. Here are the most important policy pillars:

Policy Instrument	What It Governs
GNSO New gTLD Policy	The foundational policy recommendations from the Generic Names Supporting Organization that established the New gTLD Program — a multi-year consensus development process
Applicant Guidebook (AGB)	The definitive operational rulebook: evaluation criteria, eligibility, fees, objection grounds, string contention rules, and registry agreement requirements
Registry Agreement	The binding contract between ICANN and each approved registry operator covering DNSSEC, WHOIS/RDAP, abuse mitigation, SLAs, and compliance obligations
String Contention Resolution	Defines how competing applications for the same or confusingly similar strings are resolved — through auction, agreement, or community priority evaluation
Community Priority Evaluation	Policy allowing community-based applicants (meeting defined criteria) to receive prioritized evaluation over generic commercial applicants for the same string
Sensitive String Review	Certain strings require additional review: geographic names, strings relating to regulated industries (.bank, .pharmacy), and strings with public interest implications
DNS Abuse Framework	Registry operators must implement active DNS abuse mitigation policies as a condition of their Registry Agreement — governing phishing, malware, and botnet activity
New gTLD Subsequent Procedures	The GNSO’s policy work governing Round 2 and future rounds — incorporating lessons from Round 1 and establishing improved procedures for subsequent applications

UNIQUE FEATURE:  The New gTLD Journey Timeline — From Idea to Internet

The New gTLD Journey: A Visual Timeline

Here is how the entire new gTLD approval process maps across time — from the moment an organization decides to apply to the moment their new extension appears live on the internet:

Phase	Typical Duration	What Happens
Pre-Application	6-24 months	Organization researches, builds business case, retains legal/technical advisors, prepares application documentation
Application Window	3-4 months	Application submitted with US$185,000+ fee, technical plans, financial evidence, and community or brand justification
Initial Review	1-6 months	ICANN reviews completeness; applicants notified of deficiencies; string reveal published for public objection notice
Contention Sets	3-24 months	Competing applications for same/similar strings identified; contention resolution through auction, agreement, or community priority
Evaluation	3-12 months	Independent panels evaluate legal, technical, financial, and community criteria; extended evaluation if initial concerns raised
Objections	6-18 months	Formal objection proceedings at ICDR, ICC, WIPO, or AAA; applicant must defend against objections or resolve
Background Check	1-3 months	ICANN verifies applicant organizational integrity, criminal history screening, sanctions check
Registry Agreement	3-6 months	Negotiation and execution of binding Registry Agreement with ICANN; key operational and compliance terms finalized
Pre-Delegation	1-3 months	IANA technical team verifies DNS infrastructure, DNSSEC configuration, and registry system readiness
Delegation	Days	String inserted into DNS Root Zone — new gTLD is live; Sunrise, Landrush, and General Availability phases begin
TOTAL (typical)	3 to 8+ years	End-to-end timeline from application submission to established registry operation varies widely by application complexity

Frequently Asked Questions

Q1: What is the new gTLD approval process and who controls it?

The new gTLD approval process is the multi-stage procedure through which ICANN reviews, evaluates, and either approves or rejects applications for new generic Top-Level Domain strings. ICANN is the sole global authority that controls this process, operating under policies developed by the Generic Names Supporting Organization (GNSO) through the internet community’s multi-stakeholder model. The process is governed by the Applicant Guidebook and results in a binding Registry Agreement between ICANN and the approved operator.

Q2: How much does it cost to apply for a new gTLD, and is the fee refundable?

For Round 1 (2012), the base application fee was US$185,000 and was largely non-refundable regardless of outcome. For Round 2 (2026), ICANN revised the fee structure. The fee covers the cost of independent evaluation panels, objection processing, IANA technical review, and administrative overhead. Additional costs apply for contention resolution, extended evaluation, and legal proceedings — meaning the total investment for a new gTLD can reach several hundred thousand dollars before the registry even launches.

Q3: How long does the new gTLD approval process take from application to delegation?

Based on Round 1 experience, the process took between 3 and 8 or more years from application submission to delegation into the Root Zone, with the median around 4-5 years. The variation depends on whether an application faces string contention with competing applicants, formal objections, extended evaluation panels, or complex Registry Agreement negotiations. Applications without contention or objections generally move faster. Pre-application preparation adds another 6-24 months before the window even opens.

Q4: What are the four grounds for objecting to a new gTLD application?

ICANN’s Applicant Guidebook allows formal objections on four grounds: (1) String Confusion Objection — the applied-for string is confusingly similar to an existing TLD or applied-for string; (2) Legal Rights Objection — the string infringes existing trademarks or other legal rights (filed through WIPO); (3) Limited Public Interest Objection — the string is contrary to generally accepted legal norms of morality and public order; and (4) Community Objection — a substantial portion of the community the string claims to represent formally objects to the application. Each type is heard by a designated independent dispute resolution provider.

Q5: What is ICANN’s Round 2 New gTLD Program, and how is it different from Round 1?

Round 2 is the second application round for new gTLDs, opening in 2026, following the 2012 Round 1. Key differences include an updated Applicant Guidebook incorporating lessons from Round 1’s delays and contention issues, a revised fee structure, improved contention resolution mechanisms, and new Subsequent Procedures policies developed by the GNSO to make the process faster and more efficient. Round 2 is also expected to see more IDN (internationalized domain name) applications in non-Latin scripts, reflecting the growth of multilingual internet access since 2012.

The Internet Namespace Is Open for Business.

The new gTLD approval process is complex, long, and demanding — but it is also one of the most open governance processes in the digital world. Every step is documented, every decision is published, and every policy was developed by the internet community itself through years of open consultation.

Whether you are considering a Round 2 application, advising a client on domain strategy, or simply seeking to understand how the internet’s namespace expands — the knowledge is yours to use.

Your Next Steps

• Read ICANN’s New gTLD Applicant Guidebook at icann.org/resources/pages/applicants/agb
• Explore Round 2 details and timelines at newgtlds.icann.org
• Check the public list of all delegated gTLDs at iana.org/domains/root/db
• Attend an ICANN Public Meeting to engage with the new gTLD policy community

Submit public comments on ICANN’s new gTLD consultations at icann.org/participate

Every new domain extension on the internet began with one organization going through this process. Could yours be next?

© 2026 IG Insight Blog. This article is published for educational and informational purposes.