.dpp
Is .dpp a real TLD? Who’s applying to run it?
.dpp is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is CORE Association.
A technical namespace for digital product passports; useful as machine-readable plumbing, rarely a brand anyone promotes.
manufacturers, brands and identifier/compliance service providers who need resolvable addresses for digital product passports and product traceability records
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 as .dpp: a namespace whose only value is asserting verified conformance to an externally defined standard, so the registry succeeds or fails on whether a recognised certifying authority backs it and gates who may register — not on consumer appeal of the word.
Like .dpp, a short acronym whose entire category was conjured by a regulatory regime rather than by language, sold to a narrow set of institutions that qualify under that regime, so the bet is that regulated entities will adopt a dedicated compliance-signalling namespace.
Shares the shape of a standards-and-plumbing acronym with no consumer resonance — identity goes on records and systems rather than on a company's front door — but it is a naming-layer technicality, not a mandated per-object compliance artifact, and nothing in 2012 corresponds to a legally required product-level data record.
What a .dpp domain is
.dpp is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Infrastructure. One application for it is on ICANN’s Reveal Day list.
Is the .dpp domain extension real yet?
.dpp 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 .dpp domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .dpp name can only be registered after that, once the string is delegated and its registry opens.
Is .dpp a real TLD?
Not yet. .dpp is not in the DNS root, so nothing resolves under it. It’s here because .dpp is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- CORE Association · first recordedICANN
“CA2682T-T18182 · CORE Association · replacement string of .src · Deactivated HS2699T-T37790 · Heir Superiority, LLC · primary IRI2679T-T97493 · Intercap Registry Inc. · replacement string of .brain · Deactivated LFGL2683T-T12896 · Link Freedom Group Ltd · replacement string of .btc · Deactivated RTIS2674T-T18686 · Radix Technologies Inc SEZC · replacement string of .neo · Deactivated XL2625T-T65446 · XYZ.COM LLC · replacement string of .hvac · Deactivated”ICANN
- The string reads most naturally as 'digital product passport', the product-traceability concept tied to European sustainability and circular-economy rules, which gives it a plausible end-use as a resolver namespace (product identifiers resolving to passport data) rather than as a human-facing brand. I place it in the 30-49 'usable but limited' band: registrations could happen at volume if regulators, standards bodies or large manufacturers adopt it as an addressing convention, and that would give it genuine utility, but even then the TLD would be invisible plumbing with a weak brand signal and a thin aftermarket, since nobody competes for memorable passport addresses. It is not in the 50-69 band because there is no evidence of organic demand for .dpp as a primary identity; by analogy (flagged as analogy), purpose-built infrastructure strings such as .onion-style or identifier-resolution namespaces earn use without earning aftermarket value, and compliance-driven namespaces historically see uptake only when mandated. It is not in the 10-29 band because, unlike a vanity or joke string, it maps to a concrete, growing regulatory and supply-chain workload where a dedicated, policy-governed namespace could become a serious default for machine-readable identifiers. The record shows one confirmed application by CORE Association, a registry operator with prior TLD experience, which supports delivery of a governed, standards-oriented space but says nothing about buyer demand. Main market uncertainty: whether passport identifiers will resolve through a DNS namespace at all, versus through existing identifier schemes and QR/web links on ordinary domains, which would leave .dpp with little to address.