This article describes the procedures and requirements of .cz 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
Note: Registry could initiate a contact verification for some registrants.
Verification Process Overview
The process begins when CZ.NIC's internal checks or an external stimulus raise doubts about the data accuracy. Common reasons for a check include providing false or misleading details, such as:
- Using only a pseudonym, initials, or a clearly non-existent name (e.g., "Superhero," "Dr. House")
- Listing an address that is non-existent or conflicts with public records
The Procedure and Timeline
Request to verify details sent: The Contact receives the request to verify contact details via the registered email. The administrative contact is also notified.
Verification Action: The Contact must log into the Verification Portal and choose a method to verify their details.
Deadline and Communication: The verification process typically takes up to 45 days, though CZ.NIC can extend the deadline. Status updates are sent throughout the process.
Consequences of Failure: If verification fails, the domain's Delegation is cancelled (removed from the zone). This state lasts for approximately one month, after which the registration is permanently cancelled. When the contact fails to verify, it is automatically set to the state "serverLinkProhibited - Contact linking forbidden" so the contact cannot be linked to any object (domains, nameservers etc..). If domains are transferred to another contact during the verification process, a new verification is initiated on the new contact.
Successful domain transfer via RCP or API requires:
- authorisation code
- two or more nameservers or a nameserver group
A transfer is realtime. The registration period after a successful transfer will not change.
Additional notes on a .cz transfer
- If the current registrar cannot or does not want to provide you with the authorization code of the domain name, you can also request this directly via the .CZ Registry website: https://www.nic.cz/whois/send-password/ .
| Authorization code required | yes |
| Method of confirmation | authcode |
| Registration period after transfer | unchanged |
| Average transfer time | Realtime |
| Advanced and simple transfers available | Contact our Sales department to check if easy transfer of 100 or more .cz domains is available. |
- External authorization code request - via RCP (Reseller Control Panel), or XML API or REST API or directly at the registry
- External authorization code delivery - sent by the .cz registry to the registrant, and if sending to a different email address is requested, the authorization of the person confirming the request is verified (via registry).
- External authorization code reset - via RCP (Reseller Control Panel), or XML API or REST API
- Authorization code validity - The validity of the transfer password (AuthInfo) is limited in time as per the registry.
Owner change (trade)
- Trade - via RCP or API, by updating the owner handle. Process is real-time
Other update
- Domain updates - via RCP or API. Processed real-time
Due to automatic cleanup processes of the Czech registry, sometimes a domain contact received an e-mail with subject "Oznámení o zrušení sady nameserverů ... / Notification of NS set ... deletion" or about the "Cancellation of the contact" which is not in use.
Such e-mail does not impact domain availability and can be ignored.
Delete
Explicit delete
- requested via RCP or API
- processed realtime
- will be available for new registration immediately (no quarantine or redemption period applies)
Expiration
In case the domain expires (not renewed in time):
- will lead to soft quarantine for 60 days, after which the domain is released for new registration
Restore / reactivate
- Restore / reactivation supported via RCP or API
- If 60 days of Soft Quarantine has passed, the domain can no longer be restored.
| 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.