.fam

Is .fam a real TLD? Who’s applying to run it?

.fam is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are Intercap and ShortDot. XYZ Registry named .fam as a backup string for its .therapy application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.

Application type: GenericCategory: CultureContested · 2
on the record since Sep 8, 2026 · updated Oct 7, 2026
◈AI score
31/ 100
Usable but limited

A niche TLD for family and community sites, fan groups, creators and group chats wanting a short, informal "we're a crew" identity, plus genealogy and family-business pages.

assessed by claude-fable-5-1 · Sep 8, 2026
AI score 31 of 100. .com scores 96, .ai scores 84.
who it’s for

family and community sites, fan groups, creators and group chats wanting a short, informal "we're a crew" identity, plus genealogy and family-business pages

CultureBrandOther
applicants
2 applications · 1 deactivated backup
ShortDotConfirmed

shortdot.bond ↗

One of the 80 strings ShortDot published for the ICANN 2026 round. ShortDot states it has submitted 40 applications, but publishes the 80 strings without revealing which 40 are applications and which 40 are designated replacements. The submission claim is therefore applicant-level, not string-level: nothing in the source says ShortDot applied for THIS string. Catalogued, not announced.

listed in a catalog Sep 8, 2026 · announced Sep 9, 2026 · confirmed by ICANN Oct 7, 2026 · backup .amp

GenericICANN NA2626T-T51374set 2026-80ShortDot (Ireland) Limited ↗
IntercapConfirmed

intercap.inc ↗

confirmed by ICANN Oct 7, 2026 · deactivated backup .gym

GenericICANN IRI2679T-T94602set 2026-80ICANN ↗
backups
XYZ RegistryDeactivated backup

xyz.xyz ↗

Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .therapy application, shown as deactivated: another applicant applied for the same string or named it as a backup

Deactivated backup for .therapyGenericICANN XL2625T-T84804ICANN ↗
closest 2012 bets
3 of 1,408

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.

.familystrong parallel
delegated 2015 · live36,604 domains · May 2026

It is the identical bet in unabbreviated form — an unowned kinship-affinity generic that nobody can claim as a brand, sold to households, family businesses and family-focused orgs who must be persuaded to put personal identity on a non-.com word.

3 applicants contested it · scored 45* in 2012 · run by Bitter Galley, LLC

See .family in Stats
.mommoderate
delegated 2015 · live78,910 domains · May 2026

Same bet in a different register: a short, warm, everyday kinship noun whose value depends on individuals and small family-facing brands adopting it as personal identity rather than on any registry-side rights holder.

3 applicants contested it · scored 25* in 2012 · run by Uniregistry, Corp.

See .mom in Stats
.dadmoderate
delegated 2014 · live3,675 domains · May 2026

Another three-letter kinship word sold on informal personal affinity — the same 'people will name themselves after their family role' wager, with the same dependence on consumer registrants who mostly already have a .com.

uncontested · scored 20* in 2012 · run by Charleston Road Registry Inc.

See .dad in Stats

* A separate 2012-only read, time-locked to what was public that year. Different scale from this page’s score, so the two are not comparable.

What a .fam domain is

.fam is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Culture category. 2 applications for it are on ICANN’s Reveal Day list.

Is the .fam domain extension real yet?

.fam 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 .fam domain?

You can’t yet. A .fam 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 .fam was .family, delegated on 11 August 2015.

Is .fam a real TLD?

Not yet. .fam is not in the DNS root, so nothing resolves under it. It’s here because .fam is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.

history
  1. XYZ Registry · first recordedOct 7, 2026
    ICANN
  2. Intercap · first recordedOct 7, 2026
    ICANN
  3. ShortDot · now confirmedOct 7, 2026

    On the ICANN Reveal Day list, 7 October 2026

    ICANN
  4. ShortDot · now announcedSep 9, 2026

    Founder ruling 2026-09-09: an applicant-level submission claim plus a published string list is an announcement for every listed string, whether primary or designated replacement (LFG, Journey to the West and Aruba filed the same way). ShortDot (Ireland) Limited stated it submitted 40 applications and published the 80 strings on shortdot.bond/80 on 2026-09-08.

  5. ShortDot · first recordedSep 8, 2026
    ShortDot (Ireland) Limited
news & sources
ICANNICANN gTLD application list, 7 October 2026
Oct 7, 2026
“IRI2679T-T94602 · Intercap Registry Inc. · primary · contention set 2026-80 NA2626T-T51374 · ShortDot (Ireland) Limited · primary · contention set 2026-80 XL2625T-T84804 · XYZ.COM LLC · replacement string of .therapy · Deactivated”
ICANN
ICANNICANN Reveal Day list, 7 October 2026
Oct 7, 2026
“IRI2679T-T94602 · Intercap Registry Inc. · primary · contention set 2026-80 NA2626T-T51374 · ShortDot (Ireland) Limited · primary · contention set 2026-80”
ICANN
CatalogShortDot's 80 strings for the ICANN 2026 round
Sep 8, 2026
“ShortDot (Ireland) Limited has submitted 40 applications to ICANN's 2026 New gTLD Program. The 80 strings shown include applied-for and designated replacement strings across ShortDot's 40 ICANN applications, presented without revealing their status or pairing.”
ShortDot (Ireland) Limited
Considering a name on .fam?Appraise a name on this TLD →

This record is corrected in the open. See the changelog and methodology.