This article describes the procedures and requirements of .com domain names.
Click on the subject below to open the dropdown for more information.
Successful domain registration via RCP or XML API or REST API requires:
- two or more nameservers or a nameserver group
- registrant e-mail address verification applies
Tip: Did you know that registry Verisign also offers the following internationalized variants of .com?
- .コム (Japanese)
- .קוֹם (Hebrew)
- .닷컴 (Korean)
Important: As a rule, Verisign’s registries reject the commingling of code points from different Unicode scripts. That is, if an IDN contains code points from two or more Unicode scripts, then that IDN registration is rejected. For example, a character from the Latin script cannot be used in the same IDN label with any Cyrillic character. All code points within an IDN label must come from the same Unicode script. This is done to prevent confusable code points of different scripts from appearing in the same IDN. Please refer to Verisign IDN policy (3. Restrictions on Commingling of Scripts) for more information.
Successful domain transfer via RCP or XML API or REST 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,email |
Registration period after transfer | extends |
Average transfer time | 6 days |
Advanced and simple transfers available | Contact our Sales department to check if easy transfer of 100 or more .com domains is available. |
- External authorization code request - via RCP (Reseller Control Panel) or XML API or REST API
If the domain is already expired, the transfer cannot be pushed, so you will need to wait the Average Transfer Time which is 6 days.
Owner change (trade)
- requested as a normal domain update via RCP or XML API or REST 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
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 XML API or REST API
- Processed realtime
- Soft Quarantine & Hard Quarantine doesn't apply. If you wish to restore an explicitly deleted .com domain, please contact our Support Team to check if your domain could be restored manually.
Expiration
In case the domain expires (not renewed in time);
- Will lead to 5 days of Soft Quarantine
- Hard Quarantine does not apply.
Restore / reactivate
- Restore - via RCP or XML API or REST API
- Soft Quarantine Period is 5 days and there is no Hard Quarantine.
- If you wish to restore a .com domain after the 5 days of Soft Quarantine, please contact our Support Team to check if your domain can be restored manually.
- Restore + Renew Charges will apply (VAT included)
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.