.force
Is .force a real TLD? Who’s applying to run it?
.force is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are GoDaddy Registry and Salesforce.
A strong, short English word with domain-hack appeal, but no category treats it as a default identity.
domain-hack buyers and small brands wanting a punchy suffix (task.force, work.force, brute.force), plus security, fitness, gaming and defense-adjacent projects seeking an energetic name
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.
Both are abstract aspirational English nouns with no natural registrant community, so the bet is identical: sell an evocative capability word broadly and let each registrant supply the meaning in front of it.
Same bet on a short, common, semantically open noun that works as a suffix for almost any venture, succeeding on the sound of the phrase rather than on owning a defined category of registrants.
Another single-syllable abstract word applied for as a brandable open string whose value rests on connotation and memorability, not on a vertical of buyers who would already describe themselves with it.
What a .force domain is
.force is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. 2 applications for it are on ICANN’s Reveal Day list.
Is the .force domain extension real yet?
.force 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 .force domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .force name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .force was .vision, delegated on 11 February 2014.
Is .force a real TLD?
Not yet. .force is not in the DNS root, so nothing resolves under it. It’s here because .force is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“CRM2628T-T77764 · Salesforce, Inc. · primary · contention set 2026-88 NA2631T-T11642 · Registry Services, LLC · primary · contention set 2026-88”ICANN
“LFGL2683T-T82030 · Link Freedom Group Ltd · primary NA2631T-T80151 · Registry Services, LLC · replacement string of .all · Deactivated”ICANN
- Band chosen: usable but limited (30-49), at its low edge. The string is a short, common English noun with several readings (power, military force, workforce, task force, and a well-known science-fiction association), and it composes naturally as the right-hand half of compound words, which gives it domain-hack appeal. That keeps it out of the vanity/joke band (10-29): some registrants will plausibly adopt a .force name as a real primary identity, and the word carries a credible, energetic brand feel rather than reading as a gag. It does not reach the strong-niche band (50-69) because no identifiable industry or community treats 'force' as its namespace; demand would be scattered across unrelated uses, and adoption would need explaining to customers and investors. By analogy (flagged as analogy), open-registration single-word suffixes with broad connotation but no category anchor, such as evocative lifestyle or attitude strings launched in the earlier round, tended to see initial registration bursts driven by price and novelty, with thin aftermarket resale and few serious primary-identity sites; that pattern is the base case here. Two applicants are confirmed on the record: Salesforce, Inc. and Registry Services, LLC, both in ICANN contention set 2026-88. Neutrally, Salesforce is an operator whose own brand contains the string, and Registry Services, LLC is a registry operator; this suggests the two applications may envision different operating models. The main market uncertainty, independent of delegation, is which model the delegated TLD actually runs under: an open general-availability namespace sold through registrars versus a tightly controlled namespace used mainly by one organization and its ecosystem. Under the open model the score above holds; under a controlled model the string could become a meaningful identity inside one commercial ecosystem (closer to a brand-anchored niche) while being largely unavailable to the general buyer. Secondary uncertainty: whether brand association with the existing 'force' naming in the CRM ecosystem helps (familiarity) or hurts (confusion, trademark friction) independent registrants. Registration counts, pricing, and launch dates are unknown.