Domain administration guidance for non-residents Reviewed 15 September 2026

ESIA account route

Gosuslugi verification for a .RU administrator

Gosuslugi is the public services portal, and the usual way into ESIA, Russia’s Unified Identification and Authentication System. For a .RU domain the question is narrower than it first looks. It is not whether you can prove who you are. It is whether the administrator recorded by the registrar can complete the identity process that your next operation requires.

Last reviewed: 15 September 2026

The practical start

Four facts come first: the administrator shown in the registrar record, any notice attached to that account, the operation you are asking for, and the domain expiry date. Collect those, then weigh a trustee. Doing it the other way round is how people buy a service that does not fit the case.

Direct answers

Reviewed 15 September 2026

What is Gosuslugi in this domain process?

Gosuslugi is the public services portal, and the usual way people reach ESIA, Russia’s Unified Identification and Authentication System. What it touches here is the identity of the recorded domain administrator. It is not a public lookup for domain availability, though plenty of people arrive expecting one.

The rules are one thing and the account process is another: your registrar applies its own procedure on top of them, which is why two customers can be told two different things in the same week. Two questions settle most cases. Which person or company has to complete verification? And which domain action is waiting on it right now?

Rules and implementation: Coordination Center verification update ↗ · Atak Domain’s current .RU guidance ↗

Can a foreign company verify directly?

Sometimes. Atak Domain’s current .RU guidance describes a route for a foreign company that has an accredited Russian branch together with an organisation ESIA account. Both halves matter. Without qualifying Russian presence, a director’s passport and an overseas company certificate do not open that route on their own, however well they are certified. Confirm eligibility, and confirm what your registrar implements today, before you pay for translations or start moving the administrator record.

Rules and implementation: Coordination Center verification update ↗ · Atak Domain’s current .RU guidance ↗

Does 18 January 2027 apply to every domain?

No. That date is reported in Atak Domain’s current .RU guidance as a registrar transition date, and no universal deadline for domains should be read out of it. It describes when accredited registrars finish switching over. It says nothing about your registration.

Three facts stay separate: the timing of your registrar’s switch, the expiry date on your domain, and the operation you are actually trying to complete. They rarely fall in a helpful order. A renewal that comes due before your registrar has finished changing over is a different problem from one that comes due afterwards, and the second is usually the easier of the two. So ask the registrar what its process is at the moment, look up your own renewal date, and let those two answers set the timing of an administrator-change application rather than a headline date.

Rules and implementation: Atak Domain administrator-change guide ↗

Atak Domain operational service information: administrator-change and ESIA guide ↗ · updated .RU registration and renewal guide ↗. Case-specific steps still have to be checked with the accredited registrar.

The administrator, not the website user

Whoever runs the site is not automatically whoever the registry recognises. A business can publish the website, control the DNS, pay every invoice on time, and still not hold the administrator record; another legal person does. Verification follows that record. It does not follow the traffic, the billing address or the password to the control panel.

Which leads to the thing people get wrong when a trustee is in the picture. Signing into your own customer account does nothing for the trustee account’s verification, no matter how thoroughly you are verified yourself. They are different accounts. The one the registrar checks is the one attached to the administrator entry.

A foreign company with a Russian branch

Atak Domain’s current .RU guidance sets out a possible route here: a foreign legal entity with an accredited branch, holding an eligible organisation ESIA account. Treat that as a starting point rather than a ruling. A published page describes the general route; your registrar decides what it accepts from you, on the day you ask it.

Without an accepted direct route

Two options to compare. One is whatever documentation route your registrar will take. The other is a formal administrator change to a party that is already verified.

The second moves the registry-facing record, which is exactly why the contract sitting behind it needs to be specific: who may use the domain, who gives DNS instructions, who carries renewal responsibility, and how the record comes back to you when the arrangement ends. Settle the exit in the same document as the entry. Nobody has ever regretted that order.

Need a .RU domain?

Availability and registration options are at Atak Domain. If the issue is an existing domain with an administrator or renewal question attached to it, request an assessment.

Search .RU availability at Atak Domain