.vrs
Is .vrs a real TLD? Who’s applying to run it?
.vrs is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is RP1.
A three-letter brand string with no plain meaning; useful to its applicant as a private namespace, not something others would buy.
the applicant itself, for its own product and service addresses; no third-party buyer group is implied by the string
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 as a vowel-stripped three-letter string offered as a general-purpose suffix: the registry has to convince the market that the consonant skeleton reads back as the longer word it compresses, because the string carries no meaning of its own.
Same bet as an opaque three-letter industry initialism: it means something precise to the handful of people inside one sector and nothing at all outside it, so the addressable base is a trade, not a public.
Same bet in the single-owner version of it: a consonant abbreviation of a longer proper name where the meaning is supplied entirely by the one organisation putting its identity there, not by the string.
What a .vrs domain is
.vrs is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .vrs domain extension real yet?
.vrs 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 .vrs domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .vrs name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .vrs was .onl, delegated on 28 December 2013.
Is .vrs a real TLD?
Not yet. .vrs is not in the DNS root, so nothing resolves under it. It’s here because .vrs is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- RP1 · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The record shows one application, by Metaversal Corporation, filed as a brand type with .loc recorded as its replacement string; the contention count on the record is 1. A brand-type application generally means a closed namespace used by the applicant for its own addresses, so the best-fit buyer is the applicant and the aftermarket is effectively absent. The string itself is an opaque three-letter abbreviation: readers may associate it with virtual reality or a service acronym, but it carries no self-evident category meaning that would make an outsider pick it over established endings. By analogy (flagged as analogy), closed brand TLDs from the 2012 round tended to see modest internal use, with some operators using them for redirects or a handful of product addresses and others leaving them dormant, and essentially no resale market. It is not in the 30-49 band because registrations at volume or on price do not happen in a closed brand namespace and no brand signal reaches outside buyers; it is above the 1-9 band because the applicant can get real end-use utility from a short memorable string as a primary identity for its own properties within the next 5 years. Main market uncertainty: how actively the applicant deploys the string for public-facing products versus internal or redirect use, which determines whether anyone outside the company encounters .vrs addresses at all.