Transfers
Why a domain transfer can fail
A transfer can fail because the domain is locked, the Auth-Code is wrong, contact email is inaccessible, the domain is expired, data is inconsistent or the extension has special rules.
Reviewed:
Not every transfer is accepted
A domain transfer may look simple, but it depends on the registry, the current provider, the new provider and the domain status.
If a condition is not met, the transfer may stop or be rejected.
Common causes
The most frequent reasons are:
- domain locked against transfers;
- wrong or expired Auth-Code;
- inaccessible contact email;
- domain expired or in recovery;
- domain registered or transferred too recently;
- incomplete or inconsistent registrant data;
- extension with special requirements;
- transfer rejected by the registrant or current provider.
Not all extensions work the same way.
How to reduce the risk
Before starting the transfer:
- Check that the domain is active.
- Unlock it at the current provider.
- Request a recent Auth-Code.
- Check that the contact email works.
- Review whether web and email depend on current DNS.
This preparation avoids many incidents.
How PRIMARI.NET handles it
When a transfer to PRIMARI.NET fails or remains pending, the cause may come from the registry or current provider.
From Transfer domain, PRIMARI.NET collects and submits the request. If the registry returns an error, the cause must be corrected before trying again.
When to contact PRIMARI.NET
Contact PRIMARI.NET if you do not understand the error, if the domain is locked, if the Auth-Code does not work or if the transfer affects a critical domain with active web or email.