.calendar
Is .calendar a real TLD? Who’s applying to run it?
Nobody has applied for .calendar in its own right, as of 8 October 2026. Identity Digital named .calendar as a backup string for its .pop application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. Identity Digital named .calendar as a backup string for its .gig application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. Intercap named .calendar as a backup string for its .platform application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A plain utility word that suits scheduling tools and public calendars, but few serious projects would make it their main address.
scheduling and booking software, event organizers, and teams or communities publishing a public calendar as a secondary or redirect address
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 .platform 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 .gig 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 .pop 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: take the plain everyday noun for a universal productivity utility and run it as that function's namespace, which only pays off if an operator can make a generic word mean its product rather than the object everyone already has.
Same bet on a one-word generic name for a core personal-information-management function, with the same buyer (a platform or SaaS operator putting its primary identity there) and the same risk that the word is too generally useful to belong to anyone.
Same class of string and same logic — a common noun for an everyday digital function rather than a brand or a community name — differing only in that messaging has a much broader pool of would-be registrants than scheduling does.
What a .calendar domain is
.calendar is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .calendar in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .calendar domain extension real yet?
.calendar 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 .calendar domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .calendar name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .calendar was .docs, delegated on 18 December 2014.
Is .calendar a real TLD?
Not yet. .calendar is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .calendar as part of an application for another string. Every entry on this page links to its source.
“IRI2679T-T25468 · Intercap Registry Inc. · replacement string of .platform · Deactivated VC2665T-T32637 · Vanity Check, LLC · replacement string of .gig · Deactivated VC2665T-T57535 · Vanity Check, LLC · replacement string of .pop · Deactivated”ICANN
“IRI2679T-T16795 · Intercap Registry Inc. · replacement string of .url”ICANN
- Band chosen: 30-49, usable but limited, at its low edge. The string is a common English noun naming a feature rather than a category of business, so its best-fit use is functional: a scheduling or booking product, an event organizer, or a company publishing its public calendar at a memorable secondary address. By analogy (flagged as analogy) to generic utility-noun TLDs such as .events, .today and .link, demand on such strings has tended to come from redirect and side-project use rather than from projects adopting the TLD as their primary identity, and aftermarket activity on them has been thin. It is not in the 50-69 band because there is no identifiable buyer group for whom a .calendar address is a natural primary identity needing only a short explanation; it is not in the 10-29 band because scheduling software is a real and durable product category and the word reads as a legitimate utility rather than a joke or event-driven novelty. The record shows two standard applications, both deactivated and both filed as replacement strings for other primary strings, which I treat neutrally as a signal of limited commercial conviction rather than as a judgment on the applicants. Main market uncertainty: whether scheduling and booking vendors would adopt brand.calendar-style addresses at volume as a shareable link convention, which would lift this toward the middle of the band; the next-5-year figures for registrations and aftermarket prices on comparable utility-noun TLDs are unknown to me and I assert none.