Bluesky Applied for .bsky: What a Native Domain Would Change
Bluesky has applied for “.bsky” as a generic top-level domain, the same category as .com or .org, CEO Toni Schneider disclosed. If granted, it would give Bluesky control of its own section of the internet's naming system instead of operating mainly inside names rented from others and its current bsky.social subdomain. TechCrunch
The application has not been approved. ICANN is scheduled to publish this round of new applications on October 7, 2026, including Bluesky's request. Bluesky expects approval to take 18 to 24 months from that point. Until delegation, contracts and policy work are finished, nothing changes for existing handles.
If approved, the day-to-day change would be shorter handles. A default handle like sarahp.bsky.social could become sarahp.bsky. That shorter version would still be a complete domain name on the public internet, readable by DNS (the Domain Name System, the directory that turns names into addresses), not just a nickname inside the app.
Bluesky has not finalized how those second-level names under .bsky would be requested, registered or handed out. The company says it has no plans to sell or monetize “.bsky” domains, and COO Rose Wang is listed as a point of contact. That leaves open the registry details: whether current bsky.social strings are reserved, how trademark sunrise and name-collision rules work, which registrar channel would be used, plus renewal and abuse procedures.
This builds on a handle model Bluesky already offers. Users can replace the default handle with their own website domain, or buy a custom domain through Bluesky. AP The app's Change Handle screen includes an “I have my own domain” option, where users type the full handle again for verification. Bluesky Using a domain this way helps with account identity, verification and moving an account between hosting providers. Bluesky
The broader context here is who controls the identifier layer. Today a Bluesky user who wants a portable handle that proves itself must bring a domain bought in the existing market for endings like .com or country codes, and link it to the account. Running “.bsky” would remove that extra step for people who want a native name, with Bluesky acting as registry operator rather than as a tenant in someone else's zone. Registry operation is a different job from managing usernames in an app database, with duties around root-zone delegation, data escrow, WHOIS records and compliance.
In my view, the shorter name is not the real test. The question is whether Bluesky can keep those handles truly portable while it also holds the registry keys. A company-run ending would make setup and verification simpler, and spare users from dealing with registrars they may not understand. It also concentrates policy control. Users and developers will want clear answers on transfers, what happens to a name if an account is suspended, whether a “.bsky” name can point outside Bluesky, and how disputes are settled without a market to set prices. Taking monetization off the table settles one concern. The governance answers will matter more over the next 18 to 24 months.
