.防伪
Is .防伪 a real TLD? Who’s applying to run it?
Nobody has applied for .防伪 in its own right, as of 7 October 2026. Internet DotTrademark Organisation named .防伪 as the backup string of its .mark application.
A Chinese "anti-counterfeit" label with a narrow verification use; brands may register defensively, few will build on it.
brand owners and product-authentication providers serving Chinese-speaking consumers, mostly registering names to point at verification pages rather than as a main identity
Nobody has applied for .防伪 in its own right.
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.
商标 (trademark) is the same bet as 防伪 (anti-counterfeiting): a Chinese-script abstract function noun sold to brand owners as a protective, authority-backed namespace that nobody makes their primary identity, where value comes from institutional credibility rather than consumer search.
Same bet that the name itself acts as proof — an abstract assurance word whose buyer is an institution or brand wanting the domain to certify that what sits on it is genuine — differing mainly in script and in leaning on policy/vetting rather than goods authentication.
Also a generic purpose noun bought for a defensive job by brand and security vendors rather than as an identity, but it is broader and buyer-agnostic where 防伪 names one narrow verification function for physical-goods makers.
What a .防伪 domain is
.防伪 is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Brand category. Nobody has applied for .防伪 in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .防伪 domain extension real yet?
.防伪 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 .防伪 domain?
You can’t yet. A .防伪 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 .防伪 was .商标, delegated on 22 May 2014.
Is .防伪 a real TLD?
Not yet. .防伪 is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .防伪 as part of an application for another string. Every entry on this page links to its source.
- Internet DotTrademark Organisation · first recordedICANN
“IDOL2621T-T66079 · Internet DotTrademark Organisation Limited · replacement string of .mark”ICANN
- Band chosen: 10-29 (vanity/joke/narrow). The string 防伪 means "anti-counterfeiting" in Chinese: it names a function (verify that a product is genuine) rather than a place, sector, or identity. The verified-facts block records one application, by Internet DotTrademark Organisation Limited, filed as an IDN replacement string tied to the primary application .mark; no demand, pricing, or volume facts are recorded, so all market judgment here is qualitative. By analogy (flagged as analogy): Chinese-script gTLDs built around a single functional or commercial word have tended to collect registrations that are defensive or promotional, with very few sites using the IDN name as their primary web identity; the closest analogy, a Chinese TLD meaning "trademark", has by reputation seen modest uptake concentrated among brand-protection registrants rather than organic business adoption. 防伪 is narrower still: the natural use is a per-brand verification endpoint (brand.防伪) that consumers reach via a label or QR code, which is a real but thin utility and does not confer brand credibility on its own. It is not in the 30-49 band because there is no visible path to volume registrations or a price-led market: the buyer set is bounded to rights-holders with a China-facing authentication need, and the mainland hosting regime for new TLDs (details unknown) tends to slow practical use. It is not in the 1-9 band because a genuine use case exists: counterfeiting is a persistent concern for brands selling in Chinese-speaking markets, and a dedicated verification namespace marketed alongside a trademark-oriented TLD could see a small, steady defensive and functional registrant base over the next 5 years. Main market uncertainty: whether brand-protection programs in Chinese-speaking markets would adopt a domain-based verification address at all, versus staying with app-, platform-, or QR-based authentication that never surfaces a domain name to the consumer.