.stubhub
Is .stubhub a real TLD? Who’s applying to run it?
.stubhub is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is StubHub, Inc..
A closed brand space for one ticket marketplace: useful to its owner for trusted links, with no market for anyone else.
the applicant itself (a ticket resale marketplace) and its internal teams, using it for brand-controlled addresses such as regional sites, event campaigns and trusted links in customer communications; no outside buyer group exists
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.
Same bet: a coined consumer-marketplace brand owned by a larger group puts its own two-sided buyer/seller platform identity on a dot-brand, so the TLD only works if customers already recognise the brand and the parent keeps routing transaction traffic to it.
Same bet: an invented, single-vertical online shopping brand acquired by a bigger parent, betting its dot-brand carries a consumer transaction destination that lives or dies with the parent's willingness to keep the sub-brand distinct.
Same bet in a different vertical: a compound coined brand for an online booking intermediary that sits between consumers and event/travel inventory, wagering that a mid-size transactional platform brand is strong enough to be its own namespace.
What a .stubhub domain is
.stubhub is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .stubhub domain extension real yet?
.stubhub is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .stubhub domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .stubhub name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .stubhub was .taobao, delegated on 21 January 2016.
Is .stubhub a real TLD?
Not yet. .stubhub is not in the DNS root, so nothing resolves under it. It’s here because .stubhub is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- StubHub, Inc. · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The verified-facts block records a single confirmed application of ICANN type brand by StubHub, Inc., so this is a closed dot-brand: registrations are restricted to the applicant and there is no resale or aftermarket by design. By analogy with the 2012-round dot-brands (flagged as analogy), outcomes split into three patterns: a minority put the space to real use for trusted redirects, campaign addresses or regional sites; a larger group held it dormant as a defensive asset; and a meaningful share were later retired by their owners. Specific counts for those patterns are unknown and not asserted. For a ticket marketplace the end-use case is more credible than for many brands: event and venue names map naturally onto a left-of-dot label, and a namespace only the brand can register has an anti-phishing value for ticket links, a category where lookalike fraud is a known customer-trust problem (qualitative, analogy). It is not in the 30-49 band because there are no registrations at volume or on price, no third-party brand signal, and no aftermarket at all; usable-but-limited presumes an open market, which this is not. It is not in the 1-9 band because there is a realistic, bounded market of one: the applicant has a plausible primary-identity use (secure ticket links, regional and event addresses) over the next 5 years. Main market uncertainty: whether the owner migrates customer-facing or transactional links onto the string rather than holding it dormant, which by analogy with earlier dot-brands is the more common outcome.