.keep
Is .keep a real TLD? Who’s applying to run it?
.keep is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Google.
A pleasant verb that reads as a product name, not a namespace; few projects would make it their main address.
a brand owner using it for its own note-taking and storage products; if ever opened, hobbyists wanting a keepsake or archive address
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 exactly: a plain everyday English verb in the imperative, owned by nobody and tied to no category, that only means something once a second-level supplies the object — so the registry is selling a usable phrase-ending rather than membership in an industry.
Same one-word, non-category custody/protection bet aimed at whoever wants to promise safekeeping, differing only in being an adjective-state rather than a verb-action, so it reads as a label more than an instruction.
Also an abstract single English word about holding something on someone's behalf with no defining industry, but it carries a fiduciary pull that narrows its likely buyer to finance in a way the target's verb does not.
What a .keep domain is
.keep is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .keep domain extension real yet?
.keep is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .keep domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .keep name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .keep was .save, delegated on 7 June 2016.
Is .keep a real TLD?
Not yet. .keep is not in the DNS root, so nothing resolves under it. It’s here because .keep is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Google · first recordedICANN
“CRRI2564-T80526 · Charleston Road Registry Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/joke/narrow), near its top. The string is a common English verb with warm connotations (storage, archives, keepsakes, collections), which gives it memorability, but a verb TLD only works when the left side completes a phrase (photos.keep, notes.keep), and that pattern has tended to produce shallow, event-driven demand rather than serious primary identities. Analogy, flagged as such: open verb and short-word TLDs from past rounds (such as .click, .link, .work) registered at volume on price and built thin aftermarkets, while the ones that became genuine identities (.app, .page, .new) did so because of a strong category meaning plus operator-driven product tie-ins rather than the verb itself; .keep lacks a clear category anchor. The record shows one confirmed application from Google (legal name Charleston Road Registry Inc.), ICANN application type brand, with no contention; a brand-type application informs adoption likelihood toward operator-internal use, which keeps third-party demand narrow even under the assumption of delegation and general availability. It is not in the 30-49 band because there is no evidence of volume registration demand or a buyer group that would adopt it as a primary identity, and not in the 1-9 band because the word is memorable, pronounceable and plausibly attractive for a small set of storage, archive and collectible projects. Registration volumes, pricing and any launch timing are unknown. Main market uncertainty over the next 5 years: whether a product tie-in (the way some operator-run TLDs gained identity use through app integration) would create real primary-identity demand for .keep, or whether it stays an internal vanity namespace.