Pavel Durov announces Telegram has applied for the '.gram' top-level domain. The immediate reaction is a chorus of '10 billion users, free domains, the next Web3 identity layer.' I read the implementation, not the intent. The code does not lie, only the whitepaper does. And here, the whitepaper is a single Telegram post with zero technical specification. No ICANN confirmation. No audit trail. Just a promise.
Let me be clear: Telegram's user base is massive. Their Mini App platform is real. But converting a social graph into a DNS registry is a different engineering discipline. I have audited protocols that claimed to bridge Web2 and Web3. Most failed because they underestimated the operational burden of a globally resolvable namespace. Trust is a variable, verification is a constant. Let's verify.
Context: The Hype Cycle of Identity Infrastructure
The industry is desperate for a 'killer app' that justifies blockchain beyond speculation. Web3 domains (ENS, Unstoppable) have struggled to gain mainstream adoption. Now Telegram, with its 900 million active users, proposes to map every username to a .gram domain. The narrative is seductive: 'Your Telegram handle becomes your website.' But the history of new gTLDs is littered with failures. Google's .app, .dev, .page — they have utility but not viral adoption. The average user does not care about DNS. They care about convenience.
Telegram's advantage is distribution. Their disadvantage is that they are not a DNS operator. They have no experience with ICANN compliance, DNSSEC signing, or abuse handling. The Dencun upgrade lowered fees for rollups, but post-Dencun blob data will be saturated within two years, and then all rollup gas fees will double again. Similarly, Telegram's initial free domain allocation will hit a scaling wall. The ledger remembers what the founders forget.
Core: Systematic Teardown of the .gram Proposal
Technical Feasibility
Telegram's existing infrastructure resolves t.me/username to a profile page. That is a simple HTTP redirect, not a DNS delegation. To operate a top-level domain, Telegram must deploy an authoritative DNS cluster, support DNSSEC, and maintain a global anycast network. They must also handle zone transfers, registrar interfaces, and WHOIS/RDAP services. Based on my audit experience, a company that has never run a DNS backend will take at least 18 months to build a production-grade system. The announcement shows no evidence of such preparation.
Security and Abuse
A domain open to 900 million users is a phisher's paradise. Telegram will need to implement real-time abuse detection, takedown procedures, and cooperation with law enforcement. This contradicts Telegram's historical stance on censorship resistance. The SEC's regulation-by-enforcement is not ignorance of technology — it is deliberately withholding clear rules. ICANN will force Telegram to adopt a similar compliance posture. If Telegram refuses, .gram will not be resolvable from standard DNS resolvers, killing its value.
Regulatory Compliance
ICANN's new gTLD application fee is approximately $185,000. That is the least of the costs. The ongoing obligations include: annual registry fees, DNS abuse metrics reporting, trademark clearinghouse involvement, and GDPR-compliant WHOIS. Telegram's privacy-focused brand will clash with ICANN's requirement to collect and disclose registrant data. The EU's MiCA and GDPR create additional layers. I have seen projects underestimate regulatory friction by a factor of ten. .gram will be no different.
Business Model
The article analysis suggests a gross margin above 80% for domain registrations. But the key variable is renewal rate. If users treat .gram as a disposable vanity URL, lifetime value will be near zero. Telegram needs to create a compelling reason to renew — such as bundling with Premium subscriptions or Mini App hosting. Without that, .gram becomes a cost center, not a revenue stream. The assessment of a 'high-margin, low-acquisition-cost' model is correct only if activation rates exceed 10%. Historical data from similar experiments (e.g., Google's .new domains) suggest activation will be below 5%.
Contrarian: What the Bulls Got Right
I am not a cynic by default. The contrarian view has merit. Telegram's social graph is a genuine moat. If every channel, group, and user automatically gets a .gram domain, the network effect is real. Developers can create Mini Apps tied to a domain, reducing friction. The integration with TON could create a Web3 identity layer that competes with ENS. The potential for emerging markets — where traditional hosting is expensive — is significant. The bulls are correct that the distribution channel is unparalleled.
However, the gap between potential and execution is vast. The bulls ignore the operational reality of running a registry. They assume that 'decentralized' means 'no rules.' The ledger remembers what the founders forget: ICANN is a centralized gatekeeper. If Telegram tries to bypass ICANN with a blockchain-based alternative root, they will fragment the internet. That is not innovation; it is isolation.
Takeaway: Accountability Through Audit
Telegram's .gram is a speculative bet on distribution overcoming engineering. The code does not lie, only the whitepaper does. Until I see an independent security audit of their DNS infrastructure, a published abuse handling policy, and a clear ICANN compliance roadmap, I treat .gram as a marketing stunt. The ledger remembers what the founders forget: the cost of cutting corners in infrastructure is borne by users, not by Telegram. Precision is the only form of respect. I will wait for the audit before I type a single .gram URL.