Requesting a transfer code: Securely moving your domain

If you want to transfer a domain from CURIAWEB to another provider, you will often need a so-called transfer code. Depending on the domain extension and registrar, this code may also be referred to as an Auth Code, EPP Code or authorisation code. It serves as a security credential and confirms that the domain transfer has actually been initiated by the authorised domain holder or by an authorised person.

The transfer code can be understood as a kind of “password” for the domain transfer. Without this code, a new provider usually cannot start or successfully complete the transfer of a domain. For this reason, the code should be treated confidentially and only passed on to the provider to which the domain is actually being transferred.

In brief: What is the transfer code needed for?

The transfer code authorises the transfer of a domain to another registrar or hosting provider. It protects your domain from being transferred without consent. The new provider requires this code in order to initiate the domain transfer technically and administratively.

Why is the transfer code not displayed directly in the client area?

To protect against unauthorised domain takeovers, the transfer code is not displayed directly in the CURIAWEB client area. This procedure increases the security of your domain, as possible access to the client area alone is not automatically sufficient to transfer a domain away.

Domains are often a central part of the digital identity of a company, association or private project. Websites, email addresses, online shops, customer portals and many other services can depend on a domain. If a domain falls into the wrong hands, this can have serious consequences – such as loss of website availability, disruption of email traffic or misuse by third parties.

The manual review of a transfer code request is therefore not intended to make the domain transfer unnecessarily difficult, but to protect your internet address from unauthorised or accidental transfers.

How to request the transfer code

If you need the transfer code for your domain, you can request it via a support ticket in the CURIAWEB client area.

Procedure overview:

  1. Log in to the CURIAWEB client area.
  2. Open a new support ticket.
  3. Specify the exact domain for which you require the transfer code.
  4. Our team will review the request.
  5. For security reasons, the transfer code will be sent to the registered domain holder email address within a few hours.

Please make sure to provide the full domain in the ticket, for example yourdomain.ch or yourdomain.com. This allows the request to be clearly assigned and processed more quickly.

Why is the code sent to the registered domain holder email address?

Sending the code to the registered domain holder email address is an additional security mechanism. It ensures that sensitive information is not simply sent to any contact address, but to the address associated with the domain holder.

Before requesting the transfer code, you should therefore check whether the registered domain holder email address is still up to date and whether you have access to it. If this address is no longer accessible, delivery of the transfer code or further processing may be delayed.

Check the Registrar Lock before transferring

Some domains may have a so-called Registrar Lock or Transfer Lock enabled. This lock prevents a domain from being transferred to another provider without prior release. It is an additional protection against unwanted domain transfers.

If a Registrar Lock exists for your domain, it must be disabled before the transfer. Otherwise, the new provider may be able to start the transfer, but it may not be completed successfully. Whether such protection is active and how it can be removed depends on the respective domain extension and the technical management of the domain.

Important: Only disable a Registrar Lock if you actually want to carry out the domain transfer. As long as no transfer is planned, the lock can provide additional protection for your domain.

What should you consider before a domain transfer?

A domain transfer primarily affects the management of the domain at the registrar. Depending on how your services are configured, however, a transfer may have an impact on DNS settings, name servers, email services or the availability of your website. Before moving the domain, therefore check whether your DNS zone, name servers and email settings have been correctly prepared at the new provider.

This is particularly important if you use active email addresses, Microsoft 365, Google Workspace, external mail servers, subdomains or special DNS records such as SPF, DKIM, DMARC, MX, CNAME or TXT. If these settings are not correctly transferred or prepared at the new provider, interruptions to your website or email may occur after the transfer.

The transfer code itself does not change any DNS settings. It only enables authorisation of the domain transfer. Nevertheless, proper technical preparation at the destination provider remains important so that your services continue to function correctly after the transfer.

Handling the transfer code securely

Treat the transfer code confidentially. Only pass it on to the provider to which you actually want to transfer your domain. Do not send the code to uninvolved third parties and never publish it in publicly accessible areas.

If you no longer wish to carry out the transfer, you should not continue to use or pass on the code. If you are unsure whether a transfer request is legitimate, contact CURIAWEB Support before disclosing the code.

Summary

The transfer code, also known as an Auth Code or EPP Code, is required to transfer a domain to another provider. For security reasons, this code is not displayed directly in the CURIAWEB client area, but is requested via a support ticket. After the request has been reviewed, the code is sent within a few hours to the registered domain holder email address. Before transferring, also check whether a Registrar Lock exists and whether DNS, email and name server settings have been correctly prepared at the new provider.

Was this answer helpful? 0 Users Found This Useful (0 Votes)