The 2012 Round
New TLDs vs classic TLDs — reading an ending the way a registrar reads one
ICANN's 2012 round turned a dozen endings into more than a thousand. Some are genuinely better names for particular work; most of the internet still resolves to the originals.
The short answer
Default to a classic ending — .com, .org, .net — for a brand meant to be typed, remembered and trusted by the broadest audience; four decades of habit is an asset no new ending can replicate yet. Reach for a new ending when it says something true about the work: .dev for a developer project, .app for software, .store for a shop, where the ending completes the name instead of decorating it.
Two practical differences decide edge cases. Availability: the name you want is far likelier to be free under a new ending. And plumbing: .app and .dev are HSTS-preloaded, so browsers refuse plain HTTP on them — a security floor built into the ending itself. Everything else on this page is the detail behind those two facts.
By the Hosting & Domains team · Reviewed 25 August 2026
1985
The classics enter the root
2012
ICANN's new gTLD round opens
1,000+
Endings delegated since
HTTPS
Enforced by .app and .dev
The classic generic endings — .com, .net, .org among them — date from 1985 and carry the internet's muscle memory. The new generation arrived after ICANN's 2012 application round, which invited registries to propose almost any string; hundreds went live from 2014 onwards, from the generic (.online, .site) to the sharply specific (.dev, .store).
A registrar's job is to strip the marketing from both camps. New endings are neither a revolution nor a scam: they are inventory, run by real registries under ICANN contract, with their own pricing tiers, their own reputations with mail filters, and — in a few cases — genuinely useful technical properties the classics lack.
What the classics still own
Recall. When a person half-remembers an address, they finish it with .com; no new ending has displaced that reflex anywhere on earth.
Reputation. Four decades of legitimate use means classic endings start neutral with every spam filter, reviewer and procurement department. Young endings start with whatever their early registrants earned them, and some earned them suspicion.
Liquidity. The aftermarket in classic names is deep and priced; a strong .com is a recoverable asset in a way most new-ending names are not yet.
What the new endings genuinely add
Availability, first and always: the dictionary is re-opened. Short, pronounceable names long gone under .com sit unregistered under .dev or .studio.
Meaning. An ending that describes the work — .app, .store, .agency — lets the whole address read as a sentence. For a product aimed at people who live online, that reads modern rather than odd.
And in two cases, hard engineering: .app and .dev sit on the HSTS preload list, so every mainstream browser refuses to load them over plain HTTP. A certificate is not optional furniture there; the ending enforces the site's transport security by construction.
The pricing shape to understand before you search
Classic endings price flat: one rate to register, one to renew, the same for every available string. New registries price in tiers — ordinary strings at ordinary rates, desirable strings designated premium at higher registration and, often, higher renewal, set by the registry rather than the registrar.
Introductory offers add a second wrinkle: the first year of a young ending is frequently promoted below its ongoing rate, so the renewal is the number that describes what the name actually costs to keep.
Neither practice is hidden, but both reward the buyer who reads the renewal line. We print it beside the registration on every result, every ending, so the comparison is made with real numbers in view.
A decision procedure that survives contact with marketing
Ask what the address must do. If it will be spoken on phones, printed on vehicles and remembered by strangers, weight recall heavily and favour a classic. If it will be clicked from search, feeds and app stores, the ending's unfamiliarity costs little.
Ask what the ending says. A .dev that describes a developer tool adds information; a novelty ending stapled to a law firm subtracts it. The test is whether the ending would survive being read aloud to your best customer.
Then ask the registrar questions: what does this string renew at, is it registry-premium, and how does mail from this ending currently fare with the big receivers. Any ending that survives all three questions is safe to build on.
Endings are registries, not fashions
Every ending, classic or new, is a business run by a registry under contract, with a published rulebook, a pricing policy and a reputation earned by its registrants. Judging one by its television adverts is how buyers end up surprised at renewal or stuck on an ending mail filters distrust.
Judge them instead like a registrar: who runs it, what it renews at, what its abuse statistics look like, and whether its rules — eligibility, HTTPS enforcement, premium tiers — help or hinder the specific thing you are building. On that reading, a handful of new endings are excellent, most are harmless, and the classics remain the default for good reason.
- Every ending searchable with renewal shown up front
- Registry-premium strings flagged before checkout
- HSTS-preloaded endings paired with SSL from the first minute
- Classic and new endings held side by side in one account
Why Hosting & Domains
Standard on every plan
One search, every generation
Classic and new endings answered together, so availability under .dev is weighed against the .com's status in a single view.
The registry's rules, translated
Premium tiers, HTTPS enforcement, eligibility quirks — the parts of an ending's rulebook that affect you, explained before you register.
Renewals without archaeology
The ongoing rate printed beside the introductory one, because the second year is the true price of a young ending.
Defensive registrations made easy
Take the classic and the descriptive ending together, point both at one site, and stop thinking about it.
Quick Start
Order placed to site online
- 1
Write the address in a sentence
Say the full address aloud in the sentence a customer would use. The ending that survives that reading is a candidate; the one that needs explaining is not.
- 2
Check the string under both generations
Search the name across classic and new endings at once, noting which results are registry-premium and what each renews at.
- 3
Register the lead, secure the echo
Build on the ending that fits the work; register the obvious alternative defensively and redirect it home.
Built In
Fitted to every plan
- The address read aloud before any ending is chosen
- Renewal and premium status checked for the exact string
- SSL live from day one on HSTS-preloaded endings
- Mail authentication published before the first campaign
- The classic sibling registered where the brand justifies it
- Every name in one account, one calendar, one card
Frequently Asked
The questions that come up most
Do new endings rank worse in search than .com?
Search engines treat new generic endings the same as classic ones — placement follows content, links and experience, not the ending. Where teams see gaps, the cause is usually a young site measured against an old one. The ending's real-world effect is on people: recall and click-through, not the algorithm.
What does HSTS preloading on .app and .dev actually mean for me?
Browsers ship with those endings on a built-in HTTPS-only list, so any .app or .dev address is refused over plain HTTP before a single byte loads. Practically: your site must have a valid certificate from the first minute, and no visitor can ever be downgraded to an insecure connection on your name. With free SSL on every plan, it costs nothing to satisfy and buys a security floor the classic endings cannot promise.
Why is the same word so much more expensive under one new ending than another?
Each new registry sets its own tiers and designates its own premium strings, so one registry may consider a word ordinary while another prices it as premium — sometimes with the premium rate applying at renewal too. Always check the exact string's renewal before registering; we surface both at search.
Are new endings riskier to hold long-term?
The endings themselves run under ICANN contracts with continuity provisions, so a registry failure would see the ending transitioned, not deleted. The realistic long-term risks are commercial — pricing changes at renewal and reputation drift from other registrants' behaviour — both of which you monitor rather than insure against. For a mission-critical brand, holding the classic sibling as well is the sensible hedge.
Should an established business move from .com to a descriptive new ending?
Rarely as a replacement; often as an addition. The .com holds your history, links and recall — keep serving on it, or 301 it carefully if the rebrand is total. Most firms get the upside by using the descriptive ending for a product, campaign or short link while the classic name remains the canonical home.
Keep reading
.xyz vs .com
The most-registered young ending examined against the default, spam folklore included.
.com vs .net
The choice inside the classic camp, for when the new endings are ruled out.
Domain Names
Search a name across the classics and the 2012 generation in one query.
Domain Prices
Registration, renewal and transfer rates for every ending, premium tiers flagged.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Pick the ending that tells the truth about the work.
Search classic and new endings together, see every renewal up front, and register the name in your own details.
View Domain Names plans