1. Openprovider
  2. Domains
  3. Documentation per TLD

.is

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

Registration

Successful registration requires:

  • Nameservers and DNS zone compliant with ISNIC's technical requirements.
    • If test fails during the registration - nameservers are not applied to a domain
  • Nameserver and DNS zone setup can be validated via ISNIC validation tool
  • Openprovider's Nameservers CANNOT be used while registering .is domains.
Transfer
  • Transfer - via RCP or API. Process must be completed via Openprovider support
  • Openprovider support requires the login details (contact ID and password) of the current NIC admin contact handle to complete the transfer
  • Openprovider's Nameservers CANNOT be used while transferring .is domains.
Authorization code required no
Method of confirmation
Registration period after transfer restarts
Average transfer time Realtime
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .is domains is available.
Update

Owner change (trade)

  • Trade - via RCP or API, by updating the owner handle. Process is real-time

Other update

  • Handle updates - via RCP or API
  • DNS zone updates - via RCP and API. Not real-time. Update cna take 6-12 hours to complete
  • Nameserver updates - via RCP and API. Not real-time. Process is manual, can take up to 2 business days to complete
  • Openprovider's Nameservers CANNOT be used while updating .is domains.

NB: Error message like Domain update failed: E0102, Domain could not be updated., Identical task is already being processed means previous update is not finished yet

Deletion / Restore

Delete

Restore / reactivate

  • Restore - within 30 days after expiration
Detailed extension information
Registry
Technical information
  • DNSSEC support: no
  • Min: 1
  • Max: 63
  • Letters and numbers
  • IDN: supported characters: áéýúíóþæöð
  • Registration period: 1 year
  • 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: 30 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? yes
  • Nameservers must be configured and return an authoritative answer before the domain is requested.
  • NS records in the nameservers must have a TTL of at least 86.400 seconds (24 hours)
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