Dynadot

new gtlds Should We Rename New gTLD's?

Spaceship Spaceship
In 2012, ICANN started the monumental process of releasing the new class of domain extensions. This represented the largest introduction of new extensions in over two decades. As such, over 1,900 applications were submitted to ICANN, with 751 of those applications being contested. Large corporations such as Google and Amazon submitted 101 and 76 applications respectively.

By November 2013, following a lottery and a public comment period, extensions such as .BIKE, .GURU and .CLOTHING entered the sunrise period.

Since then, according to ICANN, 1,230 domain extensions have been introduced into the Internet, with over 26.2 million domains registered. Based on statistics from nTLDStats.com, the most popular extensions to date in terms of overall registrations are .TOP, .XYZ and .LOAN, followed by .CLUB and .SITE.

Google has released the popular .APP and .DEV extensions, which have amassed over half a million domain registrations between them.

Throughout all of this, the most popular term to describe these new extensions is “new gTLD”. The “gTLD” comes from the acronym for “Generic Top-Level Domains”. ICANN describes these extensions as “New gTLD’s” repeatedly on their website, and it has become a widely used term amongst investors, often shortened to “nTLD” (new top-level domain).

The idea of these new gTLD’s came into fruition in 2012, meaning that the concept is seven years old this year. Can something that is seven years old still be described as “new”? In 2012, a Bitcoin was worth $13, the iPhone 5 was new to the market, and the first of the Avengers movies was released.

Whilst there are new extensions being released, the concept of a "new gTLD" is firmly embedded into the minds of most investors, and end users, particularly in emerging tech sectors, are familiar with these extensions, even if they do often opt to operate on other ccTLD's or gTLD's. Could the fact that these are "new" extensions even be putting potential end-users off using them?

I thought it'd be interesting to see what a host of popular registrars use to describe "new gTLD's". GoDaddy has a whole section dedicated to "New Domain Extensions", NameCheap uses the term "New TLD's", and Uniregistry uses "New Domain Extensions".

Although this may be a pointless endeavor, I would like to pose the question: should we rename "new gTLD's"? I have heard the term "vanity TLD's" being used before, but I don't think this accurately describes the new format.

My own personal preference would be to call the flock of new extensions "expansion TLD's (eTLD's)", as these extensions expand on the original group of .COM, .NET and .ORG extensions. This is by no means an original phrase, as I have seen it mentioned a couple of times in historical blog posts. However, I think it fits the bill well.

Could the rebranding of "new gTLD's" to something that gives these extensions a sense of history, establishment, and permanence attract more potential users to these extensions?
 
14
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
Alt Extensions, sounds good imo
 
2
•••
"New Extensions" -- is good; Even end user understands the term.
 
Last edited:
1
•••
A five year old computer may work but is ready to be replaced. A five year old car will likely still drive but maintenance costs will start increasing.
My car is 17 years old. Still looks pretty cool and drives fine. It cost me outright what most people pay every month for theirs. No premium renewals there :stig:

I'm reading this thread on my thirteen year old macbook, but true this is ready to be replaced :xf.smile:
 
Last edited:
0
•••
""New domain extension" suits me fine as I have it in dot com.
 
0
•••
Let us not forget what a domain is supposed to be used for - creating a website.
Thanks for the obvious. The fact is that most "new" extension owners also own the .com at some point because they cant really run it on just example.random and get type in traffic.
 
0
•••
As always an interesting and informational read @James Iles !

Personally, I don't actually feel very strongly either way. Yes most are not new anymore (although In Canada we have a major political party starting with the word new that has been around since 1961!).

Why I don't feel strongly is that while a category is useful to domainers, say doing stats using tools like NameBio or listings like DNJournal, the end user simply views any as a domain. Yes, there are a whole host of characteristics, including how many others use that TLD, but lumping dissimilar domains into one category name does not provide useful information.

The "new" gTLDs are really a combination of different types of domains. The geo oriented ones (like .nyc) are very different from the niche ones (like .dog or ..app) which in turn are different from the broadly generic ones (like .site or .xyz or .online).

Many view (even confuse) what are formally considered legacy alternative extensions (like .name or .pro or .mobi) with new gTLDs even though they are not by ICANN terminology.

I think it is important to designate extensions that are distinctly different such as the brand ones that are restricted to the owner of the TLD and the restricted ones (like .coop, a legacy extension that can only be used by a recognized cooperative venture).

Bob
 
0
•••
I wouldn't change it. New extensions probably won't stop popping up.
 
0
•••
Cant call them new forever..

Heres my top two votes

BGTLDs
Better Generic Top Level Domains

RGTLDs
Relevent Generic Top Level Domains



 
0
•••
I think this has been discussed in other threads too, always fun to circle back to. Having "new" in defining the new extensions isn't going away anytime soon, even when they get old. Eventually they'll just be normal domain names to the public, but likely to investors still defined by "new", just as a point of separation because we need that.

For example, Regular Joe doesn't know his ccTLD is a ccTLD, he just knows its his domain name or the name of his website.

There was some traction on another name for the gTLDs, a la "Next Gen" names or "Next Generation" names.

Personally I think we just go with "G Spot", what do you think? :laugh: Because that's what they hit, with a good combo.
 
1
•••
They should be renamed to Custom Domain Extensions.
 
0
•••
I had many negotiations with endusers (my inbound buyers) - and never heard NewTLD/nTLD/New* from them...
So looks that only domainers and some registrars use those terms...
 
Last edited:
0
•••
I had many negotiations with endusers (my inbound buyers) - and never heard NewTLD/nTLD/New* from them...
So looks that only domainers and some registrars use those terms...
Well from your other posts you have experience selling non dot com so your end user doesn't know much like most which is how we make money they don't need to know just their appeal.
 
Last edited:
0
•••
Personally I group them into three categories:

1. .com
2. Location TLD's (.fr, .nyc etc.)
3. Descriptor TLD's (everything else).
 
Last edited:
1
•••
Personally I group them into three categories:

1. .com
2. Location TLD's (.fr, .nyc etc.)
3. Alt/NonCom TLD's (everything else).
..
Ditto.
 
0
•••
New gTLDs are called New gTLDs. Enough said.

This is the main way the business can comprehend what we are discussing. Every other individuals just calls everything "spaces" or a couple of individuals call them "new areas" or even less call them "new augmentations".

No one outside the business realizes that gtlds are Generic Top-Level Domains. I am certain there are domainers that don't have the foggiest idea about that. It is as of now befuddling that a few people call "New gTLDs" just "gTLDs" and in "gTLDs" they do exclude .com, .net and .organization that were the ORIGINAL gTLDs!

BTW we call all the nation augmentations ccTLDs when no one in any of these nations know or care what ccTLDs are. This is to make sure we can impart simpler and quicker.

We didn't call .data and .business New gTLDs in light of the fact that they were only several expansions. New gTLDs are over a thousand and a couple of thousand more will before long accompany the following ICANN round.

Would you like to take "New" out of "New gTLDs"? Would you like to call them gTLDs? So how are we going to call .com and .organization?

Is it accurate to say that we are going to call all expansions gTLDs? Or then again would we say we are going to call New gTLDs, gTLDs and call .com, .net and .organization heritage gTLDs so we can recognize them?

They are called New gTLDs and that is the means by which we are going to call them. On the off chance that we change their name after 7+ years nobody in the business will ever comprehend what we are discussing.

ICANN call them New gTLDs. Is it accurate to say that we are going to speaking and expounding on New gTLDs with some other name while the main association calls them New gTLDs?

Enough with this. This is just filled by the New gTLD vaults that need the new good and gone so they look set up. We have progressively genuine things to talk about.
 
0
•••
I first thought that we should now say "gTLDs". I keep using ccTLDs for "country codes" and use the term "legacy TLDs" for ".com" and his close friends.

The thing is that the ICANN plans more annual rounds of new gTLDs so to me...I guess that I will keep using the term #newgtlds
 
0
•••
..
When gtlds arent new any longer, whats the problem with calling them 'gtlds'(!), instead of 'newgtlds'?
 
Last edited:
0
•••
..
When gtlds arent new any longer, whats the problem with calling them 'gtlds'(!), instead of 'newgtlds'?
gtlds stands for general top level domains, so it includes also .com, .net and .org for example - so newgtlds is used to differentiate that :)
 
0
•••
If it's any consolation, New Wave Music or British New Wave from the 80s is still "new", 30+ years later.

New gTLDs will still don their "new" cap years from now, because it defines a style during a time period rather than a factor that changes its age descriptor as time passes.

The Second gTLD Invasion could also work, I suppose.
 
0
•••
  • The sidebar remains visible by scrolling at a speed relative to the page’s height.
Back