This article describes the procedures and requirements of .tf domain names.
Click on the subject below to open the dropdown for more information.
Successful domain registration requires:
- Registrant contact require:
- Located within the EU, Iceland, Liechtenstein, Norway, Switzerland or any of the French overseas territories.
- For private individual
- the date, place and country of birth (hidden in whois)
- the date, place and country of birth (hidden in whois)
- Technical contact must be a company
- two or more nameservers or a nameserver group
If you use are French resident, please besides the date of birth and birth country, complete handle with
- birth city
- birth postal code
The registry will preform checks on the requirements above and contact the registrant in case the requirements are not met to ask for proof of identification data. (For example, the registrant seems to have an address outside the EU).
Proof of identification data contains:
- Business registration certificate
- The ID of the legal representative of the company
Registry AFNIC maintains a list of domain names to the "reserved" status, for example town and community names. Unfortunately we cannot see this status until the registration request, that will fail with a "2304, Object status prohibits operation" error.
Reserved domain names can be registered if the registrant has a legitimate interest, for example if the name is his company name. Please contact us in such case. The list is available at AFNIC's website.
You can start a .tf domain transfer through our API or control panel. This transfer requires the following information:
- an authorisation code that you need to request at your current provider.
- a registrant that resides in the EU, Iceland, Liechtenstein, Norway, Switzerland or any of the French overseas territories.
- an admin contact handle
- a tech contact handle - this can not be a person, but needs to be a company handle
- two or more nameservers or a nameserver group
Once the transfer is started, it will be finished in maximum 22 days:
- if the current registrar approves the transfer, the transfer will complete immediately;
- if the current registrar does not approve nor reject the transfer, the transfer will complete after 8 days;
- if the current registrar rejects the transfer within the first 8 days, the transfer will still complete automatically after 22 days.
If the domain holder wants to cancel an initiated transfer, only the gaining registrar (Openprovider, through you as a reseller) can do so; you can cancel the transfer from the transfer queue in your control panel. The registration period after a successful transfer restarts. The registry will not send an e-mail to the domain contacts after the transfer finishes.
Additional notes on a .tf transfer
-
Authorization code required | yes |
Method of confirmation | authcode |
Registration period after transfer | extends |
Average transfer time | 8-22 days |
Advanced and simple transfers available | Contact our Sales department to check if easy transfer of 100 or more .tf domains is available. |
Owner change (trade)
An owner change can be performed by updating the owner handle of the domain. This change is processed realtime.
Other update
An contact update can be performed by updating the handle of the domain. This change is processed realtime.
Delete
A domain can be deleted by either manually removing it from your control panel or setting it to not be automatically renwed. When a domain is set it to not be automatically renewed, our system will delete the domain on its expiration date.
Restore / reactivate
A domain name can be restored during its quarantine period (also called redemptionPeriod). Under 'detailed TLD information' below you can find how long a domain stays in its quarantine period after the domain name has been deleted or expired.
Registry |
|
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.