.tom
Is .tom a real TLD? Who’s applying to run it?
Nobody has applied for .tom in its own right, as of 7 October 2026. Suffix Inc. named .tom as the replacement string of its .lfg application.
A first-name TLD: fun for people called Tom and a few word-ending hacks, but rarely a serious project's main address.
people named Tom and small Tom-branded businesses wanting a personal or playful web address, plus hack-hunters after word endings like cus.tom or phan.tom
No applications recorded for this TLD yet.
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 common personal name opened as a namespace so that the many thousands of unaffiliated people who share it buy their own name as identity, with the registry's whole business resting on name-frequency rather than on any single owner's brand.
Same string type — an ordinary Western given name — but the bet runs the other way, with one organisation putting its single corporate identity on the name instead of selling it to everyone who answers to it.
Shares the personal-identity-of-an-individual buyer and the short-friendly-word feel, but it is a role anyone can claim rather than a name a fixed population already owns, so the demand pool is defined by self-description, not by registration records.
What a .tom domain is
.tom 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 .tom in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .tom domain extension real yet?
.tom 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 .tom domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .tom name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .tom was .kim, delegated on 23 January 2014.
Is .tom a real TLD?
Not yet. .tom is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .tom as part of an application for another string. Every entry on this page links to its source.
- Suffix Inc. · first recordedICANN
“SI2639T-T89961 · Suffix Inc. · replacement string of .lfg”ICANN
“LFGL2683T-T12771 · Link Freedom Group Ltd · primary SI2639T-T84933 · Suffix Inc. · replacement string of .rep · Deactivated”ICANN
“Catalog lists: .asap .create .future .lfg .mvp .out .pal .planet .research .share .tag .this .visit”Suffix Inc.
- Band chosen: 10-29 (vanity/narrow). .tom is a given name, so its natural buyers are individuals and small businesses carrying that name, plus a short list of English words ending in -tom usable as domain hacks (custom, phantom, bottom, atom, symptom). By analogy (flagged as analogy) with given-name and family-role gTLDs from the prior round, such strings have tended to attract a small vanity base and a trickle of hack registrations rather than sustained primary-identity use by serious projects, and their aftermarkets have stayed thin. It is not in the 30-49 band because there is no volume driver: no category of business describes itself as 'tom', no pricing-led mass registration dynamic is evident, and the brand signal a .tom address carries is personal rather than professional. It is not in the 1-9 band because a real, if shallow, market exists: a common first name has a built-in audience, a handful of word-ending hacks is a known narrow driver on other TLDs, and Tom-named businesses could plausibly adopt it. On the record this is a replacement-string application by Suffix Inc. whose primary string is .lfg, with zero known contention; that is stated neutrally and only suggests the operator's commitment to this specific string is secondary, which modestly lowers the odds of heavy marketing behind it. Main market uncertainty: whether the operator positions .tom as a cheap open personal-name namespace (volume but no brand value) or as a premium hack/brand namespace (few sales, slightly stronger aftermarket); either way the ceiling over the next 5 years looks like the upper part of this band at most.