.wedding TLD stats

• Run by GoDaddy Registry
• Our model compares it with 2 strings in the 2026 round

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.

In its first year, to March 2016, 43 registrars held 10 or more .wedding names and the largest held 27%; by its eleventh, to March 2026, 54 did and the largest held 22%.

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.

eNom, LLC held 21.1% of .wedding names in May 2026; the largest five together held 64.6%.

Shares add to 100%. From the registry's report for May 2026.

When we scored the 2026 round, our model listed .wedding 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.

• Strong (1):.xn--h1sq23e
• Moderate (1):.knot

Cross-checkThe registry reported 12,292 names for Jun 2026; the zone on Oct 23, 2026 held 94 more. The two are counted differently and 4 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.

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.

Names under management at month end, as the registry reported it. Reported to ICANN monthly. Dashed months are third-party estimates. Sunrise Jan 2015 to Mar 2015; general registration Apr 2015.