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

Registration of a .co.id, .or.id or .web.id domain requires a local address of the domain owner and administrative contact. Furthermore, a copy of trademark documentation or commercial license is required.

If all these are present a registration can be started by contacting our support department with the domain name, contact handles and nameservers you would like to use.

We will initiate the procedure for you and send the necessary forms for registration.

Note that the top level domain .id is available without local presence requirements.
To transfer a .co.id domain, please retrieve the authorization code from the current registrar and send this to our support department together with the contact handles and the nameservers you would like to use.

We will process the rest of the transfer for you.

Additional notes on a .co.id transfer

If your customer does not have a local presence, you may use our trustee service.
The trustee service requires a power of attorney document that must be signed by the owner - you will get further details upon transfer start.
Authorization code required yes
Method of confirmation authcode
Registration period after transfer
Average transfer time Unknown
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .co.id domains is available.

Owner change (trade)

A trade is currently not available for .co.id domain names.

Other update

To update the contact details associated with a domain name you can modify the contact handles linked to the domain and it will be updated.


You can delete a domain name by letting it expire at the end of the registration period or by deleting it manually.

Restore / reactivate

Reactivating a .co.id is unfortunately not possible.
Domain lifecycle
Technical information
  • Available second level domains: .or.id, .web.id
  • DNSSEC support: no
  • Min: 3
  • Max: 63
  • Alphanumeric and a hyphen except in the first or last position
  • IDN: No
  • Registration period: 1-2 years
  • 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.
  • Local presence required? yes
  • Does Openprovider provide local presence services? yes
  • Local activity required? yes
  • Correct nameserver configuration required? no
  • Copy of business license (NPWP)
  • Copy of identity card (KTP)
  • Local address of the domain owner is required.
  • Local address of the domain administrator is required.
  • Trustee services are available for .co.id and .web.id (but not for .or.id), and are subject to additional costs (USD 219) per period on top of renewal costs.
  • A copy of trademark documentation or commercial license is required.
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