.рф (.xn--p1ai)

This article describes the procedures and requirements of .рф (.xn--p1ai) domain names.
Click on the subject below to open the dropdown for more information.

Successful domain registration via RCP or API requires:

  • two or more nameservers or a nameserver group
  • registrant e-mail address verification applies
  • Filling out .ru/.рф additional data fields during contact creationFor 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
    -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 fieldsNB: .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

Successful domain transfer via RCP or API requires:

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.


Additional notes on a .xn--p1ai 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.


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 .xn--p1ai domains is available.

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.

Owner change (trade)

Successful trade 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


  • 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

Documents are 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 moves domain to the new owner.

Owner change application forms

For private individuals: https://drive.google.com/file/d/1Qibr7MIellunJgVsDbp4xWCvPVC89MaZ/view

For Legal entities: https://drive.google.com/file/d/1l6XcgxK0efI-VstHqWakBLSMHROhQgQ1/view

Other update

Other updates

  • Nameservers - can be updated via RCP or 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.


For Legal Entities:

  • Fill in the application form: https://drive.google.com/file/d/1l6XcgxK0efI-VstHqWakBLSMHROhQgQ1/view?usp=sharing
  • 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: https://drive.google.com/file/d/1Qibr7MIellunJgVsDbp4xWCvPVC89MaZ/view?usp=sharing
  • 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.


Explicit delete

Deleting domain via RCP or 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

For private individuals: https://drive.google.com/file/d/1u83DvnmRsGuctrDYBiZwpGKisjJ8cBfV/view?usp=sharing


For legal entities: https://drive.google.com/file/d/1-iXTEoHLUFnypAW8-CzcQwgV0wXwBPcA/view?usp=sharing 



In case the domain expires (not renewed in time);


will not be deleted directly at the registry

will lead to soft quarantine, followed by regular quarantine

IMPORTANT: Can not be renewed earlier than 60 days before expiration. Domains .рф/.ru doesn't support explicit renewals, se we just increment the date in OP and the domain gets renewed automatically at the registry when the time comes.

Restore / reactivate

  • restore / reactivation supported via RCP or API
  • quarantine periods can be found under
    Detailed extension information > Technical information > Quarantine period
  • After quarantine, 5 days PendingDelete period (restore not possible)
Technical information
  • DNSSEC support: no
  • Minimum length: 3 characters
  • Maximum length: 63 characters
  • Allowed characters: only Cyrillic characters
  • IDN characters: yes
  • Registration period: 1-10 years
  • Renewal date offset: 0 days
    The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info.
    Note that the dates as shown in your Openprovider account are always leading, even if they do not match the renewal date offset mentioned here.
  • Soft quarantine period: 40 days
    During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info.
  • Quarantine period: 0 days
    During this period, an expired or deleted domain name can be reactivated at an additional fee.
  • Local presence required? no
  • Does Openprovider provide local presence services? no
  • Local activity required? no
  • Correct nameserver configuration required? no
  • Only Cyrillic domain names allowed
  • The Domain(s) can be registered without further limitations.
  • http://www.cctld.ru/en/docs/rules.php
  • In accordance with clauses 9.3.7 - 9.3.8 of registry policies, we may initiate domain owner details verification at will, if we suspect said details inconsistency. If documents, verifying supplied owner details are not present within 7 calendar days since requested, domain delegation is terminated in accordance with clause 5.6 of registry's T&Cs, until documents are supplied.
  • ru/.рф additional data fields must be filled-in
  • For non-Russia based individuals and companies, Cyrillic .ru / .рф additional data fields can be filled-in in Latin characters
  • Company number (companies) or Identity Card number (individuals) is required.
  • Registrant name must include the company type if the registrant is a company. For example: 'BV', 'Ltd.', 'GmbH'.
  • Cyrillic domain names can only be registered with .рф tld
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.

Was this article helpful?
Additional questions? Submit a request