.harvest
Is .harvest a real TLD? Who’s applying to run it?
Nobody is chasing .harvest, as of 7 October 2026. One applicant claimed it and is out. We keep the entry on the record either way.
- Journey To The West
A pleasant seasonal word, but few businesses would make .harvest their main web address; expect mostly hobby and themed sites.
farm brands, agtech startups, food and CSA businesses, and the many organizations named "Harvest" (churches, apps, festivals) wanting a name-match or themed address
In Journey To The West's published portfolio of 323 strings submitted in the ICANN 2026 round. Their catalog line: “The reward of patience and season.”
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 plain English agricultural noun sold as an open generic to growers, ag-supply firms and food producers, where success depends on an industry with thin digital-identity spend re-badging itself onto a semantic TLD.
Same portfolio-generic play - an everyday cultivation noun whose registrants would be long-tail trade and hobby businesses rather than one dominant category owner, so it lives on registration volume, not on an anchor tenant.
Closest match for the evocative-promise half of the bet: a food-and-growing word that signals a value rather than naming a business type, so it draws marketers and cause branding, with the same risk that nobody makes it their primary identity.
What a .harvest domain is
.harvest is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody is chasing .harvest today. The applicants that claimed it are out.
Is the .harvest domain extension real yet?
.harvest 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 .harvest domain?
You can’t yet. A .harvest name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .harvest was .farm, delegated on 28 December 2013.
Is .harvest a real TLD?
Not yet. .harvest is not in the DNS root, so nothing resolves under it. It’s here because an applicant claimed .harvest and is no longer in it. We keep the entry, and every entry on this page links to its source.
- Journey To The West · now abandonedICANN
- Journey To The West · first recordedJourney To The West Corporation
“.harvest · Nature & Geography · “The reward of patience and season.””Journey To The West Corporation
- I place .harvest in the 10-29 band (vanity/narrow). It is not in the 30-49 band because, by analogy with existing agricultural and food dictionary TLDs such as .farm and .organic, semantic suffixes in this sector have shown thin uptake as primary identities, and .harvest is semantically narrower still — an event/verb rather than a place or business category, so 'name.harvest' rarely reads as a natural identity. It is above the 1-9 band because a real, if shallow, market exists: many entities are literally named 'Harvest' (churches, software brands, festivals), plus seasonal and farm-to-table marketing campaigns, which by analogy with other evocative-word TLDs supports steady low-volume registrations. The applicant is a portfolio filer with 323 submitted strings, which I read neutrally as suggesting standardized registry operations rather than dedicated category marketing, tempering adoption expectations. Main market uncertainty: whether the sizable population of 'Harvest'-named organizations treats an exact-match TLD as a brand upgrade or ignores it in favor of established extensions.