This article describes the procedures and requirements of .zuerich 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
- The registrant must be a legal entity or a public authority with residence in the Canton of Zuerich.
- Natural persons cannot register a .zuerich domain.
- Legal entities have to provide their business registration number (UID).
- Domain names that have sexual connotations or are used to promote sexual activities are not allowed.
- Domain names that are offensive are not allowed.
- Manual verification is done by the registry.
- WHOIS Privacy Protection is not supported for this extension
The registry requires that the Registrant Information accurately reflect the entity in the name of which the domain has been registered.
Therefore, registrants of .zuerich are not permitted to utilise privacy or proxy registration services / fake details in registrant information, if such activity is detected, the registry will delete the domain within 24 hours of registration without a refund.
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,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 .zuerich 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.