.vendor
Is .vendor a real TLD? Who’s applying to run it?
Nobody is chasing .vendor, as of 7 October 2026. One applicant claimed it and is out. We keep the entry on the record either way.
- Journey To The West
A generic B2B word few sellers would brand around; expect cheap, low-stakes registrations and little resale demand.
B2B marketplaces, procurement and vendor-management platforms, and individual sellers or suppliers wanting a role-labeled web address for storefronts or supplier portals
In Journey To The West's published portfolio of 323 strings submitted in the ICANN 2026 round. Their catalog line: “The seller at the other end of the deal.”
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 exactly: an open, singular, generic role-noun for the seller side of a transaction, betting that businesses defined by selling will put their primary identity on the role rather than on their category or brand.
Same B2B procurement-side generic, sold to the same buyer (a company that supplies goods to other companies), but it names the function/goods rather than the actor, so identity sits one step further from the registrant.
Also a generic occupational-role noun whose registrants are intermediaries claiming a trade identity, but it carries a narrower finance/insurance gravity than .vendor's open commercial-seller framing.
What a .vendor domain is
.vendor is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody is chasing .vendor today. The applicants that claimed it are out.
Is the .vendor domain extension real yet?
.vendor is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .vendor domain?
You can’t yet. A .vendor name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .vendor was .dealer, delegated on 24 December 2015.
Is .vendor a real TLD?
Not yet. .vendor is not in the DNS root, so nothing resolves under it. It’s here because an applicant claimed .vendor and is no longer in it. We keep the entry, and every entry on this page links to its source.
- Journey To The West · now abandonedICANN
- Journey To The West · first recordedJourney To The West Corporation
“.vendor · Trade & Logistics · “The seller at the other end of the deal.””Journey To The West Corporation
- I place .vendor in the 10-29 band (upper end). 'Vendor' is a role word businesses are called by others, not a name they brand themselves under, so serious primary-identity use over the next 5 years looks rare; the closest analogies (flagged as analogy) are role/commerce TLDs like .trade, .market, and .jobs, which drew volume mainly on price or stayed narrow corporate utilities with thin aftermarkets despite plausible-sounding use cases. It is not in the 30-49 band because I see no mechanism for sustained volume registrations beyond promotional pricing and no category (marketplaces default to .com or platform subdomains) where it becomes the expected address. It is above the 1-9 band because there is a real, if narrow, functional niche — supplier portals and marketplace seller pages — that could produce steady low-value registrations. The applicant is a Beijing-based portfolio applicant with a published portfolio of 323 submitted strings, which suggests broad catalog economics rather than a dedicated adoption push; my main market uncertainty is whether any procurement or marketplace platform would programmatically issue .vendor addresses to its sellers, which is the one dynamic that could create volume.