Buy .рус Domain Name

No. The community section of the ICANN agreement asks for no nationality or residency; it states that the extension will be open to anyone complying with the registry's Acceptable Use Policy and with ICANN guidelines, and in its own words that it «will be treated as a gTLD such as .COM». No documents are required either. On the use side, however, there is a condition, and it concerns language — sites are expected to carry the majority of their content in the Russian Cyrillic language.

The agreement frames this as a condition, not an expectation. The primary goal of the extension is the protection of Russian Cyrillic culture, language and heritage, and the registry requires two things of sites seeking a place in it: that the majority of their content be in the Russian Cyrillic language, and that this content respect the Russian Cyrillic language, culture and history. The Acceptable Use Policy states the same rule negatively, expressly forbidding use that denigrates the Russian language, culture or heritage.

Both are in Cyrillic, but institutionally they have nothing in common. .рф is a country code extension managed by the Coordination Center in Moscow; .рус is a generic community extension from ICANN's new extension programme, operated by Rusnames Limited in Samara. The rules of .рф therefore do not apply in .рус; term, lifecycle and dispute procedure follow separate documents. The scale differs too: in April 2026 .рус held 20,635 names against 805,286 in .рф.

No. The name selection section of the agreement states that second-level names will be in the Cyrillic alphabet, adding that this alphabet already includes the Unicode points for the numbers 0-9. So .рус is by definition an internationalised domain zone; a name in Latin script cannot be built. The registry also states that it will follow ICANN guidelines regarding potential restrictions on second-level domains.

According to the announcement, no. The notice published by the Technical Centre says the «Gosuslugi» identity verification becoming mandatory on 1 September 2026 applies to the .ru, .рф and .su zones, and it does not list .рус. The reason is institutional: those three zones follow the Coordination Center's rules, while .рус follows its ICANN agreement. Even so, it is worth confirming your registrar's own identity checks before ordering.

Through random audits. The agreement states that the registry has complete enforcement rights over a registrant's use: a breach of the policy counts as a material breach of the agreement, and the registry reserves the right to revoke, suspend, terminate, cancel or otherwise modify the rights to the name. In practice it randomly audits names to ensure compliance with all eligibility and use criteria, and if a violation is discovered an investigation begins immediately. If an applicant appeals, the registry reviews it and may assign the dispute to an ombudsman.

Through RDAP. The IANA root zone record — last updated on 4 December 2025 — carries no WHOIS server line for .рус; it names only an RDAP server address. A measurement on 14 August 2026 found that endpoint working and returning a domain object for the name queried. Classic WHOIS tools that connect to port 43 may therefore not behave as expected in this zone. You can inspect records for other extensions on the whois search screen.