Send the name in Cyrillic and tell us which registrar holds it today. Add the punycode form if you have it. .РФ encodes as xn--p1ai, and a Cyrillic name does not always come through a ticket form, a mail client or a copy out of somebody’s browser bar intact. Having both spellings in front of us removes a whole category of guessing before the first lookup.
What gets checked against the .РФ rules
Four facts: who holds the administrator record, what status the domain is in, what the registrar requires of that administrator, and when the name falls due for renewal. All four are read against the rules for .РФ, not against the version of the process you may already have been quoted for .RU.
Both extensions are administered by the Coordination Center for TLD .RU/.РФ ↗, so a good deal does carry across. A good deal is not all of it. Where a registrar handles a Cyrillic name differently, it usually shows up in the small operational steps, and those are far cheaper to find now than in the week a renewal falls due.
Where the arrangement has to be explicit
A trustee arrangement proposed for a .РФ name should pin down the same points as one written for .RU:
- DNS instructions: who issues them, and who is obliged to act on them.
- Identity checks: which fall to the trustee, and which stay with you.
- Renewals: who pays, and on what notice.
- Administrator exit: how the record comes back to you, or moves on to somebody else.
None of that is specific to .РФ, which is rather the point. The extension changes what you verify. It does not change what the agreement has to cover. Exit is the clause most often left vague, and the only one that counts on the day somebody wants out.
Need a .RU domain?
Atak Domain lists availability and registration options. This page is for the other case: a domain that already exists, with an administrator or renewal question attached to it. If that is yours, request an assessment.
Search .RU availability at Atak Domain