.update
Is .update a real TLD? Who’s applying to run it?
.update is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is NextGEN TLDs GmbH.
A functional word that fits changelogs, newsletters and release pages, but few projects would make it their main name.
software teams, newsletter and status-page publishers, and media outlets wanting a short "something.update" address for release notes, announcements or subscriber feeds
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet: a bare software-lifecycle verb nobody brands themselves with, sold as a functional address for the act of shipping bits to users — demand depends on publishers adopting a utility label rather than on any identity or community.
Same bet shape: a generic abstract noun for one channel a company emits to its users, bought as a labelled endpoint (brand.feedback / brand.update) rather than as a primary identity, so its ceiling is per-company utility pages, not a market of registrants.
The nearest category-noun version of the same "fresh information" bet, but a real class of buyers (publishers) would put their primary identity on it, where .update is a weaker, more functional cousin of that same information-refresh demand.
What a .update domain is
.update is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. One application for it is on ICANN’s Reveal Day list.
Is the .update domain extension real yet?
.update is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .update domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .update name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .update was .download, delegated on 25 March 2015.
Is .update a real TLD?
Not yet. .update is not in the DNS root, so nothing resolves under it. It’s here because .update is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- NextGEN TLDs GmbH · first recordedICANN
“GEL2647T-T15541 · Glass Emotion, LLC · primary · contention set 2026-116 NSL2674T-T66583 · NAME SPACE LLC · primary · contention set 2026-116 NTG2671T-T35907 · NextGEN TLDs GmbH · replacement string of .tkns · Deactivated XL2625T-T36661 · XYZ.COM LLC · replacement string of .dao · Deactivated”ICANN
- Band chosen: 30-49 (usable but limited), at its low end. The string is a common English noun/verb tied to a recognisable function: software release notes, status and changelog pages, newsletters, news-style daily-update feeds. That gives it plausible secondary-address use (a product's release channel, a publisher's subscriber feed) and some price-driven registration volume, which is why it sits above the 10-29 vanity band: the demand is functional rather than joke or event-driven. It is not in 50-69 because no major category would adopt .update as a primary identity; projects name themselves after what they are, not after one activity they perform, so most registrations over the next 5 years would likely be redirects or utility addresses of an existing brand, which yields a weak brand signal and a thin aftermarket. By analogy (flagged as analogy), function-word TLDs such as .link, .click and .download have found volume mainly on price and utility rather than identity, while word TLDs with a clearer publishing category (.news, .today, .live, by analogy) achieved sustained mid-scale niche use; .update sits closer to the former group because the word describes an action performed on something else. A string-level headwind is that the word is often seen in deceptive account-notification messaging, which may weigh on user trust and on how some filters treat addresses under it; this is an observation about the string, not about any operator. On the record there is one confirmed standard application, from NextGEN TLDs GmbH, with .traffic recorded as a replacement string naming it as primary; the contention count is 1. Main market uncertainty: whether release-notes and newsletter publishers treat a .update address as a real destination they promote, or only as a redirect, which decides whether volume ever becomes identity use. Figures on registrations, pricing, or comparable-TLD volumes are unknown from the verified facts and are not asserted.