Loading…
Internationalized extensions
Browse extensions written in non-ASCII scripts. The extension’s script and support for internationalized names before the dot are separate registration rules.
Registrar filters· USD
Columns
| Domain | Cheapest registration | Cheapest renewal | Cheapest transfer | Popularity | Best 3-year value |
|---|---|---|---|---|---|
47.1K registrations | |||||
| — | 25.5K registrations | ||||
22.9K registrations | |||||
19K registrations | |||||
17K registrations | |||||
15.6K registrations | |||||
11.2K registrations | |||||
9.9K registrations | |||||
| — | 4.8K registrations | ||||
3.4K registrations |
Questions
Why does an internationalized domain sometimes use xn--?
Unicode domain labels have an ASCII form for DNS use. RFC 5890 calls the Unicode form a U-label and the encoded form an A-label; the familiar xn-- prefix identifies that ASCII-compatible form.
Can I register any characters written in the same script?
No. A registry’s IDN table defines the characters it makes available and may have separate tables for languages or scripts. Check the extension’s rules and its registry table before choosing a name.
Are lookalike letters the same domain?
No. Characters can look alike while representing different domain strings. Registries define any variant-character rules in their IDN tables, so a visually similar name is not a substitute for checking the specific name you intend to use.
Can I search using Unicode characters?
Yes. Search accepts valid Unicode domain input and converts it to the DNS-compatible form needed to match an extension. That conversion checks the form of the name; it does not decide the registry’s character policy.