Bluesky Files for .bsky and Enters the Registry Queue

Bluesky has applied to ICANN for a.bsky internet suffix, a move CEO Toni Schneider said would take 18 to 24 months. The filing would let handles such as alice.bsky exist if the bid clears.

It also puts the social app in line to run a piece of the domain name system, in a round of 1,616 paid applications that ICANN is set to publish at 18:00 UTC on October 7, 2026.

Bluesky Filed for a Whole Internet Suffix

On October 5, 2026, Schneider posted a short note ahead of ICANN’s Reveal Day. He said the nonprofit would publish 1,000+ applications for new top-level domains, and that one of them is.bsky. ICANN’s paid count is higher than that teaser: 1,616 paid applications will proceed from 1,663 submissions after the window closed on August 12, 2026.

The post is the whole product pitch in two sentences. If the string is delegated, handles like alice.bsky become possible, in place of the default alice.bsky.social form most accounts still carry. He called it a long road of 18 to 24 months.

A little scoop before Oct 7, when ICANN publishes 1,000+ applications for new top-level domains: one of them is .bsky! It's a long road (18 to 24 months), but if it goes through, handles like alice.bsky become possible.

— Toni Schneider (@toni.bsky.team) 2026-10-05T13:44:00.648Z

That is not a username tweak inside the app. A top-level domain is a suffix in the global naming system, the same class as.com or.org, and the company that receives it signs on as registry operator. Bluesky would run the zone for every name that sits to the left of.bsky, under an ICANN registry agreement, with the technical and legal duties that follow from that contract.

Schneider also floated a later product idea: once the suffix exists, a profile could grow from a bio-and-posts page into a fuller personal home page. Bluesky has not said how that page would be hosted, how names would be handed out, or whether alice.bsky would resolve in a browser the way a normal website does. Those answers sit on the far side of evaluation.

You Can Already Use a Domain You Own

The AT Protocol treated handles as domain names years before this filing. On March 6, 2023, Jay Graber wrote that Bluesky had registered its first custom domain name handle. Daniel moved from @dan.bsky.social to @dholms.xyz because he owned dholms.xyz.

A handle on Bluesky is a hostname. The long-lived account identifier underneath it is a DID, a string that stays put when the public name changes. You prove control of a domain with a DNS TXT record on the _atproto subdomain, or with a plain file at /.well-known/atproto-did, and the DID document has to point back at that handle. Help docs walk through how to set a domain you own as a handle, and they warn that the old.bsky.social name becomes free for someone else once you leave it.

WHAT A CUSTOM HANDLE ALREADY DOES

• Site as proof: Graber’s 2023 note said a newsroom could sit at a name like @npr.org, so the website and the account share one root of trust.
• Same name elsewhere: The handle is meant to travel with you onto other AT Protocol apps, so you are not collecting a fresh username on each client.
• Move without a rename: If you leave the bsky.social service for another host, a domain you control can stay on the account.

In July 2023 the company also partnered with Namecheap so people could buy a domain inside Bluesky and attach it without leaving the app. Anyone who already paid for a.com,.org, or.xyz handle is not waiting on ICANN for a short, clean name. They have one. The.bsky bid is for everyone who never bought a domain and still lives on the long default suffix.

The Ticket Costs $227,000

This is the first new-gTLD application window since 2012. It opened on April 30, 2026, and closed at 23:59 UTC on August 12, 2026. ICANN’s standard USD 227,000 per application covers the required reviews, including background screening, DNS stability, and financial and operational checks. Qualified Applicant Support Program bids get a 75 percent to 85 percent cut. Extra reviews, from community priority to a high-risk name-collision plan, are billed on top.

THE 2026 GTLD ROUND IN NUMBERS

Forty-seven filings never reached the paid stage. ICANN does not publish which of the remaining bids came in at the full fee, so a round-wide total would be a guess. What the check buys is a place in evaluation, not a live suffix in the root. After a registry agreement, ICANN’s fee FAQ notes, operators still owe annual registry fees and Trademark Clearinghouse charges. A company that says it will not sell names still has to fund that machinery.

Most of the 1,616 paid filings are ordinary commercial bets on a string. ShortDot and other portfolio applicants have talked in public about dozens of short endings. Bluesky’s bid is odd in that company: a social app paying the same entry price to hold a four-letter suffix that it says it will not turn into a shop.

No Plan to Sell the Names

Reached after Schneider’s post, Bluesky said it has not settled how.bsky names would be requested, registered, or handed out. It did say it has no plan to sell or monetize them. Rose Wang, the company’s COO, tied that pledge to the same ownership line the protocol has used since 2023.

Domains are a big part of the open web, as they allow users to control their own online identity. Bluesky was built on the belief that you should own your presence online, not rent it from a platform that can take it away.

Rose Wang, COO, Bluesky

The words land cleanly next to custom.com handles, which the user buys from a registrar and can take to another AT Protocol host. They sit less cleanly next to.bsky. If Bluesky is the registry, every alice.bsky name lives in a zone the company operates under ICANN rules. Users would not be renting a post from a feed the way they do on a closed app, but they would still depend on Bluesky to keep the suffix in the root and to keep their second-level name in the zone.

That is the second-order shift. The 2023 design pushed people off Bluesky’s own suffix and onto domains they already paid for. The 2026 filing pulls a slice of identity back onto a suffix with the company’s name on it. A free alice.bsky would be easier than buying dholms.xyz. It would also be easier for Bluesky to keep as the default public face of the network, which is a different kind of control than a third-party.com.

The company has raised large private rounds and is not running ads. Skipping domain sales closes one obvious path to cash from the same filing. It does not close the annual registry bill, the cost of a backend operator, or the staff time to answer objections. A no-sale pledge is a policy. The registry contract is a bill.

What Happens to the Long Handles?

Default accounts would be the ones that feel the cut, if delegation ever happens. @sarahp.bsky.social shrinking to sarahp.bsky is the example Schneider’s post implies and that later write-ups repeated. People who already mapped a personal domain onto the account would gain little, unless Bluesky also turns.bsky names into web pages that a browser can load. The company has not said whether a.bsky name will be a handle only, a website, or both.

WHAT WE KNOW

• The string: Schneider said Bluesky applied for.bsky, and that ICANN would list the bid on Reveal Day.
• The wait: He put the remaining process at 18 to 24 months, which from October 2026 runs to April 2028 at the short end and October 2028 at the long end.
• The sales line: Bluesky said it has no plan to sell or monetize the names, and it has not published a request or lottery scheme.

WHAT IS UNCONFIRMED

• Contention: Another applicant may have filed for the same string; that only becomes visible when ICANN posts contention sets.
• Application type: The public forms will show whether Bluesky filed this as an open suffix, a brand TLD, or something with extra commitments.
• The cutover: There is no published map for who gets first pick of short names, or what happens to a parked alice.bsky.social if alice.bsky is assigned to someone else.

If the old default names stay in DNS as aliases, a two-year migration is messy but survivable. If they do not, every link, business card, and search result that still points at.bsky.social becomes a forwarding problem. Bluesky’s own help text already treats a handle change as a release of the previous name. Apply that rule to a forced suffix cut, and the squatters show up the morning the zone opens.

A two-year identity project only pays off if the network is still the place people look. Replies under the first wide write-up of the filing treated Bluesky as a niche tab, which is a crude reading of a live protocol and a real user base, and still a fair warning about calendar risk. A suffix that lands in 2028 has to serve the people who are actually there in 2028.

The Queue Runs Well Into 2028

Reveal Day is the first public look, not an award. ICANN said it will publish the list of new gTLD applications at 18:00 UTC on October 7, 2026, including applicant names, primary strings, variants, replacement strings, public application text, and initial contention sets. Until that dump is up, Schneider’s post is the only on-the-record confirmation that.bsky is in the pile.

THE ICANN CLOCK FOR.BSKY

1. October 7, 2026, 18:00 UTC: Reveal Day posts the proceeding applications and first contention sets.
2. October 8, 2026, 00:01 UTC through October 21, 2026, 23:59 UTC: Applicants with an eligible replacement string may switch, and they cannot create new contention by doing it.
3. November 17, 2026: String Confirmation Day publishes the final string list and opens community input.
4. November 27, 2026, 23:59 UTC: Last day to withdraw and still receive a 65 percent refund of the evaluation fee.
5. November 17, 2026 through March 16, 2027: Comments, GAC early warnings, singular/plural notices, and objections run, with an office pause from 1:00 UTC on December 19, 2026, to 16:00 UTC on January 4, 2027.
6. First half of 2027: A prioritization draw sets processing order after a string-evaluation stage ICANN has described as lasting 180 days.

Contracting, onboarding, and delegation come after that. Schneider’s 18 to 24 months is the honest public summary of a queue that still includes objections, possible auctions for contended strings, and a live registry test. Private side deals to settle contention are barred in this round, so a clash over.bsky, if one exists, goes through ICANN’s own process.

Brand owners who see.bsky as too close to a mark, or governments that file an early warning, can still slow a clean application. That is not visible until the public forms are posted. The useful habit on Reveal Day is to read the Bluesky application itself, not the two-sentence post that announced it.

A Profile That Lives on DNS

If the suffix is delegated, the interesting product is not a shorter @. It is a name that already works in the same system as websites, mail, and every other hostname, which is what Graber was driving at in 2023 when she said custom domains borrow the web’s existing proof of control. A personal home page at alice.bsky would be a return to that idea with Bluesky’s brand on the right of the dot.

Until then, the open-web path is the one that already ships. Buy a domain, publish the TXT record, and the handle is yours on any AT Protocol app that respects it. The ICANN bid is a parallel track: a company-run suffix, a $227,000 evaluation, and a calendar that runs into 2028, offered at no sale price to people who never wanted to be their own registrar.

The list at 18:00 UTC will show whether anyone else wants the same four letters. The next 18 to 24 months will show whether Bluesky still wants to operate a registry by the time it is allowed to.