.for
Is .for a real TLD? Who’s applying to run it?
Nobody has applied for .for in its own right, as of 7 October 2026. .TOP Registry named .for as the replacement string of its .lot application.
A preposition TLD built for phrase hacks like vote.for; memorable for campaigns, rarely a serious main address.
campaign and call-to-action marketers, redirect and link-shortener builders, and domain-hack collectors who want a readable verb-plus-".for" phrase; not a namespace a company would choose as its primary identity
No applications recorded for this TLD yet.
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.
Identical bet: a pure English function word with no category, industry or community behind it, so all value sits in the phrase to its left and the registry is wagering that registrants will buy grammar rather than a label they can own.
Another contentless connective whose only use is sentence-completion to the left ("we.are"), meaning it attracts one-off marketing constructions and campaign hacks rather than anyone willing to put a primary, permanent identity on the right-hand side.
Same grammar-as-TLD wager on phrase construction, but a question word carries a built-in use case (instructional and answer content) that a bare preposition lacks, so it has a thinner but real editorial constituency.
What a .for domain is
.for is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. Nobody has applied for .for in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .for domain extension real yet?
.for is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .for domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .for name can only be registered after that, once the string is delegated and its registry opens.
Is .for a real TLD?
Not yet. .for is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .for as part of an application for another string. Every entry on this page links to its source.
- .TOP Registry · first recordedICANN
“LL2624T-T78389 · LeapSense Limited · replacement string of .lot”ICANN
“A2619T-T76756 · Berth Order, LLC · primary · contention set 2026-96 IRI2679T-T36278 · Intercap Registry Inc. · primary · contention set 2026-96 LFGL2683T-T54628 · Link Freedom Group Ltd · primary · contention set 2026-96 LL2624T-T70470 · LeapSense Limited · replacement string of .key · Deactivated NA2626T-T22589 · ShortDot (Ireland) Limited · primary · contention set 2026-96 XI2694T-T41185 · XRegistry Incorporated · primary · contention set 2026-96”ICANN
- Band chosen: 10-29 (vanity/joke/narrow). ".for" is a function word with no category, product, or place behind it; its only natural use is the domain hack, where the second-level label completes a phrase (vote.for, apply.for, care.for, pay.for). By analogy (flagged as analogy), the preposition and verb strings that have found real use are mostly ccTLDs that were repurposed (.to, .by, .is, .me) and carry pre-existing registrar distribution and a long aftermarket history; purpose-built new-gTLD hack strings such as .how and .new have, in my qualitative recollection, stayed niche or depended on the operator's own products, with thin resale demand. The record shows this string as a replacement application from LeapSense Limited whose primary string is .lot, which I read neutrally as a secondary priority for the applicant and so a weaker signal of a committed launch marketing plan; specific volumes, prices and launch dates are unknown. It is not in the 30-49 band because there is no plausible volume driver (no vertical, no geography, no price-led registrar push evident) and the brand signal of a bare preposition is weak outside a slogan; it is not in the 1-9 band because phrase-hack demand is real and recurrent for call-to-action verbs, which would produce a small but genuine set of premium hacks and campaign redirects over the next 5 years. Main market uncertainty: whether phrase hacks on a new gTLD can convert into sustained primary use the way .to did, or remain event-driven novelty as the .how analogy suggests.