.browser
Is .browser a real TLD? Who’s applying to run it?
.browser is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A narrow tech word: fine for browser makers and in-browser tools, but most projects will still pick .app or .dev over it.
browser vendors, browser-extension developers and makers of browser-based web tools who want an address that says "runs in your browser"
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.
Both are the generic noun for a single class of consumer client software, so the only credible primary-identity holders are the handful of firms that ship that product plus the surrounding support/download ecosystem — a narrow vendor-category bet, not an open registrant pool.
Same bet shape of owning the plain-English name of a core web-software function whose identity is concentrated in very few players, but it is an activity word with broader everyday use than a named product class.
Also a bet on the category noun for one specific class of computing product with a tiny set of makers, differing in that the category is hardware and was essentially a vendor-created term rather than an organically generic one.
What a .browser domain is
.browser 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 .browser domain extension real yet?
.browser 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 .browser domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .browser name can only be registered after that, once the string is delegated and its registry opens.
Is .browser a real TLD?
Not yet. .browser is not in the DNS root, so nothing resolves under it. It’s here because .browser is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T84800 · Charleston Road Registry Inc. · primary”ICANN
- Band chosen: usable but limited (30-49), at the low end. The string names a real product category (web browsers) and carries a second plausible meaning, "runs in the browser", which gives it a legitimate end-use for browser-based tools and extensions; that is more than joke or event-driven demand, so it sits above the vanity band. It does not reach the strong-niche band because the natural buyer pool is small (a handful of browser vendors plus extension and web-tool makers), and the developer-facing generics .app and .dev already serve the "web application" identity role, so most serious projects would choose those without explanation while .browser would need explaining. By analogy (inference, not fact): narrow single-concept tech generics such as .how, .foo, .soy and .ing have tended to see thin registration and little aftermarket, whereas broad category generics such as .app and .dev found real primary-identity use; .browser resembles the narrow group far more than the broad one. The single application on the record is from Charleston Road Registry Inc.; by analogy with other TLDs run by that applicant this could mean wide registrar distribution and security-oriented defaults, or it could mean restricted or affiliated use. Registration counts, prices and launch dates are unknown. Main market uncertainty: whether the "in-browser" meaning catches on with web-app makers as a differentiator from .app over the next 5 years, or whether it stays a vanity redirect for a few browser brands.