.母婴

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

Nobody is chasing .母婴, as of 7 October 2026. One applicant claimed it and is out. We keep the entry on the record either way.

Commerce
  • Journey To The WestAbandoned
on the record since Aug 17, 2026 · updated Oct 7, 2026
◈AI score
15/ 100
Vanity and narrow

A Chinese web address for mother-and-baby brands; the market is huge but shops there live in apps, not on niche domains.

assessed by claude-fable-5 · Aug 17, 2026
AI score 15 of 100. .com scores 96, .ai scores 84.
who it’s for

chinese-language maternity and infant-care brands, mother-baby retail chains, and parenting content platforms wanting a category-labeled Chinese-script address

CommerceCultureBrand
applicants
0 applications · 1 abandoned claim
Aug 17, 2026

xiyou.domains ↗

In Journey To The West's published portfolio of 323 strings submitted in the ICANN 2026 round; a Chinese-script IDN (“mother & baby”, A-label xn--71sp71b). Their catalog line: “Everything for the newest members of the family.”

announced Aug 17, 2026 · abandoned Oct 7, 2026

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.

.babystrong parallel
delegated 2016 · live55,490 domains · May 2026

母婴 ("mother-and-infant") is the same bet as .baby — an open generic consumer-category noun whose registrants are the brands, retailers and content sites of the maternity/infant market putting their primary identity on the category word itself.

6 applicants contested it · scored 48* in 2012 · run by Johnson & Johnson Services, Inc.

See .baby in Stats
.珠宝moderate
delegated 2015 · later pulled2 domains · Jun 2020

Same structural bet in the same script and market: a Chinese-language generic merchandise-vertical noun sold to that vertical's merchants, where value depends on Chinese-script navigation habits rather than on any brand or community.

uncontested · scored 34* in 2012 · run by Richemont DNS Inc.

See .珠宝 in Stats
.家電moderate
delegated 2016 · live103 domains · May 2026

Another CJK-script generic retail product-category string aimed at the shop-by-aisle consumer commerce vertical, needing the same thing to be true — that shoppers and sellers in that market treat a category word as a credible address.

uncontested · scored 30* in 2012 · run by Amazon EU S.à r.l.

See .家電 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 .母婴 domain is

.母婴 is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody is chasing .母婴 today. The applicants that claimed it are out.

Is the .母婴 domain extension real yet?

.母婴 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 .母婴 domain?

You can’t yet. A .母婴 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 .母婴 was .baby, delegated on 8 April 2016.

Is .母婴 a real TLD?

Not yet. .母婴 is not in the DNS root, so nothing resolves under it. It’s here because an applicant claimed .母婴 and is no longer in it. We keep the entry, and every entry on this page links to its source.

history
  1. Journey To The West · now abandonedOct 7, 2026

    Announced, but not on the ICANN Reveal Day list, 7 October 2026

    ICANN
  2. Journey To The West · first recordedAug 17, 2026
    Journey To The West Corporation
news & sources
ICANNICANN Reveal Day list, 7 October 2026
Oct 7, 2026
ICANN
Announcementxiyou.domains: published portfolio of 323 submitted gTLD applications
“.母婴 (mother & baby) · Consumer Goods · “Everything for the newest members of the family.””
Journey To The West Corporation
Considering a name on .母婴?Appraise a name on this TLD →

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