This article describes the procedures and requirements of .blog domain names.
Click on the subject below to open the dropdown for more information.
Successful domain registration requires:
- the domain's contact handles (owner, administrative, etc.)
- two or more nameservers or a nameserver group
Note that, as for ICANN's contact verification requirements, we are obliged to send an e-mail to the domain owner if his e-mail address was not verified before. Failure to respond to this e-mail may lead to suspension of any gTLD domain name with this same e-mail address in the owner contact.
IMPORTANT: If "Allocation Token" is requested during registration it means the domain is reserved by registry. Contact CentralNIC directly and ask if name could be released for you and under what conditions. If request approved, you will receive a token that can be used during the registration.
You can start the .blog main transfer through our API or RCP.
This transfer requires the following information:
- an authorization code that you need to request at your current provider.
- the domain's contact handles (owner, administrative, etc.)
- two or more nameservers or a nameserver group
A transfer for a .blog takes a maximum of 6 days to complete. The transfer can be rejected by the current provider or the owner of the domain during this period.
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.
| Authorization code required | yes |
| Method of confirmation | authcode,email |
| 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 .blog 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
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.
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.
