.btw

Is .btw a real TLD? Who’s applying to run it?

.btw is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Suffix Inc..

Culture
on the record since Oct 7, 2026 · updated Oct 7, 2026
◈AI score
19/ 100
Vanity and narrow

A chat-slang ending that is fun to say but hard to build a serious business or brand on.

assessed by claude-fable-5-1 · Oct 7, 2026
AI score 19 of 100. .com scores 96, .ai scores 84.
who it’s for

casual creators, newsletter and side-project owners, and people buying a punny or conversational name for a personal site, link-in-bio page, or short-lived campaign

CultureOtherBrand
applicants
1 application
Suffix Inc.Confirmed

suffix.domains ↗

confirmed by ICANN Oct 7, 2026 · deactivated backup .auth

GenericICANN SI2639T-T50366ICANN ↗
closest 2012 bets
3 of 1,408

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.

.lolstrong parallel
delegated 2015 · live948,744 domains · May 2026

Same bet exactly: a chat-born three-letter initialism with no category meaning, sold on the assumption that internet-native people will put casual, expressive identity on a phrase they already type daily rather than on a descriptive noun.

2 applicants contested it · scored 35* in 2012 · run by Uniregistry, Corp.

See .lol in Stats
.fyistrong parallel
delegated 2015 · live71,124 domains · May 2026

The closest structural twin — an initialism of a short discourse-marker phrase that prefaces a remark, carrying no industry, product or geography, so its value rests entirely on universal shorthand recognition and brevity.

2 applicants contested it · scored 25* in 2012 · run by Silver Tigers, LLC

See .fyi in Stats
.wtfmoderate
delegated 2014 · live41,108 domains · May 2026

Also a conversational initialism bought for recognition rather than meaning, but its bet leans on shock/novelty appeal and a narrower expressive use, where .btw (like .fyi) bets on an everyday, inoffensive connective anyone would attach their name to.

uncontested · scored 30* in 2012 · run by Hidden Way, LLC

See .wtf in Stats

* A separate 2012-only read, time-locked to what was public that year. Different scale from this page’s score, so the two are not comparable.

What a .btw domain is

.btw is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. One application for it is on ICANN’s Reveal Day list.

Is the .btw domain extension real yet?

.btw 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 .btw domain?

You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .btw name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .btw was .lol, delegated on 2 May 2015.

Is .btw a real TLD?

Not yet. .btw is not in the DNS root, so nothing resolves under it. It’s here because .btw is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.

history
  1. Suffix Inc. · first recordedOct 7, 2026
    ICANN
news & sources
ICANNICANN Reveal Day list, 7 October 2026
Oct 7, 2026
“SI2639T-T50366 · Suffix Inc. · primary”
ICANN
about Suffix Inc.
ICANNICANN gTLD application list, 7 October 2026
Oct 7, 2026
“LFGL2683T-T12771 · Link Freedom Group Ltd · primary SI2639T-T84933 · Suffix Inc. · replacement string of .rep · Deactivated”
ICANN
about Suffix Inc.
Catalogsuffix.domains: published catalog of TLD strings
“Catalog lists: .asap .create .future .lfg .mvp .out .pal .planet .research .share .tag .this .visit”
Suffix Inc.
about Suffix Inc.
AnnouncementFounder announcement of Suffix Inc.'s ICANN 2026 TLD applications
Aug 16, 2026
Suffix Inc. founder (@t0m_3d) on X
Considering a name on .btw?Appraise a name on this TLD →

This record is corrected in the open. See the changelog and methodology.