.RU

TLD metadata
Add Properties
Register
Transfer in
Trade
Transfer out

TLD metadata


Add Properties

In order to add properties for .RU domains to a contact, follow the procedure below.

  • Lookup the contact you wish to add the properties to and open it. Next, you're going to add additional properties to the contact. In this case, you will choose the .RU (tci) option. Once you've selected the .RU properties, you'll be directed to the page where you can submit the requested information.

Take note: The information added as additional properties have to be correct and valid.

  • Fill out the data as requested by the form and click save properties when you're done.
  1. ID number: Submit the passport number, only applicable for natural persons.
  2. Date of birth: Submit the date of birth, only applicable for natural persons. (Format: YYYY-MM-DD).
  3. Taxpayer identification number: Submit the Taxpayer identification number, only applicable for organizations.

Register

To create a .RU domain, follow the procedure below:

  • Create a contact handle, or search for a contact handle already created with valid data to use for the create. For a detailed description of how to create a contact handle, check the contacts knowledgebase article.
  • Add additional properties for .RU (tci) to the Registrant contact.
  • Use the availability checker to determine if the domain is available. If the domain is available, select it to register using the green 'Select to register button' and confirm with the 'Register selected domains' button.
  • Submit the details you wish to use for registration. For in-depth support on the registration process, check the register domain(s) knowledge base article.

Transfer in

To successfully transfer in a .RU domain, follow the procedure below:

  • Create a contact handle, or search for a contact handle already created with valid data to use for the transfer, for a detailed description of how to create a contact handle, check the contacts knowledgebase article.
  • Add additional properties for .RU (tci) to the Registrant contact.
  • Initiate the transfer through the Domain Manager. For a detailed description of how to initiate a transfer through the Domain Manager, check the initiate transfer knowledgebase article.
  • Once the registrant accepts the transfer FOA sent by the current registrar, the transfer will complete real-time.
Troubleshooting

If the transfer fails due to an incorrect authcode, keep in mind that .RU authcodes have limited validity. Have the registrant request a new authcode with the current registrar and re-initiate the transfer. If the transfer still fails on the second attempt, contact support.


Trade

To successfully change the registrant for a .RU domain, follow the procedure below.

  • Create a contact, or search for a contact already created with valid data to use for the registrant change. For a detailed description of how to create a contact, check the contacts knowledgebase article.
  • Add additional properties for .RU (tci) to the Registrant contact.
  • Send an email to support@realtimeregister.com and request the trade. Take note: Provide the domain and registrant contact you want to update the domain to. Without this information, we're not able to start the trade procedure.

Take Note: For the registrant change of a .RU domain you will need a signed form on which the registrant requests the registrant change with the registry. This form will be supplied by support in a reply to your registrant change request.

  • Fill out all necessary fields on the form. The current owners ID and the new owner handle are pre filled on the form.
  • All the other fields have to be submitted as an exact match to all the registrant information submitted in the current & new registrant contacts.

Take Note: The 'application' section on the form is where the current registrant information is submitted. The 'To the new Owner:' section on the form is were the new owner's information is submitted.

  • The current owner and a licensed notary have to sign the document for approval.
  • Return the signed form to support@realtimeregister.com along with a valid copy of the current owners' ID. Support will forward the documents to the registry to start the trade.
  • Once the trade has completed, you'll be notified by support through email.

Legacy (RUcenter)

Take note: The information below is applicable for .RU domains registered or transferred to Realtime Register before November 2015.

First off, determine if RU-center is the registry active for your domain. This can be done by checking if RU-center properties are active for the current registrant contact handle. When opening the contact page, properties, as shown on the image below, should be visible.

If this is the case, you will have to go to the RU-center website and download the letter applicable to the situation of the current registrant:

Or

Once you've downloaded the letter, follow the steps below to request a trade.
  • Create a contact, or search for a contact already created with valid data to use for the registrant change. For a detailed description of how to create a contact, check the contacts knowledgebase article.
  • Add additional properties for .RU (tci) to the Registrant contact.
  • Have the registrant fill out the letter applicable for his/her situation, if the registrant is not in possession of their NIC-D number, request this with support through email.
  • Request the trade by updating the domain to the new registrant contact handle and provide the letter to support with an email to support@realtimeregister.com. Make sure you provide the new registrant contact handle and the signed letter in your email. Additional identification documents may be required to complete the trade. If this is necessary, support will request the necessary documents in reply to your email.
  • Once all documents are received, support will request the trade with the registry.
  • Once the trade is completed, you'll be notified by support through email.

Transfer out

To transfer out a .RU domain, follow the procedure below.

To transfer out a .RU domain you're going to need an authcode. At this time, the authcode has to be requested by support manually.

  • First, remove all transfer locks for the domain through the Domain Manager or API.
  • Send an email to support@realtimeregister.com requesting the authcode for the domain you need to transfer.
  • Support will log in with the registry control panel to send the authcode directly to the registrant email address.

Take note: The registrant email address needs to be verified through email. If the registrant email address is not verified, support will request validation and an email is send to the registrant email address to confirm his/her contact details. Once the validation has been sent, you'll be notified in a reply to your authcode request.

  • Once the registrant email address is verified, notify support and they will request the authcode and confirm the authcode being requested in a reply to your email.

Take note: The authcode is only valid for 20 days.

  • Once the registrant has obtained the authcode, they can initiate the transfer with the new registrar using the authcode and the transfer will complete real-time.

Legacy (RUcenter)
Take note: the action below should only be performed by the registrant of the domain.

Have the registrant go to:

https://www.nic.ru/info/services/domain-transfer/to-other-registrar/

Here, the registrant can request the authcode through the procedure below.

  • Log in to the /NIC-D account provided
  • Enter the domain you wish to transfer
  • Select the delivery method. !! SET TO E-MAIL !! This has to be done manually. Collecting at RU-Center is the standard-setting.
  • A confirmation e-mail is sent to the registrant email address. This can take up to 3 hours. !! The authcode is valid for 72 hours !!
  • Use the authcode to start the transfer with the new provider.
Troubleshooting:

If you or the registrant does not know the correct NIC-D number, send an email to support and they'll provide the NIC-D number.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us