.cloud

This article describes the procedures and requirements of .cloud domain names.
Click on the subject below to open the dropdown for more information.

Successful domain registration requires:

  • the domain's contact handles (owner, administrative, etc.)
  • two or more nameservers or a nameserver group


Note that, as for ICANN's contact verification requirements, we are obliged to send an e-mail to the domain owner if his e-mail address was not verified before. Failure to respond to this e-mail may lead to suspension of any gTLD domain name with this same e-mail address in the owner contact.

You can start the .cloud main transfer through our API or RCP.
This transfer requires the following information:

  • an authorization code that you need to request at your current provider.
  • the domain's contact handles (owner, administrative, etc.)
  • two or more nameservers or a nameserver group

 

A transfer for a .cloud takes a maximum of 6 days to complete. The transfer can be rejected by the current provider or the owner of the domain during this period.

The registration period after a successful transfer will extend with 1 year unless the transfer is ordered within the domain's auto-renew grace period at the previous registrar. 

Authorization code required yes
Method of confirmation authcode,email
Registration period after transfer extends
Average transfer time Max 6 days
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .cloud domains is available.

Owner change (trade)

  • requested as a normal domain update via RCP or API
  • processed realtime
  • both previous and new registrant will receive an e-mail. This is a notification only, no action is required.
  • registrant e-mail address verification applies

Other update

  • requested via RCP or API
  • processed realtime

 

If as part of the update the domain owner’s e-mail address changes, we’re obliged to start a contact verification process if this new e-mail address was not verified before.

Delete

Explicit delete

  • Requested via RCP or API
  • processed realtime
  • will directly result in quarantine (redemption period)  (no soft quarantine applies)


Expiration
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

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)
Registry
Domain lifecycle
Technical information
  • DNSSEC support: yes
  • Minimum length: 3 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z, 0-9, -
  • 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.
  • Soft quarantine period: 44 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: 28 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? n/a
  • Local activity required? no
  • Correct nameserver configuration required? no
Policies
  • Rules for Uniform Domain Name Dispute Resolution Policy: http://www.icann.org/en/help/dndr/udrp/rules
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:
Was this article helpful?
1 out of 1 found this helpful