This page contains the official guidelines regarding .eu in Cyrillic, or .ею. The information on this page is only available in English.
Accredited registrars or registrars currently undergoing accreditation for the .eu extension are accredited for the .ею extension by default. No extra pre-payment is required.
All policies, procedures and features currently available for .eu such as transfers, bulk transfers, multiyear, DNSSEC, registry lock, etc., also apply to .ею (Cyrillic string).
The current WHOIS Policy and Terms & Conditions apply to domain names registered under .ею. The Alternative Dispute Resolution is also available for .ею.
The script of the second level domain name must match the script of the TLD extension (.eu, .ею). In other words, if anyone registers abc, they get abc.eu (with the Latin TLD extension). If the domain name being registered is in Cyrillic script, the script at the top-level will be .ею.
A registrar wishing to register an exclusively numeric domain name - possibly including hyphens - should specify the TLD extension. In the case that the extension is not specified, the .eu (Latin string) extension will be allocated by default.
The homoglyph bundling rules for domain names registered in Latin, Cyrillic, and Greek follow the IDNA 2008 protocol and our homoglyph bundling rules, taking into account the extension. As the Cyrillic extension cannot be confused with the Latin or Greek extensions, EURid assumes that domain names with the Cyrillic extension can never be confused with those in the Latin or Greek extension.
When undertaking a DAS request, the whole domain name is taken into account, including the extension. When no extension is provided by the user, it will be added by the system according to the rule outlined above; the script of the domain name defines the extension and purely numerical domain names receive a .eu extension by default. The DAS output only has three different possible values: NOT ALLOWED, NOT AVAILABLE and AVAILABLE.
A domain name that violates the 'no script mixing rule' (e.g. abcd.ею) always returns a NOT ALLOWED value, as this name cannot be registered under any circumstances.
For a WHOIS request, the same rule is applied in order to add the extension if it is missing. The textual WHOIS (port 43) will keep its minimal output and refer to the web-based WHOIS for more detailed information.
Lastly, the web-based WHOIS allows the user to provide a specific extension for a domain name, or leave it up to the system to define the extension (again using the same rules as described above). However, the web-based WHOIS always shows the domain names that are in the same homoglyph bundle. You can find more information about these domain names by simply clicking on them.
On 1 June 2016 EURid enforced the basic rule that the second level script must match the top-level script, in order to eliminate any possible confusion. Please note that .eu domain names registered in Greek script are managed under the .eu rules. Regarding the original domain names registered in Cyrillic under .eu, EURid has:
Consequently, EURid activated all Cyrillic domain names that had been cloned from .eu to .ею. The original and cloned domain names co-existed until 31 May 2019, and were maintained by the registrar independently of one another. During the script adjustment phase, registrars did not have to pay for cloned domain names.
Specific cases at the time the .ею (Cyrillic string) extension went live:
At the launch of .ею: