21.07.2026
Technologies & CMS

AuthInfo code, unlocking, timescales by extension (.fr, .com, .eu) and DNS and email precautions: the complete procedure for transferring a domain name to another registrar without interrupting your services.

Transferring a domain name means moving its management from one registrar to another provider. This operation usually requires an authorisation code, called an AuthInfo or EPP code, and a few preliminary checks.
A transfer makes it possible in particular to group several domain names with the same provider, change provider or take back direct management of a domain previously administered by a third party.
But be careful: transferring a domain name does not necessarily mean moving your website or email addresses. These operations are separate and must be coordinated to avoid interruptions.
How do you get the transfer code? What steps should you follow? How long should you allow for a .fr, .com or .eu domain?
ID Interactive is a digital agency based in Arradon, near Vannes (Morbihan), since 2006, and a Google Partner, Meta Business Partner and Shopify Partner. It supports companies with their web projects and the technical operations involved in managing their sites.
Discover the procedure for transferring your domain name and the precautions to take before you start.
A domain name is an internet address, such as example.fr or example.com, registered for a fixed period.
In particular, it associates a memorable address with a website and email services.
Several parties are involved in managing it.
The holder, also called the registrant, is the individual or legal entity in whose name the domain is registered.
They hold the contractual rights associated with this registration for the agreed period, subject to compliance with the applicable rules.
For a company, it is important that the holder is the legal entity or person who should actually control the domain.
The registrar is the provider with which the domain name is registered and managed.
It may be OVHcloud, Gandi, IONOS or another registrar accredited to offer the extension concerned.
The registrar handles the administrative and technical operations related to registration: renewal, holder contact details, transfer and management of certain domain settings.
The registry manages the domain names of one or more extensions.
For example:
ICANN coordinates in particular the policies applicable to generic extensions. Afnic and EURid have specific procedures for the extensions they manage.
To understand how to choose extensions, also see ID Interactive's article on domain name extensions.
Before doing anything, three operations need to be distinguished.
These operations can be carried out separately or as part of the same project.
For example, a company redesigning its site can change hosting while keeping the same registrar.
Conversely, a company can transfer its domain to another registrar without changing its site's hosting.
This distinction is essential to avoid needlessly changing DNS servers or email services.
The transfer must be prepared from the current registrar's account.
Before you start, check the following points.
Make sure the declared holder is your company or the person authorised to manage the domain.
This check is particularly important when a domain name was originally bought by an agency, an employee or a contractor.
Changing technical provider does not automatically change the holder's identity.
Check the expiry date and the status of the domain.
An expired domain cannot always be transferred immediately. The options depend in particular on its status and the applicable renewal or restoration procedures.
It is better to plan the transfer before the expiry date rather than launch it in a hurry.
For generic extensions subject to ICANN policies, restrictions may apply in particular:
In the latter case, some registrars may offer an option to avoid the lock, provided it is chosen before the change concerned.
A simple annual renewal does not automatically trigger a new 60-day transfer ban.
The specific rules of some national extensions may be different.
You must be able to receive security and transfer notifications.
Check in particular the email address registered with the registrar, the holder's contact details and access to the admin account.
Since 28 January 2025, the RDAP protocol has become the reference for looking up registration data for generic extensions, replacing the old mandatory Whois services.
Some personal information may be hidden in public results.
You should therefore not rely solely on a public directory to check the contact details used during the transfer.
Warning: changing certain holder contact details just before a transfer can trigger a lock period for domains covered by ICANN rules.
Start by selecting the registrar that will manage the domain from now on.
Before choosing, compare:
For a company with several domains, centralisation can simplify administration, provided access rights remain secure.
Before the transfer, identify the DNS servers in use and back up the necessary records.
The main records to examine include:
SPF, DKIM and DMARC rely in particular on DNS records, often of the TXT type.
This backup is particularly important if the DNS servers also need to change.
Some registrars protect domains against unauthorised transfers by enabling a lock.
For generic extensions, this lock may appear as the clientTransferProhibited status.
It can usually be disabled from the admin interface, when the transfer is allowed.
If you do not have this option, contact the current registrar.
For domains subject to ICANN policy, the registrar must comply with the obligations applicable to removing the lock.
Do not confuse this administrative lock with the domain's DNS settings.
The AuthInfo code is an authorisation code used to secure the transfer.
It may be called:
It is usually available in the current registrar's account.
For generic domains governed by ICANN, if the code cannot be generated directly in the interface, the registrar must provide it within five calendar days of the request.
For .fr domains, Afnic states that providing the AuthInfo code is free of charge.
This code must be treated as sensitive information.
Never publish your AuthInfo code in an article, a forum or a publicly accessible document. Only send it through an appropriate channel to the gaining registrar or to an expressly authorised provider.
Log in to the new provider's account.
Look for the "Transfer a domain" function or its equivalent.
Enter the domain name concerned, then the AuthInfo code requested.
The new registrar checks the information and submits the request to the registry concerned.
Depending on the extension and the provider, you may need to accept the transfer terms, pay the applicable fees or confirm certain operations.
Once the request has been submitted, watch for notifications from the new and the old registrar.
Validation procedures differ between extensions.
You should not assume that a lack of response always means every request is approved.
Once the transfer is confirmed:
The transfer is only considered operationally complete after these checks.
.fr domains are managed by Afnic.
To change registrar, the procedure mainly involves getting the AuthInfo code from the losing registrar, then passing it on to the new registrar.
The new registrar then submits the request to Afnic.
According to Afnic's procedure, the losing registrar normally has eight days to respond to the transfer notification.
It can approve the request quickly.
If there is no response, the transfer takes place at the end of the set period.
Some opposition situations can extend the procedure.
The actual duration therefore depends on how the request is processed and on particular circumstances.
Getting the AuthInfo code is free.
However, the transfer operation at the new registrar may be charged according to its commercial terms.
The transfer may also change the domain's expiry date, depending on the applicable rules.
For the detailed procedure, see the official Afnic documentation.
Generic extensions such as .com and .net are governed by the transfer rules coordinated by ICANN.
The process involves checking the domain's eligibility, removing any locks, getting the AuthInfo code and starting the transfer from the gaining registrar.
In standard procedures, a transfer can be processed within a few days.
ICANN rules provide in particular for a processing time of up to five calendar days in common situations, subject to the authorised reasons for refusal and the validation steps.
This processing time should be distinguished from the 60-day lock periods, which are eligibility restrictions.
After a transfer, a new restriction period on transfers between registrars may apply.
Start by identifying the reason given.
Some refusals may be justified, in particular where there is a lock, a dispute or a regulatory restriction.
However, if you believe the registrar is not complying with the applicable policy, you can use ICANN's complaint procedures.
The ICANN documentation on transfers details holders' rights and the reasons for refusal.
.eu domain names are managed by EURid.
The transfer requires a specific authorisation code, also called a Transfer Authorisation Code.
The code can be obtained from the current registrar.
Under certain conditions, EURid also lets you generate it from its "My .eu account" interface.
The code has 16 characters and follows a specific structure.
It is valid for 40 days or until it is used.
As a last resort, procedures allow an emergency code to be obtained from EURid, provided the request is justified.
The holder then passes the code on to the new registrar.
To find out more, see the official EURid instructions.
The price depends mainly on the extension and the new registrar.
Three items need to be distinguished.
Some transfers include an extension of the registration; others follow different rules.
You should also check whether additional services are included: DNS management, technical support or account protection.
Don't just compare the transfer price. The renewal price and the conditions for operating the domain are just as important.
This is one of the main precautions to take when changing registrar.
The administrative transfer does not automatically require the DNS servers to be changed.
When the existing DNS configuration is kept, the site and email can usually keep working without any interruption caused by the change of registrar.
However, changing DNS or hosting at the same time can cause problems if it is poorly prepared.
Before the transfer, check whether the new registrar can keep the name servers already in use.
If the DNS remains hosted by an independent provider, no zone migration is needed in some configurations.
However, if the DNS zone is hosted in a service linked to the losing registrar, make sure it will remain available after the transfer.
Do not assume DNS services will be maintained without confirmation.
When the DNS servers need to change, first copy the necessary records to the new servers.
Check the IP addresses, subdomains, email and other services.
DNS changes can take time to become visible, depending on caches and TTL values.
However, propagation is not a required step of a simple administrative transfer when the DNS servers and their configuration remain unchanged.
A company may use addresses such as [email protected] or [email protected].
These services depend in particular on MX records and the settings associated with email.
Before any switchover, check:
Deleting or misconfiguring these records can prevent messages from being received or disrupt their authentication.
If DNSSEC is enabled, the migration must also preserve consistency between the DNS server configuration and the delegation records, in particular the DS records.
An incorrect configuration can cause domain resolution errors.
This point requires particular attention when changing DNS provider.
No.
It may be better to carry out the domain transfer and the site migration separately, to limit simultaneous changes.
For a business website with many services, a gradual migration generally makes checks and diagnosis easier if an incident occurs.
Several causes can block a transfer request.
The losing registrar must comply with the rules applicable to the extension.
For generic domains under ICANN, certain obligations govern in particular the provision of the AuthInfo code and the removal of a lock.
If the problem persists, keep your exchanges with the provider and ask for a written explanation of the block.
In most cases, the transfer code is available in the registrar's admin interface.
When it is not accessible, contacting customer support is generally the first step.
Here is a template to customise.
Subject: Request for AuthInfo code and unlocking — [domain name]
Hello,
I would like to transfer the domain name [example.fr], currently managed by your services, to another registrar.
As the holder or a duly authorised representative of the holder, I would be grateful if you could:
I remain available to carry out the necessary identity checks through your secure procedure.
Please send me the information needed to complete this operation.
Kind regards,
[First and last name]
[Company]
[Contact details]
Tip: do not include a password or AuthInfo code in a message sent to unauthorised recipients. Use the secure transfer and sharing procedures provided by the providers.
To avoid oversights, here are the main checks to carry out.
This checklist is particularly important for a domain associated with a commercial activity, an e-commerce site or several business applications.
Transferring a domain name is generally a relatively simple administrative operation.
However, when it concerns a company website, it may require technical checks to maintain access to the site, email services and applications.
ID Interactive can help companies analyse their web environment and coordinate the necessary work with the providers concerned.
This process may include in particular:
The goal is to distinguish the operations that are strictly necessary from those that can be carried out later.
Planning a change of registrar as part of creating or redesigning your site? You can contact ID Interactive to present your situation and identify the work required.
To transfer a domain name, start by checking that you are the holder or authorised to act, and that the domain can be transferred.
Then choose a new registrar, get the AuthInfo code and submit the request to the new provider.
Timescales and procedures depend on the extension concerned: .fr, .com, .net and .eu do not follow exactly the same rules.
Finally, keep existing DNS services where possible and check that the site, email and applications work after the operation.
A domain name transfer should not be confused with a hosting migration. The two operations can be carried out independently, which makes technical risks easier to control.
Article originally published on 16 May 2011.
Le code AuthInfo, aussi appelé Auth-Code, code EPP ou code d’autorisation de transfert, sert à sécuriser le transfert d’un nom de domaine. Il est généralement disponible dans le compte du registrar actuel. C’est une information sensible : il ne se publie jamais et se transmet uniquement au registrar entrant ou à un prestataire expressément autorisé.
Le titulaire (registrant), c’est-à-dire la personne physique ou morale au nom de laquelle le domaine est enregistré, ou son représentant dûment autorisé. Si le domaine a été acheté par une agence, un salarié ou un prestataire, le titulaire déclaré peut différer de l’entreprise : cette vérification précède toute demande de transfert.
Certains registrars activent un verrouillage contre les transferts non autorisés ; pour les extensions génériques, il apparaît sous le statut clientTransferProhibited. Il se désactive généralement depuis l’interface d’administration du registrar actuel, sinon en le contactant. Ce blocage administratif ne doit pas être confondu avec les paramètres DNS, et il est à réactiver après le transfert.
Cela dépend de l’extension et du registrar : certains transferts incluent une prolongation de l’enregistrement, d’autres suivent des règles différentes, et le transfert d’un .fr peut aussi modifier la date d’expiration selon les règles applicables. Après le transfert, il faut vérifier la nouvelle échéance et les conditions de renouvellement automatique.
Un code incorrect figure parmi les causes d’échec : il faut générer ou demander un nouveau code. Il convient aussi de vérifier que le domaine n’est pas verrouillé et qu’aucune restriction ne s’applique (création ou transfert récent, changement récent de titulaire). En cas de difficulté persistante, conserver les échanges avec le prestataire et demander une explication écrite.