.cnpassurances
Is .cnpassurances a real TLD? Who’s applying to run it?
Nobody has applied for .cnpassurances in its own right, as of 7 October 2026. CNP ASSURANCES named .cnpassurances as the replacement string of its .cnp application.
A single-company brand address: useful only to CNP Assurances itself, with no public registrations or resale market.
the applying insurer and its own group entities, for corporate web, customer-portal and campaign addresses under its own name; nobody else can buy one
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: an incumbent insurance carrier putting its full corporate name — brand token plus the category word "insurance"/"assurances" — on a dot-brand it must fund and populate itself, with no public registration demand to rely on.
Same bet again: a carrier's legal entity name (opaque brand token + category noun) as a closed namespace whose only value is channel control over its own policy and agent properties, not generic category traffic.
Also an insurer's company name fused to its product word, so the string only reads as a brand to people who already know the carrier — but the brand token is a real English word, so it carries some standalone meaning that an acronym-led string like the target does not.
What a .cnpassurances domain is
.cnpassurances is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. Nobody has applied for .cnpassurances in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .cnpassurances domain extension real yet?
.cnpassurances 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 .cnpassurances domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .cnpassurances name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .cnpassurances was .travelersinsurance, delegated on 15 December 2015.
Is .cnpassurances a real TLD?
Not yet. .cnpassurances is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .cnpassurances as part of an application for another string. Every entry on this page links to its source.
- CNP ASSURANCES · first recordedICANN
“CA2616T-T99380 · CNP ASSURANCES · replacement string of .cnp”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified-facts block records a single application by CNP ASSURANCES, status "replacement", with the applicant's primary string recorded as .cnp; contention count on the record is 0 and no category tag is recorded. The string is the applicant's full corporate name, so by analogy with the 2012-round dot-brand TLDs run by banks and insurers (analogy, outcomes stated qualitatively) this is a closed namespace: registrations go only to the brand owner, there is no third-party demand and no aftermarket, which rules out the 30-49 band (that band needs volume or price-driven public registrations). It sits above the 1-9 band because a large financial-services brand has a genuine, if modest, primary-identity use: by analogy with the subset of 2012-round financial dot-brands that moved customer or corporate sites onto their own TLD, a trust-signalling address under a name the company fully controls is a real end-use for anti-phishing and campaign purposes over the next 5 years. The string is long, and the record shows it as a replacement for a shorter primary string, so the brand's own use may lean on the shorter companion address if that one proceeds; this is an inference from the record, not a judgment about the applicant. Main market uncertainty: whether the insurer actually migrates customer-facing properties onto the TLD or keeps it defensive, which by analogy with 2012-round brand TLDs is what separates an actively used dot-brand from a dormant one.