This article describes the procedures and requirements of .ru domain names.
Click on the subject below to open the dropdown for more information.
Successful domain registration via RCP or XML API or REST API requires:
- Filling out .ru additional data fields during contact creation
- For Private individuals:
- VAT number (optional)
- Mobile phone
- Birth date
- Passport / ID number
- Passport / ID series (if not present, put a placehollder)
- Passport / ID issuer organization
- Passport / ID issue date
- First name
- Middle name (optional)
- Last name
- Postal address
- For Legal entities:
- VAT number or company registration number
- Company name with clearly stated type (B.V., LLC, etc)
- Mobile phone
- Company legal address
- Company postal address
- For Private individuals:
- Verifying mobile phone number via RCP or API
NB: Registration not possible on Mon - Fri 14:00 - 15:00 UTC, see technical details section below for more information.
NB: Russia based entities must supply company / person name in both Cyrillic and Latin variants. For non-Russia based entities it's allowed to fill only Latin names and paste them in Cyrillic fields
NB: .ru / .рф domains have special whois statuses:
- REGISTERED - indicates, that domain is registered
- DELEGATED / NOT DELEGATED - indicates, whether domain has nameservers assigned
- VERIFIED / UNVERIFIED - indicates, whether domain owner is verified. Verification can be performed by sending owner's scanned copy of ID / passport or business certificate to Openprovider support
Note: New .com.ru and net.ru registrations and incoming transfers are not possible.
Successful domain transfer via RCP or XML API or REST API requires:
- Authorization code
- Two or more nameservers or a nameserver group
- Confirmation email sent by the .ru Registry to the current owner of the domain has to be approved during 5 days otherwise the transfer attempt will be expired.
The owner can not be changed during the transfer, therefore you can not add handles in the transfer request. The contact are imported automatically from the registry after the transfer is successful.
Note: New .com.ru and net.ru incoming transfers are not possible.
Additional notes on a .ru transfer
- Authorization code validity - 20 days
- reg-ch field in WHOIS output - recipient registrar identifier which indicates ongoing transfer procedure
NB: Transfer not possible on Mon - Fri 14:00 - 15:00 UTC, see technical details section below for more information.
Openprovider is not a reseller from RU Center but is directly accredited at the Russian Registry. Therefore internal transfer codes from RU Center can not be used for transfers.
Please request your transfercode for external transfers ("to other registrar") at RU center:
https://www.nic.ru/en/info/services/domain-transfer/to-other-registrar/
Important when requesting the code:
Set "Receipt of transfer codes" to email, otherwise you might have to pick up the transfercodes at the RU-Center office in Moscow.
The registrar change procedure for .ru and .rf domains is not carried out in the following cases:
- there are less than seven days left before the registration period expire.
- court or pre-trial restrictions have been imposed on the domain name.
- less than 30 days have passed since the change of administrator.
- less than 30 days have passed since the last change of registrar.
IMPORTANT TO KNOW: A .RU transfer does not come with a renewal. Price for transfer and renewal is similar, but they are two different actions.
| Authorization code required | yes |
| Method of confirmation | authcode,email |
| Registration period after transfer | unchanged |
| Average transfer time | max 5 days |
| Advanced and simple transfers available | Contact our Sales department to check if easy transfer of 100 or more .ru domains is available. |
- Authorization code request - via RCP (Reseller Control Panel) or XML API or REST API
- Authorization code delivery - directly to domain owner via SMS, email or post
- Authorization code validity - 20 days
- Authorization code sending - is manual and takes up to 3 business days
Owner change (trade)
- Successful trade via RCP or XML API or REST API requires - providing physical copies of documents
- Authorization code required to initiate a trade
- Authorization code request - via RCP or API
- Authorization code delivery - directly to domain owner via SMS, email or post
- Authorization code validity - 20 days
- Authorization code sending - is manual and takes up to 3 business days
- 30 days after a successful trade - domain can't be transferred or traded to another owner
Process
- Trade is requested via RCP or API
- Reseller receives a notification listing documents required to proceed
- For Private individuals:
- Scanned copy of the domain owner’s passport/ID
- Completed and notarized owner change application form
- For Legal entities:
- Stamped with company's seal and signed by an entitled person scanned copy of a business certificate or chamber of commerce extract of the current registrant
- Filled-out, stamped with company's seal and signed by an entitled person owner change application form, with company's letter-head
- For Private individuals:
- Documents are sent to Openprovider support via email for verification
- As soon as documents are received, Openprovider support moves domain to the new owner
Owner change application forms
Other update
Nameservers - can be updated via RCP or XML API or REST API
Domain owner email and phone - can be changed via request to Openprovider support, no additional documents required
Domain owner address, passport/ID details, VAT - can be changed via request to Openprovider support and require filling-out an application form
Process
- For Legal Entities:
- Fill in the application form
- Send a scanned copy of the application form and company business certificate, proving the validity of the new details to Openprovider support
- If information is correct, owner data will be updated
- For Private Individuals:
- Fill in the application form
- Send a scanned copy of the application form and owner's passport or ID proving the validity of the new details to Openprovider Support.
- If information is correct, owner data will be updated.
IMPORTANT: .ru can not be renewed earlier than 60 days before expiration. Domains .ru doesn't support explicit renewals, se we just increment the date in Openprovider and the domain gets renewed automatically at the registry when the time comes.
Delete
- Deleting domain via RCP or XML API or REST API - schedules domain for deletion at the expiration date
- Deleting domain before expiration date requirements:
- Deletion request via RCP or API
- Filling out deletion application form
- Documents sent to Openprovider support via email for verification
- Once verified, physical copies must be sent to one of Openprovider offices
- As soon as documents are received, Openprovider support deletes domain completely
Domain deletion application forms
Restore / reactivate
| Registry |
|
| Technical information |
|
| Restrictions |
|
| Policies |
|
| Registration agreement | The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following: |
Due to the regular changes in registry rules and configuration or missing information from registry side, and despite our effort to keep our knowledge base up-to-date, information in the knowledge base may be outdated or incorrect. If you encounter some issue, please report it through the "HotJar" feedback collector on the bottom right, or (if it is blocked by your browser) by clicking the "Submit a request" link below. No rights can be derived from the information in this knowledge base. If there is discrepancy between the knowledge base and the process in Openprovider, the process in Openprovider is leading.
