.xn--kbt444f one string, 3 would-be registries

What contention means for .xn--kbt444f

Only one registry can run .xn--kbt444f. Contended strings are resolved after evaluation: applicants can negotiate or form a joint venture, a qualifying community application takes priority, and whatever is left goes to an ICANN auction of last resort. That process adds months — realistically, a contended string launches later than a clean one, and the winner's pricing and registration rules are unknowable until the contention set closes.

When can you register a .xn--kbt444f domain?

Not yet — .xn--kbt444f does not exist as a registrable extension today. If the application clears every stage, the registry will run a trademark sunrise first, then open general registration. The milestones:

1. Reveal Day7 Oct 2026

   ICANN published every application: 1,614 primary applications covering 986 different strings from 481 applicants.

2. String Confirmation Day17 Nov 2026

   After the replacement window, ICANN publishes the final confirmed string list. Strings can still change until this day.

3. Community input & objections17 Nov 2026 – 16 Mar 2027

   Anyone can comment on an application; formal objections (legal rights, community, public interest) are filed in this window.

4. Prioritisation draw & evaluationH1 2027

   Applications are evaluated in draw order. Contended strings go to contention resolution — community priority, negotiation, or auction.

5. Delegation & public launch2027–2028

   Winning registries sign contracts, get delegated into the root, then run sunrise (trademark) and general registration phases.

Other contested strings