.near
Is .near a real TLD? Who’s applying to run it?
.near is not contested. One applicant has said publicly that it applied to run it, and nobody else has, as of 15 August 2026. It is Link Freedom Group.
A crypto-flavored web address built on a common English word; useful for some, but a niche choice that needs explaining.
crypto and web3 teams building in or around the NEAR ecosystem, plus local-commerce and proximity-tech projects drawn to the generic English word (near me, nearby services).
In LFG's published list of 300+ strings submitted before the ICANN window closed on 2026-08-12. Their catalog tagline: “Closer than you think.”
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 exactly: a short relational/deictic English word with no category meaning of its own, sold on the idea that proximity-and-location services can hang their primary identity on a positional word rather than a noun describing what they sell.
Same class of bet — a plain, evocative place-word that names no industry, so its value depends entirely on registrants reading a location/'where you are' meaning into it rather than on category-matched demand.
The temporal twin of the same wager: an abstract adverb with universal appeal and zero category anchor, betting that immediacy/context words can carry brands across unrelated verticals instead of serving one defined buyer.
What a .near domain is
.near is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Crypto. One applicant has said publicly that it applied for .near.
Is the .near domain extension real yet?
.near 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 .near domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .near name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .near was .here, delegated on .
Is .near a real TLD?
Not yet. .near is not in the DNS root, so nothing resolves under it. It’s here because an applicant said publicly that it applied for .near in the ICANN 2026 new gTLD round. Every claim on this page links to its source.
- Link Freedom Group · first recordedLink Freedom Group
“.near · Crypto & Web3 · “Closer than you think.””Link Freedom Group
“LFG voluntarily published its full list of submissions ahead of ICANN’s official Reveal Day.”PR Newswire (Link Freedom Group)
“Top level domain registry Link Freedom Group (LFG) has disclosed more than 300 strings submitted as part of the ICANN new top level domain name program.”Domain Name Wire (Andrew Allemann)
- Band chosen: 30-49, usable but limited. The string carries two demand sources: it matches the name of a known blockchain ecosystem (from my own knowledge, no figures asserted), and it is a common English word for proximity, which supports local-commerce and location-adjacent uses. By analogy (flagged as analogy), crypto-themed extensions in the ICANN root have tended to see event-driven registration spikes rather than sustained primary-identity adoption, since web3 projects often prefer on-chain naming systems or established extensions for their main web presence; that pattern caps this string below the 50-69 band, where genuine sustained primary-identity demand would be required. It sits above the 10-29 band because the generic-word meaning gives it a second, non-meme demand channel and plausible serious end-use beyond novelty, and the applicant's stated positioning (category Crypto & Web3, tagline 'Closer than you think.') leans into both readings. The applicant, Link Freedom Group, filed more than 300 strings in the ICANN 2026 round and published its list ahead of Reveal Day; a broad-portfolio applicant suggests generalist registry marketing rather than ecosystem-native distribution, which tempers adoption likelihood over the next 5 years (a neutral observation about go-to-market, not the operator). Main market uncertainty: whether the matching blockchain community embraces the ICANN-root extension as complementary to its on-chain naming, ignores it, or treats it as unaffiliated, since that single dynamic drives most of the realistic aftermarket.