Stats
New gTLD · delegated 2014-03 · Dot Vegas, Inc.

.vegas TLD stats

.vegas held 11,830 names in August 2025, as Dot Vegas, Inc. reported to ICANN; its zone file on 23 Oct 2026 carried 11,432. 61 registrars held names in it that month; the largest, GoDaddy.com, LLC, held 57.3%.

11,830
names, August 2025, reported to ICANN
11,432
in the zone file, 23 Oct 2026
61
registrars holding names

Names since general availability, August 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 23 Oct 2026, a different count taken on one night.

Year by year since launch, as the registry reported it

In its first year, to July 2015, 37 registrars held 10 or more .vegas names and the largest held 48%; by its eleventh, to July 2025, 42 did and the largest held 57%.

  1. 1 · to Jul 201516,2393748%
  2. 2 · to Jul 201614,8984154%
  3. 3 · to Jul 201717,0023845%
  4. 4 · to Jul 201821,1243839%
  5. 5 · to Jul 201916,7663843%
  6. 6 · to Jul 202014,5354049%
  7. 7 · to Jul 202113,5354249%
  8. 8 · to Jul 202211,8494156%
  9. 9 · to Jul 202313,2724151%
  10. 10 · to Jul 202412,0264256%
  11. 11 · to Jul 202511,8464257%

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

August 2025

GoDaddy.com, LLC held 57.3% of .vegas names in August 2025; the largest five together held 77.6%.

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

2026 strings our model compared with it

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

Cross-checkThe registry reported 11,830 names for Aug 2025; the zone on Oct 23, 2026 held 398 fewer. The two are counted differently and 14 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 23, 2026
What moved · on Oct 23, 2026
entered the zone
+7
left it
−5
changed nameservers
7
Net
+2
Sep 16, 2026 to Oct 23, 2026 · axis starts at the data, not at zero
How the zone is used · 11,432 names
  • Listed for salemarketplace nameservers3773.3%
  • Parkedad-parking or expiry nameservers850.7%
  • In usehosting, registrar or DNS nameservers9,69884.8%
  • Not classifiednameservers we can’t name1,27211.1%

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.5%. List 2026.09.7+psl4b673689.

Counted from the registry’s own zone file on the night of Oct 23, 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
Aug 2025 to Aug 2025

Names under management at month end, as the registry reported it. Reported to ICANN monthly. Sunrise Jun 2014 to Aug 2014; general registration Aug 2014.

everything else