.forever
Is .forever a real TLD? Who’s applying to run it?
Nobody has applied for .forever in its own right, as of 7 October 2026. Intercap named .forever as a backup string for its .legacy application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. Deejuu Web Technology Private Limited named .forever as a backup string for its .follow application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A sentimental slogan word: fun for memorials, weddings and keepsakes, but few serious projects would make it their main address.
memorial, remembrance and legacy services, wedding and couple sites, and slogan-style vanity registrants who want a name that reads as a promise
No applications recorded for this TLD yet.
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .follow 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 .legacy 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: an abstract, emotionally loaded English word with no category and no natural registrant class, monetized on sentiment and gift-grade keepsake use (weddings, remembrance, devotion) rather than on any industry putting its primary identity there.
Same bet in structure — a one-word open-ended abstract concept that means something to everyone and nothing to a specific trade, so demand has to be conjured from aspiration and lifestyle branding rather than captured from an existing vertical.
The closest structural twin: a bare adverb of time sold purely on connotation (immediacy, where .forever sells permanence), with no definable applicant pool and success resting on consumers reading the suffix as part of a phrase.
What a .forever domain is
.forever is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. Nobody has applied for .forever in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .forever domain extension real yet?
.forever 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 .forever domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .forever name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .forever was .love, delegated on 2 April 2015.
Is .forever a real TLD?
Not yet. .forever is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .forever as part of an application for another string. Every entry on this page links to its source.
“DWTP2553-T45842 · Deejuu Web Technology Private Limited · replacement string of .follow · Deactivated IRI2679T-T57144 · Intercap Registry Inc. · replacement string of .legacy · Deactivated”ICANN
“IRI2679T-T16795 · Intercap Registry Inc. · replacement string of .url”ICANN
- Band chosen: 10-29 (vanity/narrow), at its upper edge. .forever is a generic English word that works as the tail of a phrase (a name dot forever) rather than as a namespace a project builds under; its natural end uses are memorial and legacy pages, wedding and anniversary sites, keepsake and archival services, and expressive vanity names. The record shows two applications, both deactivated, and both filed as replacement strings for other primaries (.follow and .legacy), which is consistent with the string being seen by applicants as a second-choice sentiment word next to a legacy/remembrance concept rather than a standalone category. By analogy (flagged as analogy), sentiment and phrase-tail TLDs such as .love, .wedding and .family have found steady but small demand, mostly from individuals and small services, with thin aftermarkets and little use as a serious company's primary identity; .forever would likely behave the same way, with occasional spikes around romantic and memorial occasions. Not the band above (30-49) because there is no obvious volume driver beyond deep discounting, the brand signal is emotional rather than credible, and a memorial or wedding platform of any size would still be expected to anchor on an established TLD. Not the band below (1-9) because the word is memorable, globally understood, and does have genuine if narrow end-use fits (remembrance, keepsake, vows) where a dot-forever address is charming enough that some real projects would use it. Main market uncertainty: whether a memorial or digital-legacy operator adopts .forever as a product namespace at scale, which would convert expressive demand into sustained primary-identity use.