New Web Domains: About Domain Extensions
By Ardan Michael Blum, who has run a Palo Alto SEO agency since 2016.
By Ardan Michael Blum, who has run a Palo Alto SEO agency since 2016.
Revised October 22, 2026
An ending such as .art or .events can make a web address feel unusually apt. The words on either side of the dot can describe a publication, a profession, or a gathering without an explanation underneath. A publisher should be able to choose a name for what it communicates, rather than accept an awkward phrase merely because a more familiar ending is available.
Yet the address has a longer life than the moment in which someone chooses it. It may appear in correspondence, printed programs, saved links, and accounts that use email to restore access. The useful question is therefore broader than whether a new extension makes a better name. Under what conditions does it make an address that people can understand and its holder can continue to use?
A domain extension is a top-level domain, usually shortened to TLD. In an address ending in .events, .events is the top-level domain. A registry maintains the records for the extension; a registrar handles registrations; the registrant holds the rights to a particular registered name under the relevant agreement. Choosing an address also means choosing contractual terms and a provider responsible for administering the registration.[1]
The expanding range of endings creates room for more precise names, including names in different writing systems. This can matter to a community whose language is poorly served by an address designed around English spelling. Internationalized domain names bring that linguistic choice into the address itself, although the systems through which people use them must also support it.[2][8]
On October 7, 2026, ICANN published a snapshot of 1,615 applications in its latest program for new generic top-level domains. Those are applications to operate extensions, not 1,615 approved endings ready for customers. ICANN says the final application numbers and types will be confirmed on String Confirmation Day, scheduled for November 17. Someone choosing an address today must distinguish an existing registration opportunity from a proposed extension still going through the program.[3]
For an ordinary publisher, the most useful comparison remains a shortlist of complete names. Say each aloud, look at it in an email address, and ask prospective readers what they would expect to find there. These small exercises can expose ambiguity. They cannot establish future sales, search rankings, or how an entire audience will respond.
Consider a hypothetical organization choosing an address for an annual arts festival. A name under .events might describe its immediate purpose neatly. If the same organization expects to develop an archive, publish criticism, and offer courses, a broader name might give those activities more room. Neither choice is inherently superior; the decision turns on whether the organization wants the address to name one activity or remain useful as its work changes.
Audience familiarity also belongs in that comparison. If a reader repeatedly mishears an ending or adds .com when recalling it, the cleverness of the original combination may have little practical value for that reader. Test that possibility with the people the project hopes to reach.
Search performance is a separate question. Google's guidance says that keywords in a domain name alone have little ranking effect and that the ending generally does not matter to Google Search, apart from country targeting. That gives no basis for expecting .art or .events to receive a special ranking advantage because the word matches the site's subject. Choose the wording for its human meaning; assess search performance through the actual site's content and results.[4]
Even an understandable, available name can be unsuitable. Check the extension's eligibility and use rules, and consider possible conflicts with existing names and brands. The United States Patent and Trademark Office explicitly distinguishes domain registration from trademark rights: registering an address does not itself create those rights. Availability at checkout is therefore only one part of deciding whether a name is appropriate to use.[5]
A first-year discount is a poor basis for comparing names intended to last. ICANN explains that registrars set their prices and terms, and that promotional registration prices can be lower than later renewal charges. Ask for the exact name's registration and renewal prices, together with any transfer or restoration charges that could become relevant. A registration lasts for a term; keeping it requires renewal.[6]
Suppose one name costs $5 for its first year and $60 for each renewal, while another costs $30 initially and $30 thereafter. Over five years, the first costs $245 and the second $150. These are invented prices, counting the initial year and four renewals, with no taxes or other charges and no price changes. The point is to compare the period for which the project needs the address, while recognizing that today's renewal quote may not remain unchanged.
The word “premium” requires another question. It may describe a name offered for resale by an existing holder or one assigned special pricing by a registry. Registry premiums can carry higher recurring charges, and a resold name may retain those terms. Namecheap's explanation of the products it handles makes this distinction clear. A substantial acquisition payment does not tell the buyer what the next renewal will cost.[7]
Price is only part of continuity. Establish who holds the registration and who can recover access to the account. An organization should have an authorized route to manage its address when a contractor departs or an employee changes roles. Keep current contact and payment information, use available account protections, and assign responsibility for checking renewals. These are practical safeguards for retaining an address on which other services may depend.[1][6]
An address can be legitimate and still encounter software that rejects it. ICANN describes one simple mechanism: an application checks an email address against an incomplete list of recognized extensions and treats an unfamiliar ending as invalid. Internationalized names can encounter additional processing or display problems. The failure lies in how the software handles the name, rather than in the mere fact that the extension is unfamiliar.[8]
Universal Acceptance is the effort to make valid domain names and email addresses work correctly throughout Internet applications, regardless of their script or length. ICANN's September 2026 announcement identifies acceptance, validation, storage, processing, and display as parts of that work. Successful registration, or a successful visit to a homepage, does not demonstrate that every system handling the address is ready.[2]
Full workflow testing requires a registered, configured domain. Before announcing it or moving existing services, test the workflows that matter to the project. Use controlled accounts to check signup forms, saved customer records, confirmation messages, password resets, and replies. For an internationalized address, also check how it appears when copied, stored, and displayed in the applications the audience uses. A successful test supports a conclusion about that particular workflow; it does not certify every outside service.
This leaves a real tension. People should not have to abandon a meaningful name because software relies on outdated assumptions. A small organization nevertheless has to decide whether it can resolve the specific failures it encounters or maintain a dependable alternative contact route. Describing the problem precisely makes that decision possible. Simply declaring an extension either modern or unreliable does not.
For a new project, much of this work happens before habits form. An established site already has readers arriving through old links and correspondents using old addresses. A more expressive name must offer enough benefit to justify preserving those connections during a move. The existing address may remain the better choice even when the new wording is more attractive.
Google's migration guidance recommends mapping old page addresses to their corresponding new destinations and using permanent redirects where possible. Redirecting unrelated pages to a new homepage can leave visitors without the information they expected. Google advises retaining redirects for as long as possible, generally at least a year, and warns that search visibility can fluctuate during the move. These are migration recommendations, not a promise of unchanged rankings.[9]
Keeping those routes open takes more than an announcement. The old registration and the services providing its redirects need to remain operational. Email requires its own transition: redirecting a web page does not forward messages to an old mailbox.[10] Identify correspondence and account-recovery dependencies, maintain the mail arrangements still needed, and test the replacement before retiring the old route. The cost of changing an address includes the overlap during which both must work.
That overlap reveals something easy to overlook when comparing names. As an address acquires readers, correspondence, and references, it becomes harder to replace without inconveniencing someone. An expressive extension can be a good beginning, but its lasting value depends on the arrangements that let people return. Choosing it well includes deciding who will keep those arrangements working when the excitement of the launch has passed.
1. ICANN: The Domain Name Registration Process. Roles of registrants, registrars, and registries; registration agreements govern fees, transfers, and renewals.
2. ICANN: Universal Acceptance Expert Working Group Guidelines. September 9, 2026. Defines the handling of valid domain names and email addresses across scripts, languages, and lengths.
3. ICANN: 2026 Round Applications for New Generic Top-Level Domains. October 7, 2026. Reports the provisional primary-string snapshot of 1,615 applications and the scheduled November 17 String Confirmation Day.
4. Google Search Central: SEO Starter Guide. See the discussion of domain keywords and top-level domains under "Things we believe you should not focus on".
5. United States Patent and Trademark Office: Trademark Process. Step 1 distinguishes registering a domain from acquiring trademark rights.
6. ICANN: Domain Name Renewals and Expiration. Questions 12 through 14 explain registration terms, renewal costs, and introductory pricing.
7. Namecheap: How to Get a Premium Domain. A registrar's explanation of resale and registry-premium pricing, including possible recurring premiums. Cited for those distinctions, not its promotional valuation claims.
8. ICANN: Frequently Asked Questions About Universal Acceptance. Explains incomplete extension lists and processing or display failures. This older explanatory source is paired with the September 2026 definition in note 2.
9. Google Search Central: How to Move a Site. Guidance on mapping addresses, permanent redirects, redirect retention, and temporary changes in search visibility.
10. Namecheap: How to Set Up Default Domain and Email Redirects. Documents web-address forwarding and email forwarding as separate configurations.
For corrections, permissions, privacy requests, or accessibility assistance, use the contact form or call +1 (650) 427-9358. For details, see Legal, Privacy and Accessibility.
Disclosure: AI tools assist with research, summaries, drafting, and editorial review. Their use varies by article and stage of the writing process. Ardan Michael Blum writes, revises, and updates the content, shapes its arguments and interpretations, and makes the final editorial decisions.