This article describes the procedures and requirements of .tel 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*
* ICANN contact verification email is sent from an alternative email address - noreply@emailverification.info
This verification is not processed by Openprovider, but its' partner. Therefore the verification status in Openprovider panel does not apply.
Successful domain transfer via RCP or API requires:
- authorisation code
- two or more nameservers or a nameserver group
- registrant e-mail address verification applies
During the transfer period which can take 6 days, the current provider or the owner can reject to the transfer.
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.
Problems transferring your domain?
Please take a look at this extended article for possible solutions.
Authorization code required | yes |
Method of confirmation | authcode |
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 .tel 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*
* ICANN contactverification email is sent from an alternative emailaddress - noreply@emailverification.info
This verification is not processed by Openprovider, but its' partner. Therefore the verification status in Openprovider panel does not apply.
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.
Note that if you want to update the data inside a handle, you will instead have to create a new handle and assign that to the domain name: the .tel registry does not support handle updates.
If you have registered your .tel domain before the 13th of March 2017, you can use the TelHosting platform in order to manage the contact data on your .tel domain. Access the TelHosting platform through managemy.tel.
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
Registry |
|
Domain lifecycle | |
Technical information |
|
Restrictions |
|
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.