{"id":1340,"date":"2026-10-06T09:00:00","date_gmt":"2026-10-06T09:00:00","guid":{"rendered":"https:\/\/allcloudhost.net\/blogs\/?p=1340"},"modified":"2026-10-08T10:28:56","modified_gmt":"2026-10-08T10:28:56","slug":"icann-new-gtld-reveal-day-2026-what-it-means","status":"publish","type":"post","link":"https:\/\/allcloudhost.net\/blogs\/icann-new-gtld-reveal-day-2026-what-it-means\/","title":{"rendered":"New gTLD Reveal Day Is Coming. It Won&#8217;t Get You a Domain."},"content":{"rendered":"<p>At 18:00 UTC on October 7, ICANN will publicly disclose all 1,616 applications submitted for new top-level domains in its 2026 expansion round, along with every applicant&#8217;s identity, proposed string, and any known contention sets where multiple applicants want the same extension. It&#8217;s being called Reveal Day, and per <a href=\"https:\/\/domainnamewire.com\/2026\/09\/30\/new-top-level-domain-reveal-day-set-for-october-8\/\" target=\"_blank\" rel=\"noopener\">Domain Name Wire<\/a>, ICANN will disclose all 1,616 applications and their replacement strings at that time. <a href=\"https:\/\/circleid.com\/posts\/icann-sets-october-7-for-2026-new-gtld-reveal-day\" target=\"_blank\" rel=\"noopener\">CircleID reported<\/a> the date lands a week earlier than ICANN&#8217;s own prior outside estimate, which had pointed to no later than October 14.<\/p>\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\">\n<h2>Table of Contents<\/h2>\n<nav>\n<ul>\n<li><a href=\"#h-what-reveal-day-actually-reveals\">What Reveal Day actually reveals<\/a><\/li>\n<li><a href=\"#h-why-none-of-this-changes-what-you-can-register-today\">Why none of this changes what you can register today<\/a><\/li>\n<li><a href=\"#h-what-happens-when-two-applicants-want-the-same-string\">What happens when two applicants want the same string<\/a><\/li>\n<li><a href=\"#h-the-domain-decision-that-actually-has-a-deadline\">The domain decision that actually has a deadline<\/a><\/li>\n<li><a href=\"#h-if-a-new-extension-actually-fits-your-brand\">If a new extension actually fits your brand<\/a><\/li>\n<li><a href=\"#h-what-to-actually-do-this-week\">What to actually do this week<\/a><\/li>\n<\/ul>\n<\/nav>\n<\/div>\n<p>If that sounds like the moment a wave of new domain extensions becomes available to register, it isn&#8217;t, and that gap between what Reveal Day sounds like and what it actually does is worth closing before anyone makes a domain decision based on it.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-what-reveal-day-actually-reveals\">What Reveal Day actually reveals<\/h2>\n<p>The 1,616 applications aren&#8217;t from small businesses trying to register a catchy new domain. Each one is a formal bid to operate an entire new top-level domain registry, submitted with an application fee reported at $227,000, a cost that puts this process squarely in the territory of global brands, city governments, and industry bodies, not individual site owners. An applicant might be a bank applying to run its own branded extension, a city applying to operate a geographic TLD, or a registry operator like Identity Digital or GoDaddy applying for a new generic string they plan to sell registrations under later.<\/p>\n<p>What Reveal Day actually publishes is who applied for what, and where those applications collide. From October 8 through October 21, applicants whose preferred string conflicts with someone else&#8217;s can switch to a backup &#8220;replacement string&#8221; instead, provided it doesn&#8217;t also collide with another applicant&#8217;s choice. ICANN then plans to release the finalized list, with updated contention sets reflecting those switches, on November 17.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-why-none-of-this-changes-what-you-can-register-today\">Why none of this changes what you can register today<\/h2>\n<p>Contention resolution, likely auctions for the strings multiple applicants still want after the replacement-string window closes, technical and background evaluations, and contractual delegation all happen after Reveal Day, not before it. Based on the pace of ICANN&#8217;s previous new gTLD round, which ran through most of the 2010s after opening in 2012, coverage of this round&#8217;s realistic timeline puts usable registrations from newly approved extensions at 2028 at the earliest, and likely later for any string caught in a contested auction. Reveal Day is the start of a multi-year administrative process, not a launch event for new domains anyone can buy next month.<\/p>\n<p>That distinction matters because &#8220;new domain extensions&#8221; coverage tends to blur two entirely different things: extensions from the 2012 round that already exist and are registerable right now (.shop, .app, .studio, .tech, and hundreds of others), and extensions from this 2026 round that won&#8217;t exist as registerable products for years. A business deciding what domain to register this quarter should be looking at the first category exclusively; the second one isn&#8217;t a live option yet under any circumstance.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-what-happens-when-two-applicants-want-the-same-string\">What happens when two applicants want the same string<\/h2>\n<p>Contention sets are the part of this process most likely to stretch the timeline even further. When more than one qualified applicant wants an identical string, and the October 8-21 replacement-string window doesn&#8217;t resolve it because neither side is willing to switch, ICANN&#8217;s established mechanism from the prior round was a last-resort auction, with the string going to whichever applicant was willing to pay the most for it.<\/p>\n<p>That process alone added a year or more to some strings in the 2012 round, on top of the baseline evaluation timeline every application goes through regardless of contention. A string with multiple serious bidders, likely for generic, commercially valuable words rather than obscure ones, is exactly the kind of application where 2028 becomes an optimistic estimate rather than a firm date.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-the-domain-decision-that-actually-has-a-deadline\">The domain decision that actually has a deadline<\/h2>\n<p>While the 2026 gTLD round runs its multi-year administrative course, something with a real, immediate deadline is happening to the extension most businesses actually use. Verisign, which operates the .com registry under its contract with ICANN, raises its wholesale .com price from $10.26 to $10.97 on November 1, 2026, pushing the registrar-level cost from $10.46 to $11.17 a year once ICANN&#8217;s fee is included, roughly a 6.9% increase. That&#8217;s the first .com price adjustment since September 2024, and it&#8217;s not a one-off: it&#8217;s the first of four annual increases permitted under Verisign&#8217;s current six-year contract, with further hikes of up to 7% allowed in 2027, 2028, and 2029.<\/p>\n<p>Retail prices at most registrars track that wholesale change and rise accordingly after November 1. For any business that knows it needs a .com domain, whether for a new site, a rename, or a domain it&#8217;s been meaning to lock down before someone else does, registering or renewing before that date, and doing it for multiple years at once where a registrar allows it, locks in the lower rate for the length of that registration. That&#8217;s a concrete, dated action available right now, in a way that nothing about Reveal Day is.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-if-a-new-extension-actually-fits-your-brand\">If a new extension actually fits your brand<\/h2>\n<p>None of this means new domain extensions are irrelevant to a small or growing business, just that the relevant ones already exist and don&#8217;t require waiting on a 2026 application to resolve. An online store might genuinely benefit from <code>.shop<\/code> over a compromise <code>.com<\/code> name that&#8217;s already taken; a software or app business might get real, immediate clarity from <code>.app<\/code> or <code>.dev<\/code>; a creative studio might find <code>.studio<\/code> does part of the brand communication on its own. These are live, registerable extensions today, distinct from and unrelated to whatever emerges from the 1,616 applications ICANN is about to reveal.<\/p>\n<p>The honest tradeoff with any non-.com extension, new or old, is recognition: .com remains the default assumption for a huge share of internet users, and a less familiar extension can cost a small amount of trust or memorability with an audience that isn&#8217;t used to seeing it, even when the extension itself is perfectly legitimate and well-established. For a business where the extension itself reinforces the brand (a <code>.shop<\/code> for a literal online shop) that tradeoff usually favors the new extension; for a business where the name matters more than the label around it, defaulting to .com and accepting a slightly less perfect name is usually the safer call.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-what-to-actually-do-this-week\">What to actually do this week<\/h2>\n<p>The practical response to this week&#8217;s domain news has almost nothing to do with the headline event. Reveal Day is worth knowing about if you&#8217;re curious which brands and registries are maneuvering for control of the next generation of internet real estate, a genuinely interesting story for anyone who follows the domain industry, but it produces no action item for a business buying a domain today.<\/p>\n<p>The action item is the .com price increase landing November 1: check any domain renewals coming up in the next few months, and consider locking in a longer registration term at today&#8217;s lower price through your <a href=\"https:\/\/allcloudhost.net\/cheap-domain-registration\/\">domain registrar<\/a> before the new rate takes effect. That&#8217;s a real, dated, small but avoidable cost, sitting right next to a much bigger, much slower story that won&#8217;t affect an actual registration decision for years.<\/p>\n<p>Most registrars let a domain be renewed for up to ten years at once regardless of when the current term ends, so locking in several years now, rather than just the standard single-year renewal, captures the pre-increase rate for the entire locked-in period rather than only the next twelve months.<\/p>\n<p>Checking auto-renew settings at the same time is worth the extra minute: a domain set to auto-renew will simply bill at the new, higher rate once November 1 passes, with no separate notification calling out that the price itself changed rather than just the usual annual renewal. A five-minute check against an upcoming renewal date is a small task next to the multi-year administrative process Reveal Day kicks off, but it is the one with an actual deadline attached.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At 18:00 UTC on October 7, ICANN will publicly disclose all 1,616 applications submitted for new top-level domains in its 2026 expansion\u2026<\/p>\n","protected":false},"author":2,"featured_media":1339,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"rank_math_title":"ICANN Reveal Day 2026: Avoid the Hype, Know the Facts","rank_math_description":"ICANN's Reveal Day on October 7 shows 1,616 new domain extension applications. What that changes for a business buying a domain today: nothing yet.","rank_math_focus_keyword":"reveal day,new domain extensions 2026,com price increase November 2026","rank_math_canonical_url":"","rank_math_robots":[],"footnotes":""},"categories":[9],"tags":[],"class_list":["post-1340","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-domains"],"_links":{"self":[{"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/posts\/1340","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/comments?post=1340"}],"version-history":[{"count":2,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/posts\/1340\/revisions"}],"predecessor-version":[{"id":1873,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/posts\/1340\/revisions\/1873"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/media\/1339"}],"wp:attachment":[{"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/media?parent=1340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/categories?post=1340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/tags?post=1340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}