If you want to transfer a domain from CURIAWEB to another provider, depending on the domain extension, you need a so-called Transfer code. This is also known as Auth Code, EPP code or authorization code.
The transfer code serves as a security feature for the domain transfer. The new registrar needs it to authorize and initiate the migration of the domain. Since this code enables the transfer of your domain, you should treat it confidentially and only share it with the provider to whom you actually want to transfer the domain.
What is a transfer code needed for? #
When changing a provider or registrar, it must be ensured that a domain cannot be transferred to another provider without authorization. The transfer code serves as a form of authorization.
Simply put, you can think of it as a one-time access code for the domain transfer. The exact transfer process and the necessary requirements can vary depending on the domain extension.
Important: Treat your transfer code like confidential access credentials. Only share it with the new registrar or provider if you actually intend to carry out the domain transfer.
How to request your transfer code on CURIAWEB #
You can request the transfer code for your domain via a support ticket in the CURIAWEB customer center.
- Log in to CURIAWEB Customer Center a.
- Create a new Support Ticket.
- State the full domain in the ticket for which you need the transfer code, for example your-domain.ch.
- Send the request to CURIAWEB support.
- We are reviewing the request and will provide you with the required transfer code.
Always provide the relevant domain in full. This facilitates clear assignment and prevents follow-up questions, especially if you manage multiple domains with CURIAWEB.
Why is the transfer code not simply displayed publicly? #
A transfer code is security-relevant information. Anyone who has a valid code can use it to initiate a domain transfer with another registrar under the respective conditions.
Domains are often a central component of the digital infrastructure of a company, organization, or private project. Websites, e-mail addresses, online shops, customer portals, and other services can be accessed via the domain.
An unauthorized domain transfer can therefore have significant consequences. The transfer code should be protected accordingly and not stored, forwarded, or transmitted to third parties unnecessarily.
Check your domain contact details before the transfer #
Before a planned domain transfer, you should check whether the contact details registered for your domain are up to date and, in particular, that you have access to the email address used.
Depending on the domain extension and the registrar involved, additional confirmations or notifications may be required during a transfer. An email address that is no longer accessible can therefore unnecessarily complicate or delay the process.
Note Registrar Lock or Transfer Lock #
For certain domains, a so-called Registrar Lock or Transfer Lock active. This lock prevents the domain from being transferred to another registrar without prior approval.
Whether such a transfer lock exists and what conditions apply to its removal depends, among other things, on the respective domain extension and the registrar.
Safety Notice: An existing transfer lock should only be removed if you actually want to perform a domain transfer. As long as no transfer is planned, the lock can provide additional protection against unwanted transfers.
What happens to the website and email during a domain transfer? #
The transfer code itself neither changes your website nor your DNS settings or email accounts. It initially only serves to authorize the transfer of the domain.
Nevertheless, you should prepare a domain transfer technically. It is particularly crucial to determine which nameservers and DNS settings will be used after the transfer.
Before moving, check in particular whether all required DNS records will still be present. These may include, for example:
- A and AAAA records for the accessibility of your website
- MX records for receiving emails
- SPF records for authorized email transmission
- DKIM records for email authentication
- DMARC records for handling incorrectly authenticated messages
- CNAME and TXT records for further services and verifications
- Entries for used subdomains
If you use external services like Microsoft 365, Google Workspace, or another mail provider, you should pay special attention to ensuring that the required DNS records remain correctly in place after the transfer.
Domain transfer and nameservers are not the same #
A common misconception is to equate a domain transfer with a change of nameservers. These are two different processes.
At Domain transfer the administration of the domain is being transferred to another registrar. The Nameserver determine, on the other hand, which DNS infrastructure is responsible for the domain.
Depending on the transfer and configuration, existing nameservers can continue to be used or changed. Therefore, clarify with the new provider before the transfer how DNS management should be handled after the move.
How to handle your auth code securely #
Only enter the transfer code where you actually requested the transfer of your domain. Do not publish it on a website, in a forum, or in any other publicly accessible place.
Do not forward a message containing the transfer code unnecessarily to additional people either. If a web designer or an agency is handling the domain transfer for you, the code should only be provided to the person responsible for it.
If you did not initiate a transfer request yourself or if a request seems suspicious to you, do not share any transfer code and clarify the matter with CURIAWEB support first.
Prepare the domain transfer completely before starting #
It is best to request the transfer code only when it has been decided where the domain is to be transferred and the necessary preparations have been made with the new provider.
Check the future DNS configuration in particular, as well as the entries required for the website and email. This reduces the risk that, although the domain was successfully transferred, individual services associated with it will no longer function as expected after the domain transfer.
