Many scripts
Chinese, Japanese, Korean, Cyrillic, Arabic and more, wherever the ending supports IDN registration.
Chinese, Japanese, Arabic and other non-ASCII names. Registries store them as Punycode.
For a local audience, what people remember is the form written in their own script. But a few things are worth settling before you commit.
Type it as it should read, or paste a complete domain.
Registries require the language or script to be declared - zh-Hans for Simplified Chinese, for example.
The screen shows both the Unicode and the Punycode form.
Chinese, Japanese, Korean, Cyrillic, Arabic and more, wherever the ending supports IDN registration.
Type the script; the page also shows the form actually stored in the register, so you can check it.
Common tags built in, or type the standard form. ICANN requires the tag to be declared at registration.
Endings marked as not taking IDN in the price list say so directly in the result instead of failing quietly.
The thing to check when registering an IDN
Different scripts contain characters that render almost identically. Attackers use them to register a domain that looks exactly like your brand and use it for phishing; the reverse also happens, where somebody registers the form you meant to take.
Before ordering, check the punycode against the string you intended. The punycode is what the registry actually stores, and one character out is a different domain. Where the risk is real, register the obvious lookalikes as well.
Registerable does not mean every client copes
We suggest both. The script form serves your local audience; the ASCII form still works on keyboards, mail clients and social platforms that do not handle the other script.
They are different domains. Some registries treat certain variants as one registration, so register the forms you actually use before somebody else takes a lookalike.
The price is the same as any other name under that ending; IDN carries no surcharge. Where an ending is expensive, that is the ending, not the script.
The tag is only validated when the registration is submitted, not during the check. Failures are usually because the ending does not take IDN, or the string cannot be converted to valid punycode.
Websites: yes, browsers and DNS handle punycode natively. Mail: confirm your clients accept non-ASCII addresses, and test before making it the main contact.
ICANN requires an internationalised domain to declare the language or script it belongs to. The registrar search command does not check it, so a wrong or missing tag looks identical while searching - but the registration is refused without it.
That is each registry decision. The registrar price list states whether an ending accepts IDN registrations, and endings that do not are marked in the dropdown.
Yes. Browsers and mail systems handle Punycode natively, so visitors see what you typed; the registry record holds the xn-- form.
From choosing a name to managing it, these usually happen one after another in the same session.