New gTLDs explained: what they are and which ones matter

A clear guide to new generic top-level domains: how the ICANN program works, which extensions have real adoption, and how to evaluate one before registering.

A new gTLD is a generic top-level domain created under the ICANN program launched in 2012, which opened domain extension creation beyond the original .com, .net, and .org. ICANN received nearly 2,000 applications and has delegated over 1,200 new extensions since 2013. Some have become genuine alternatives with millions of registrations. Many others have almost no adoption at all.

This guide covers how the program works, which extensions have taken off, which carry real risk, and how to evaluate a new gTLD before registering one.

What is a new gTLD? The ICANN program explained

Before 2012, the global domain namespace was controlled by a small set of generic extensions (the "legacy gTLDs": .com, .net, .org, .info, .biz, .name, .pro) and the sTLDs (.edu, .gov, .mil). Country-code TLDs covered national markets.

ICANN's New gTLD Program changed this. It allowed companies, governments, and organizations to apply to operate entirely new extensions. Applications cost $185,000 each, which explains why most successful registries are either major tech companies or domain industry operators.

The stated goals: break the monopoly of .com, create space for geographic extensions, industry verticals, and brand-specific extensions.

Difference between legacy gTLDs and new gTLDs

Legacy gTLDs have been running since 1985 (the original "Big Six" were .com, .edu, .gov, .mil, .net, .org). They have decades of user recognition and registrar infrastructure. New gTLDs were first delegated in 2013, so the oldest among them have about 12 years of history.

The practical difference: .com has near-universal recognition. A new gTLD, even a successful one like .app, is only recognized in specific communities.

How an extension is created and delegated

The applicant submits a proposal to ICANN, goes through a community objection period, then signs a registry agreement and operates the TLD under ICANN's oversight. The registry sets registration policies (who can register, at what price) and maintains the authoritative nameservers. Registrars like GoDaddy or Namecheap then sell registrations to end users.

New gTLDs that have genuinely taken off

Most of the 1,200+ new gTLDs have fewer than 100,000 active registrations. A handful have real scale and ecosystem recognition.

Extension	Registry	Average price/year	Typical use	Notable feature
.app	Google Registry	$14-20	Web/mobile apps	HTTPS required
.dev	Google Registry	$12-18	Developer tools	HTTPS required
.shop	GMO Registry	$25-35	E-commerce	High adoption in Asia/EU
.store	Radix	$35-50	Retail	Large volume
.online	Radix	$20-40	General business	Very high total registrations
.site	Radix	$20-35	General	High volume
.ai	Government of Anguilla	$70-100	AI/tech	ccTLD used as gTLD
.co	.CO Internet	$25-35	General startup	ccTLD used as gTLD
.io	Internet Computer Bureau	$40-60	Tech startup	ccTLD, geopolitical risk
.blog	Automattic	$25-40	Publishing	Legitimate niche

Note on .ai, .co, and .io: technically, these are country-code TLDs (Anguilla, Colombia, and the British Indian Ocean Territory respectively), not new gTLDs. But they are used globally as generic extensions and their registries operate as commercial registries without geographic restrictions. See /blog/country-code-tld-guide for the full picture.

Extensions with special security policies (.app and .dev)

Google Registry added .app and .dev to the HSTS preload list. This means browsers enforce HTTPS for every domain under these extensions before any connection is made. There is no option to serve HTTP content. For security-conscious users, this is a meaningful signal. For developers building tools, it removes one step from setup.

New gTLDs worth avoiding (or approaching carefully)

Volume of registrations doesn't correlate cleanly with quality. Some high-volume extensions are filled with spam and parked domains, which makes them look established while actually degrading user trust.

Extensions to approach carefully:

Ultra-niche verticals like .lawyer, .dentist, or .accountant work for some professionals but carry no recognition outside their sector and often have very few active legitimate sites.
Extensions with unstable registry operators. Several registries have changed hands or shut down. .ceo changed operators multiple times. .feedback was acquired and effectively abandoned. When a registry operator exits, ICANN has a continuity plan, but transitions can cause disruptions.

Registry risk is real. Before registering under a lesser-known new gTLD, check who operates the registry and whether they have a track record. A registry that collapses can leave domains in limbo for months. Domain Sentinel monitors RDAP data across all delegated TLDs, including new gTLDs, so you can track any stability issues with domains you already own.

SEO impact of new gTLDs

Google's public position is clear: new gTLDs receive no special treatment, positive or negative, compared to .com. A well-built site on .shop will outrank a poorly built site on .com.

The nuances that matter in practice:

First, ccTLDs signal geography. A .fr tells Google the content targets France. New gTLDs send no geographic signal, which is neutral for international targeting but means you lose the local SEO boost that a ccTLD provides.

Second, user trust is a separate question from algorithmic ranking. If users see .xyz in a checkout flow and hesitate, your conversion rate suffers regardless of where Google ranks you.

Third, .app and .dev carry a security signal via mandatory HTTPS. That doesn't improve rankings, but it removes a potential trust barrier.

Recommendation: choose a new gTLD for memorability or availability reasons, not for SEO gain. The SEO difference between extensions is negligible compared to content quality, backlink profile, and site speed.

How to evaluate a new gTLD before registering

Who operates the registry? Look up the registry on IANA's root zone database. Is it a company with an established track record, or a small operator with no public history? Prefer registries backed by known entities (Google, Donuts/Identity Digital, Radix, GMO).
What is the renewal price? Registration prices are sometimes promotional. The renewal price is what you'll pay every year. For premium names under new gTLDs, the renewal can be $200-500/year. Check explicitly.
Are there use restrictions? Some extensions require that registrants belong to a specific industry or meet verification criteria. .bank requires FDIC membership verification. .health has content restrictions. Know what you're agreeing to.
Has the extension reached sufficient adoption to be recognized? If you're registering mycompany.ninja, consider whether your target customers will recognize .ninja as a legitimate domain or hesitate.
Can you also secure the .com equivalent? If your brand is new, registering both is strong practice. If the .com is taken and expensive, monitor it. Domain Sentinel lets you watch the .com and notifies you if it becomes available, so you can add it to your portfolio when the time comes.

The bottom line

New gTLDs are legitimate options for specific use cases. .dev and .app are real choices for developer tools. .shop and .store work in e-commerce contexts where customers are comfortable with non-.com addresses. .ai has established itself in the AI startup space.

They are not replacements for .com when you're building for a general audience that hasn't been trained to trust non-standard extensions. For the full decision framework on choosing between TLD options, see /blog/how-to-choose-tld.

Whatever extension you choose, monitor your brand on the .com equivalent and on the primary ccTLD for your market. Registering one extension leaves the others open.