.seiko
Is .seiko a real TLD? Who’s applying to run it?
.seiko is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Seiko Group Kabushiki Kaisha.
A company-owned namespace for one watchmaker; useful to that brand, closed to everyone else, with no resale market.
the applicant company and its subsidiaries, regional sales arms and product lines, which would use it for first-party sites, campaigns and secured customer touchpoints
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.
Both are the single-word house mark of a vertically integrated watch manufacturer applying for its own name as a closed corporate namespace, so the bet rests entirely on the company's own willingness to move its retail and product identity onto a brand TLD it alone controls.
Same bet of a globally recognized watchmaker's proper-name trademark used as a brand-owned namespace, with the one difference that it must also be defended as an ordinary dictionary word rather than being distinctive on its face.
An identical bet in structure — a mid-size Japanese manufacturing group's coined latin-script house name, applied for by the company for its own product and dealer identity — differing only in that the goods behind the mark are electronics rather than timepieces.
What a .seiko domain is
.seiko 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 .seiko domain extension real yet?
.seiko 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 .seiko domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .seiko name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .seiko was .swatch, delegated on 26 June 2015.
Is .seiko a real TLD?
Not yet. .seiko is not in the DNS root, so nothing resolves under it. It’s here because .seiko is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Seiko Group Kabushiki Kaisha · first recordedICANN
“80502644T-T59918 · Seiko Group Kabushiki Kaisha · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows a single application typed as brand from Seiko Group Kabushiki Kaisha, with no contention recorded, so the string would operate as a closed dot-brand: registrations limited to the company and its affiliates. The best-fit buyer is therefore the brand itself, and the value is end-use utility only: a widely recognised watch, clock and precision-instrument maker could plausibly run product, regional or authentication pages under its own TLD, and the string carries the brand's credibility by definition. It is not in the 30-49 band because there is no open registration, no volume and no aftermarket at all; that band assumes a public market that does not exist here. It is not in the 1-9 band because there is a realistic, if single-buyer, use: the company's own web presence can adopt it as a primary identity, and by analogy with the earlier round's brand TLDs (analogy, not a verified fact) a minority of dot-brands did become their operator's main web identity, while most saw little public use and some were later retired. Which of those paths this string takes over the next 5 years is the main market uncertainty; the counts, dates and names of such outcomes are unknown to me under the rules here. A secondary uncertainty is whether a consumer-facing accessories brand sees enough trust, search or anti-counterfeiting benefit to move primary traffic off its existing domains.