Bluesky has formally applied to ICANN for control of its own top-level domain, .bsky, a request that would let users claim addresses such as yourname.bsky that function simultaneously as a social handle and as a real, resolvable web address. The company’s stated goal is to push social identity out of a single platform’s database and into the internet’s own naming system.
- A domain, not just a username: The proposed TLD would shorten handles to something like yourname.bsky instead of the current yourname.bsky.social, while giving users a portable address they control.
- No monetization: Bluesky has explicitly confirmed it will not sell or monetize .bsky registrations, breaking with the standard TLD business model built on annual registration fees.
- A long road ahead: Approval typically takes 18 to 24 months in the best case, and past ICANN rounds have stretched to three to five years. Success is not guaranteed.
From platform handles to portable identity
A top-level domain is the final extension of a web address: .com, .org, .es, .uk. ICANN ran its first major expansion round in 2012, generating hundreds of applications spanning everything from .google to .bank, and is now preparing to open a new application window.
Bluesky wants .bsky to deepen one of its most distinctive features: the ability to use any domain you own as your username on the network. If you already control a personal domain, you can attach it to your account today thanks to the AT Protocol, the open protocol the platform is built on. A company-operated .bsky would extend that concept a step further, natively integrating decentralized identity with DNS at zero cost to the user.
The technical logic is elegant. Instead of following someone at a handle tied to the platform, the way every centralized network works, you would follow an address that belongs to the account holder and keeps functioning outside Bluesky if they ever migrate to another node running the same protocol. Handles get shorter, cleaner and, in theory, more durable.
The no-monetization pledge and who actually pays
Most TLD operators make money by charging for each annual registration. A business that wants its own branded extension pays anywhere from roughly 5 to 50 euros per year depending on the registrar, with a cut flowing back to the TLD operator. Bluesky has said it will not follow that model.
The promise is striking and consistent with the company’s positioning, but it carries a practical consequence: someone still has to fund the operational cost of running a TLD. DNS infrastructure, domain dispute resolution procedures, ICANN policy compliance and continuous technical support are not cheap, and the financial evaluation attached to an application assumes the operator can keep the registry alive for decades rather than quarters.
The gap between the pledge and the economics remains the most obvious unresolved question, particularly for a platform that has not yet consolidated a subscription business.
ICANN’s gauntlet: technical, financial and contested
The application process is far more than paperwork. It includes a technical assessment of the company’s ability to operate the registry with stability, covering redundancy, uptime requirements and contingency plans under ICANN supervision. A financial solvency review must show the operator can sustain the TLD long term. Finally, an objections period allows any party that believes .bsky conflicts with an existing trademark to file formal complaints.
The application could take between 18 and 24 months to go through, according to Bluesky CEO Toni Schneider.
Even that timeline may prove optimistic. Most candidates in the 2012 round waited between three and five years between filing and actually operating their registries. Bluesky would have to demonstrate to ICANN a level of organizational maturity well beyond that of a typical social media startup, with the legal and financial scaffolding of a domain registry behind it.
The move also lands in a competitive context where Meta is aggressively courting users disillusioned with X through frequent product changes and new subscription tiers. Framed against that, a TLD application reads as a long-term bet that communicates institutional permanence rather than feature parity.
What a proprietary TLD does not solve is distribution. Bluesky’s technical foundation has proven solid, and its identity model is the most coherent of any post-X network, but conversation volume still lags far behind its rival. Owning .bsky reframes the value proposition in an interesting way: if your digital identity lives on a domain you control, the product stops being a social network and starts being identity infrastructure. That shifts the question from why you use a given app to what you actually own when you hold an address there. It is a more durable story, but it is not yet a mass-market answer, and no registry can manufacture the cultural moment that social platforms ultimately live or die on. Bluesky now has the architecture to exploit that moment if it arrives.
Sources & References