.bpce
Is .bpce a real TLD? Who’s applying to run it?
.bpce is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is BPCE.
A private company-name domain: useful to the one group that owns it, but no one else can buy or trade addresses on it.
the applicant organisation itself and its subsidiaries, using the string as a closed corporate namespace for customer-facing and internal services; there is no third-party buyer
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: a merger-born bank initialism that means nothing to the public, applied for by a continental-European retail banking group betting that its corporate letters can anchor the identity of a branch-and-account business.
A three-letter domestic-bank acronym from the same kind of applicant — an incumbent European retail bank whose customers know the letters only as a signboard — so it rests on the same assumption that an opaque initialism carries trust.
Another national retail-banking group's initialism filed as a defensive corporate identity string, with the same buyer (the bank itself, not a market) and the same requirement that letters alone do the identity work.
What a .bpce domain is
.bpce 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 .bpce domain extension real yet?
.bpce 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 .bpce domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .bpce name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .bpce was .bbva, delegated on 27 May 2015.
Is .bpce a real TLD?
Not yet. .bpce is not in the DNS root, so nothing resolves under it. It’s here because .bpce is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- BPCE · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The string matches the sole applicant's name on the record (BPCE, one confirmed application, no contention), so it reads as a dot-brand: a closed namespace where the registry and the only registrant are the same organisation. End-use utility exists for that one owner — by analogy, several financial-sector brand TLDs from the earlier round moved customer login, security and campaign links onto their own string, which gives customers a hard-to-spoof signal, and a banking group has an unusually strong phishing-defence motive to do the same. Resale and aftermarket value, however, are effectively nil: no outside party can register, hold or flip a name, so the TLD itself adds credibility only to its owner. It is not in the 30-49 band because registrations do not happen at volume or on price at all — there is no open market to be thin. It is not in the 1-9 band because, unlike a joke or orphaned string, the best-fit buyer has a realistic and demonstrated (by analogy) primary-identity use. Within the band I score toward the lower-middle: analogous dot-brands have ranged from fully deployed primary identities to dormant, defensive holdings, and the record gives no signal of which this will be. Main market uncertainty: whether the owner actually migrates customer-facing properties onto the string or keeps it as a defensive, redirect-only holding — the former is the only route to real end-use value, and nothing in the verified facts indicates intent either way. All counts and outcomes for analogous TLDs are stated qualitatively from analogy; no figures asserted.