.daiwa
Is .daiwa a real TLD? Who’s applying to run it?
.daiwa is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Daiwa Securities Group Inc..
A private corporate namespace for one financial group; no public registrations and no resale market.
the applicant company itself and its subsidiaries, for branded, controlled web addresses such as customer portals and campaign sites; not sold to the public
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 romanized Japanese house name carried by a large diversified group, where the string is an ordinary Japanese name rather than a coined mark, so the applicant is buying a namespace whose word other unrelated same-named firms also use.
Same bet: a Japanese financial group putting its primary corporate identity on the romanized short form of its house name, aimed at its own customers and group companies rather than any outside registrant.
Same bet in its riskiest dimension: a company claiming a plain, widely shared Japanese word as its own corporate identity, which only works if its own brand recall overrides the word's generic reading.
What a .daiwa domain is
.daiwa 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 .daiwa domain extension real yet?
.daiwa 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 .daiwa domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .daiwa name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .daiwa was .otsuka, delegated on 27 August 2014.
Is .daiwa a real TLD?
Not yet. .daiwa is not in the DNS root, so nothing resolves under it. It’s here because .daiwa is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Daiwa Securities Group Inc. · first recordedICANN
“86012611T-T77268 · Daiwa Securities Group Inc. · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified record shows a single confirmed application from Daiwa Securities Group Inc., and the string is a corporate name, so this is a closed dot-brand: the only realistic registrant is the applicant and its group companies. It is not in the 30-49 band because there are no volume or price-driven registrations at all and no aftermarket can form around a single-registrant namespace. It is not in the 1-9 band because one serious user does exist with a clear use case: by analogy with financial-sector dot-brands from the 2012 round (banks and insurers that moved customer login pages, campaign sites or shortlinks onto their own TLD), a securities group can get genuine anti-phishing and trust value from an address space only it can issue on. By analogy, however, many 2012-round dot-brands, including a number from Japanese corporates, were delegated and then saw little or no live use or were later voluntarily terminated, so end-use utility over the next 5 years is uncertain and depends entirely on internal adoption decisions, not on market demand. Main uncertainty: whether the group actually migrates customer-facing services onto the TLD or keeps it defensive, which is the difference between a working trust signal and an unused string.