New gTLD · delegated 2015-06 · Google Registry

.play TLD stats

.play held 6 names in June 2025, as Google Registry reported to ICANN; its zone file on 13 Oct 2026 carried 5.

6
names, June 2025, registry-reported
5
in the zone file, 13 Oct 2026

2026 strings our model compared with it

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

Cross-checkThe registry reported 6 names for Jun 2025; the zone on Oct 13, 2026 held 1 fewer. The two are counted differently and 16 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 · 5 names
  • Listed for salemarketplace nameservers00.0%
  • Parkedad-parking or expiry nameservers00.0%
  • In usehosting, registrar or DNS nameservers480.0%
  • Not classifiednameservers we can’t name120.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
Jun 2025 to Jun 2025

Names under management at month end, as the registry reported it. Reported to ICANN monthly. Sunrise Jan 2026 to Mar 2026; general registration Mar 2026.

everything else