.fitbit
Is .fitbit a real TLD? Who’s applying to run it?
.fitbit is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A brand-name TLD: useful only to the brand that runs it, with no open market for anyone else to buy or resell an address.
the brand owner's own product, support and marketing teams, for first-party addresses; not open to outside registrants
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.
Same bet: a single consumer-hardware company whose whole identity is one short repurposed English word worn on the body, applying to fence a namespace whose only value is the brand's cultural following rather than any category meaning.
Same bet in kind — an invented, dictionary-meaningless name for a consumer gadget line applying for its own string — but it is a product sub-brand of a conglomerate rather than the company's entire corporate identity.
Also a one-device consumer product brand built from an ordinary English word, betting the device's install base makes the string meaningful, though it answers to a parent whose own corporate string was applied for separately.
What a .fitbit domain is
.fitbit is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .fitbit domain extension real yet?
.fitbit 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 .fitbit domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .fitbit name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .fitbit was .beats, delegated on 3 November 2015.
Is .fitbit a real TLD?
Not yet. .fitbit is not in the DNS root, so nothing resolves under it. It’s here because .fitbit is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T35903 · Charleston Road Registry Inc. · primary”ICANN
- The string .fitbit matches a consumer fitness-wearable brand name, and the single recorded applicant is Charleston Road Registry Inc. (status: confirmed), with no category tag on the record. I place it in the 1-9 band (no realistic market): a dot-brand of this kind is, by analogy with earlier single-registrant brand TLDs such as .google, .youtube or .bmw, operated for the owner's own addresses and not sold to third parties, so there is no buyer group, no aftermarket, and no third-party primary-identity use over the next 5 years. It is not in the 10-29 band because that band assumes some outside registrations (vanity or event-driven); a closed brand string has none, and whatever utility exists accrues to one organisation rather than to 'a buyer'. It is not lower than 7 because, again by analogy with brand TLDs that have been put to first-party use (short redirect or campaign addresses under a brand string), there is modest internal utility and a credible trust signal for the brand's own services, which is more than a dead string. Main market uncertainty: whether the operator actually routes meaningful first-party traffic through the string or leaves it defensively idle, which by analogy is the most common outcome for brand TLDs; that does not change the third-party market (none) but moves the score within this band.