.via
Is .via a real TLD? Who’s applying to run it?
.via is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is XYZ. Intercap named .via as a backup string for its .visit application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A neat short word that works as a 'by way of' hack, but it owns no category, so demand likely stays modest and price-driven.
startups and consumer apps in payments, messaging, transit and travel wanting a short connector-style name ("send.via", "pay.via"), plus Romance-language local businesses where "via" means street
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .visit application, shown as deactivated: another applicant applied for the same string or named it as a backup
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 .via: a short, meaning-light English locative/directional function word with no trade or category behind it, so nobody is already "a here business" — the value sits entirely in the phrase the second level completes, and demand has to be manufactured rather than captured.
The purest form of the same wager — that a grammatical connector rather than a category noun can anchor a namespace — differing from .via only in having no residual noun sense at all, so it leans even harder on registrants building a readable phrase.
Another three-letter common-word play sold on a connotation (immediacy; for .via, routing or by-way-of) instead of membership in an industry, so both succeed only if brands adopt it as a product label, with no pre-existing pool of buyers who already describe themselves with the word.
What a .via domain is
.via 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 .via domain extension real yet?
.via 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 .via domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .via name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .via was .here, delegated on 29 August 2014.
Is .via a real TLD?
Not yet. .via is not in the DNS root, so nothing resolves under it. It’s here because .via is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Band chosen: 30-49, usable but limited. The string is a short, pronounceable word understood across English and the Romance languages (English 'via' = by way of; Italian/Spanish/Portuguese 'via' = street/way), which makes it a plausible connector suffix for payments, messaging, transit and travel products and a loose fit for street-level local businesses. It is not in the 50-69 band because it owns no category: 'via' is a preposition, so most primary-identity uses are domain hacks that need explaining rather than a natural fit, and connector-style generics from the 2012 round (by analogy, strings like .link and .click) have tended toward volume on promotional pricing with a thin aftermarket rather than sustained category-standard adoption. It is not in the 10-29 band because the word is globally legible, three letters, and carries a real functional meaning rather than a joke or event hook; three-letter dictionary strings have, by analogy, drawn some genuine brand and aftermarket interest. On the record the confirmed applicant is XYZ.COM LLC (a standard application; a second application by Intercap Registry Inc. is deactivated, with .visit as its primary string, and an XYZ application for .vault naming .via as primary is also deactivated); the applicant's existing registrar distribution plausibly raises registration reach, which informs adoption likelihood but not brand strength. Main market uncertainty: whether the connector/hack use case attracts real primary identities that renew, or whether registrations stay promotion-driven and churn. Counts, prices and renewal figures for any analogous TLD: unknown; all comparisons here are by analogy.