What is an AuthCode? And what can I do with it?
An AuthInfo code is necessary for the transfer of a domain in almost all domain extensions. The AuthCode confirms to the new provider that you are authorized to transfer this specific domain.
Please note that an AuthInfo code can lose its validity, for example, if changes are made to the holder’s manager. For .de domains, AuthCodes are generally only valid for 30 days. In such cases, a new AuthInfo code may need to be generated.
For already deleted domains, no AuthInfo code can be created. In this case, the domain must first be restored, which generally incurs restoration fees.
To find out how to generate an AuthInfo code for domains managed by hosting.fr in the client portal, please refer to the support article “Where can I find my AuthCode?”.
An AuthInfo Code for transferring your domain to hosting.fr is generally provided by your old provider, either automatically via the respective client interface or directly by the provider’s support.
Only a few domain extensions such as .pl or .es follow a different transfer process without an AuthCode. If you are unsure or need more information, please contact hosting.fr support at support@hosting.fr for advice on the steps to follow.
Where the AuthCode is used in the transfer process
An AuthCode is one element within a broader domain transfer process. Understanding the sequence helps you avoid generating the code too early, missing validity windows, or expecting immediate completion after entering the code. In most cases, the flow looks like this: you prepare the domain for transfer, obtain or generate the AuthCode at the current provider, initiate the transfer at the new provider using that code, and then complete any required confirmations until the registry finalizes the move.
A practical end-to-end overview:
- Prepare: confirm the domain is transferable, and that the owner/contact details are correct and accessible for confirmations.
- Obtain the AuthCode: generated at the current provider for outgoing transfers, or requested from the previous provider for incoming transfers to hosting.fr.
- Start the transfer by entering the AuthCode at the new provider to request the transfer.
- Confirm when required: some transfers require additional confirmation steps; others complete automatically after a waiting period.
- Finalize: once completed, DNS and associated services must be reviewed to ensure the domain resolves as intended.
This overview reduces confusion by making it clear that an AuthCode enables the transfer request, but it is not the only step involved in completing a transfer.
AuthCode validity and rejection reasons
AuthCodes are not always “good forever.” Even if you copy the code correctly, it may be rejected if the registry or provider no longer considers it valid. The original article notes a key example: specific domain changes, such as changes to the owner handle/contact, can cause an AuthCode to lose validity and require a new one.
Common validity risks to be aware of:
- Contact or owner data changes: if the registrant/owner contact is updated, previously issued codes may become invalid.
- Expiry of the code: for some domain endings (such as .de), AuthCodes have a limited validity period and must be regenerated if the transfer is not initiated in time.
- Copy/paste errors: extra spaces or missing characters can cause rejections. Always copy the code exactly as displayed.
- Wrong code for the domain: AuthCodes are domain-specific. Using a code from another domain will fail.
If a transfer fails with an “invalid AuthCode” message, the fastest fix is typically to generate a fresh AuthCode and retry, after confirming that no recent changes have introduced a transfer restriction.
Special cases: deleted domains, restored domains, and timing risks
AuthCodes cannot be created for domains that are already deleted. If a domain has been deleted, it must generally be restored first before you can generate an AuthCode and initiate a transfer. Restoration can involve additional costs and may be subject to time constraints depending on the domain’s lifecycle stage (for example, redemption periods).
Operationally, this creates a timing risk: if you wait too long after deletion, restoration may no longer be possible, or the domain may become available for re-registration by someone else. If your goal is to transfer a domain, do not cancel/delete it first. Treat transfers as a controlled migration process: keep the domain active, generate the AuthCode, and start the transfer while the domain is still in good standing.
If you discover the domain is already deleted, the correct order is:
- Restore the domain (if possible).
- Confirm the domain is active again.
- Generate a new AuthCode.
- Initiate the transfer at the new provider.
This sequence avoids wasted attempts and reduces the chance of losing control of the domain due to lifecycle deadlines.
Incoming vs outgoing transfer: where to get the AuthCode and who provides it
A common source of confusion is who is responsible for providing the AuthCode. The rule is straightforward: the AuthCode is obtained from the provider that currently manages the domain.
- Outgoing transfer away from hosting.fr: you generate the AuthCode in the hosting.fr customer portal and provide it to the new registrar.
- Incoming transfer to hosting.fr: You obtain the AuthCode from your current/previous provider and then enter it during the transfer process at hosting.fr.
This distinction matters because the receiving registrar cannot generate the AuthCode for you. They can accept the transfer request only after you provide the valid code. If you are transferring multiple domains, you must request or generate an AuthCode for each domain individually and ensure you submit the correct code with the proper domain.
Understanding who provides the code and when to request it helps prevent delays and reduce transfer failures caused by missing or invalid credentials.