New gTLD · delegated 2014-09 · Google Registry

.chrome TLD stats

.chrome held 2 names in December 2025, as Google Registry reported to ICANN; its zone file on 13 Oct 2026 carried 2. 1 registrars held names in it that month; the largest, MarkMonitor Inc., held 50.0%.

2
names, December 2025, registry-reported
2
in the zone file, 13 Oct 2026
1
registrars holding names

Names since general availability, September 2014

Names on the books at the end of each year since general availability, from the registry's monthly reports to ICANN, through May 2026. The marked point is the zone count of 13 Oct 2026, a different count taken on one night.

Year by year since launch, as the registry reported it

In its first year, to August 2015, 0 registrars held 10 or more .chrome names and the largest held 100%; by its eleventh, to August 2025, 0 did and the largest held 50%.

  1. 1 · to Aug 201510100%
  2. 2 · to Aug 201610100%
  3. 3 · to Aug 201710100%
  4. 4 · to Aug 201810100%
  5. 5 · to Aug 20192050%
  6. 6 · to Aug 20202050%
  7. 7 · to Aug 20212050%
  8. 8 · to Aug 20222050%
  9. 9 · to Aug 20232050%
  10. 10 · to Aug 20242050%
  11. 11 · to Aug 20252050%

Year 1 starts at general availability and each year is labelled by the month it ends. Registrars with 10 or more names and the largest registrar's share are read at that month. A year with fewer than nine monthly reports is left blank.

Who sells it

December 2025

MarkMonitor Inc. held 50.0% of .chrome names in December 2025; the largest five together held 50.0%.

  1. MarkMonitor Inc.50.0%
  2. everyone else50.0%

Shares add to 100%. From the registry's report for December 2025.

2026 strings our model compared with it

When we scored the 2026 round, our model listed .chrome among the closest 2012-round TLDs for 7 applied-for strings. No applicant made these comparisons; strong and moderate are how close it judged each match.

Cross-checkThe registry reported 2 names for Dec 2025; the zone on Oct 13, 2026 held 0 more. The two are counted differently and 10 months apart: a registered name that is not delegated never appears in the zone, and a zone file is read on one night, a report at a month's end.

last night, in detail

Oct 13, 2026
What moved · on Oct 13, 2026
entered the zone
0
left it
0
changed nameservers
0
Net
0
Sep 16, 2026 to Oct 13, 2026 · axis starts at the data, not at zero
How the zone is used · 2 names
  • Listed for salemarketplace nameservers00.0%
  • Parkedad-parking or expiry nameservers00.0%
  • In usehosting, registrar or DNS nameservers150.0%
  • Not classifiednameservers we can’t name150.0%

Read from each name’s nameservers on the night shown. Listed and parked are counted separately.

How we classify
A name takes the row its nameservers match on our provider list. Verification nameservers sit beside a name’s other nameservers, so they overlap the rows above: 0.0%. List 2026.09.7+psl4b673689.

Counted from the registry’s own zone file on the night of Oct 13, 2026. A zone count is not domains under management: a registered name that is not delegated never appears in the zone, and a name on hold leaves the zone while it stays registered. The two numbers will not agree, and neither is wrong.

how many names, month by month

to
Dec 2025 to Dec 2025

Names under management at month end, as the registry reported it. Reported to ICANN monthly.

everything else