.end
Is .end a real TLD? Who’s applying to run it?
Nobody has applied for .end in its own right, as of 8 October 2026. Identity Digital named .end as a backup string for six of its applications: .clean, .artist, .transport, .retail, .mail and .collection. ICANN deactivated those backups, because another applicant applied for the same string or named it as a backup. Link Freedom Group named .end as a backup string for its .way application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A wordplay domain: gems like week.end or fri.end are fun, but few serious projects would make .end their main web address.
wordplay and brand-hack buyers chasing strings like week.end, leg.end, fri.end, back.end or front.end, plus lifestyle and travel storytellers drawn to the 'where journeys end' framing
Nobody has applied for .end in its own right.
In LFG's published list of 300+ strings submitted before the ICANN window closed on 2026-08-12. Their catalog tagline: “Where journeys end and stories begin.”
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .collection application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .mail application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .retail application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .transport application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .artist application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .clean application, shown as deactivated: another applicant applied for the same string or named it as a backup
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 bare monosyllabic abstract English concept-word with no industry that owns it, so its value rests entirely on wordplay/right-of-dot phrasing and generic-concept branding rather than on any identifiable class of primary registrant.
Also a completion word doing double duty as noun and verb, sold on evocative phrasing rather than category membership, though it leans slightly harder on a recognizable use-case (races, coatings) than the fully abstract .end does.
Another short, ownerless absolute-concept word whose registrant base is speculative and phrase-driven — nobody's profession, product category, or community is named by it, so it must manufacture demand from meaning alone.
What a .end domain is
.end is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Culture category. Nobody has applied for .end in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .end domain extension real yet?
.end 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 .end domain?
You can’t yet. A .end 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 .end was .final, delegated on 26 September 2015.
Is .end a real TLD?
Not yet. .end is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .end as part of an application for another string. Every entry on this page links to its source.
- Identity Digital · fact correctedICANN
- Identity Digital · first recordedICANN
- Identity Digital · first recordedICANN
- Identity Digital · first recordedICANN
- Identity Digital · first recordedICANN
- Identity Digital · first recordedICANN
- Identity Digital · first recordedICANN
- Link Freedom Group · now deactivated backupICANN
- Link Freedom Group · now abandonedICANN
- Link Freedom Group · first recordedLink Freedom Group
“LFGL2683T-T10634 · Link Freedom Group Ltd · replacement string of .way · Deactivated MH2645T-T12650 · Mystic Hammer, LLC · replacement string of .collection · Deactivated MH2645T-T20569 · Mystic Hammer, LLC · replacement string of .mail · Deactivated MH2645T-T28488 · Mystic Hammer, LLC · replacement string of .retail · Deactivated MH2645T-T36407 · Mystic Hammer, LLC · replacement string of .transport · Deactivated MH2645T-T78893 · Mystic Hammer, LLC · replacement string of .artist · Deactivated MH2645T-T94731 · Mystic Hammer, LLC · replacement string of .clean · Deactivated”ICANN
“.end · Lifestyle · “Where journeys end and stories begin.””Link Freedom Group
- I place .end in the 10-29 vanity/narrow band. It is not in the 30-49 band because the string has weak standalone commercial semantics; 'end' reads as closure or termination, which is an awkward or even negative signal for most businesses, so I expect neither volume registrations nor a broad price-driven market, and primary-identity use should stay rare over the next 5 years. It is not in the 1-9 band because a genuine, if shallow, market exists: .end is one of the stronger domain-hack suffixes in English, completing common words (week.end, leg.end, fri.end, div.end) and developer terms (back.end, front.end), and by analogy with other hack-friendly suffix TLDs, a small set of exact-word hacks tends to attract real registrations and some aftermarket interest while the long tail languishes; that analogy is inference, not verified data. The applicant, Link Freedom Group, filed more than 300 strings in the ICANN 2026 round and lists .end under 'Lifestyle' with the tagline 'Where journeys end and stories begin.', which suggests a portfolio play where per-string marketing attention may be spread thin, tempering adoption likelihood; that is a neutral read of verified facts. My main market uncertainty is depth of the hack market: whether demand extends meaningfully beyond a few dozen exact-word strings into anything resembling sustained category use, or collapses to a handful of premium names. Renewal behavior on hack-driven TLDs is historically uneven, and I judge that from analogy rather than data.