.pr

This article describes the procedures and requirements of .pr 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:

  • two or more nameservers or a nameserver group

Successful domain transfer via RCP or XML API or REST API requires:

  • authorisation code
  • two or more nameservers or a nameserver group
Authorization code required yes
Method of confirmation authcode
Registration period after transfer extends
Average transfer time Realtime
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .pr domains is available.

Authcode is required.

Owner change (trade)

Domain udpates (including owner updates) are allowed but chargeable.

Other update

  • Requested via RCP or XML API or REST API
  • Domain updates are charageable.

Delete

Explicit delete

Restore / reactivate

  • Restore / reactivation supported via RCP or XML API or REST API 
  • Quarantine periods can be found under
    Detailed extension information > Technical information > Quarantine period
Registry
Technical information
  • DNSSEC support: yes
  • Minimum length: 1 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z 0-9 -
  • IDN characters: yes
  • Registration period: 1 - 1 year(s)
  • Renewal date offset: 35 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: n/a 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.
Restrictions
  • Local presence required? no
  • Does Openprovider provide local presence services? no
  • Local activity required? no
  • Correct nameserver configuration required? no
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.

Was this article helpful?
Additional questions? Submit a request