.xpi
Is .xpi a real TLD? Who’s applying to run it?
Nobody has applied for .xpi in its own right, as of 7 October 2026. Pi Network named .xpi as the replacement string of its .pinet application.
A ticker-style string for one crypto community; little meaning outside it, so demand is narrow and tied to that network's fortunes.
participants, app builders and promoters inside the Pi Network ecosystem who want an address that signals the token or network
No applications recorded for this TLD yet.
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 proprietary file-extension acronym that is noise to the general public but instantly legible to the one software trade that works in the format, so the namespace only works if its format steward can convert insider recognition into identity.
Also a vendor-owned file-extension token taken to registry as a namespace, but it doubles as a plain English word with far broader consumer familiarity, giving it a mainstream fallback the target's opaque three letters do not have.
Same single-steward, developer-ecosystem wager — a non-descriptive technical name pitched as the namespace for the extension/plugin community around it — though it is a famous platform brand rather than an unpronounceable artifact extension.
What a .xpi domain is
.xpi is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Crypto. Nobody has applied for .xpi in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .xpi domain extension real yet?
.xpi 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 .xpi domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .xpi name can only be registered after that, once the string is delegated and its registry opens.
Is .xpi a real TLD?
Not yet. .xpi is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .xpi as part of an application for another string. Every entry on this page links to its source.
- Pi Network · first recordedICANN
“PCC2647T-T24976 · Pi Community Company · replacement string of .pinet”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified facts show a single standard (not brand) application from Pi Network, filed as a replacement string for its primary application .pinet; no category tag, no contention. The string reads as a ticker-style label (x + pi) whose meaning is clear only to people already inside one crypto network; to anyone else it is three opaque letters, and in some technical circles the same letters are associated with a browser-extension file format, which muddies rather than helps the signal. Why not 30-49: a 'usable but limited' TLD needs registrations at volume or on price with at least some generic readability; .xpi has no generic reading, and demand would be almost entirely event-driven, rising and falling with that one network's activity rather than with any broad use case. Why not 1-9: a live ecosystem of participants and app builders exists who might plausibly want a network-branded address, so some realistic, if shallow, market exists. By analogy (flagged as analogy), single-ecosystem crypto namespaces outside the ICANN root have seen bursts of speculative registration followed by weak primary-identity use and thin resale, and ICANN-root strings with meaning confined to one community have generally stayed small; I expect a similar pattern here. The .pinet primary suggests the applicant's own preferred identity is elsewhere, so .xpi may serve as a secondary or ticker-flavoured namespace at best. Main market uncertainty: whether the operator ties .xpi addresses to in-network wallet or app identity (which would create captive utility demand) or sells it as an ordinary open TLD (where it would compete on price with far more readable strings and struggle).