Can a Domain Transfer Be Prohibited?
Author: Domeny.ForSale editorial team Published
In brief: Yes, a domain transfer can be temporarily blocked or prohibited, but the reason should be grounded in the rules for its extension, the domain’s status or legal restrictions. Not every registrar’s refusal is justified, and the rules for .com do not automatically apply to .pl. First establish whether you mean changing registrars, changing the registrant or moving a website—these are different operations.
What does a domain transfer mean?
A domain transfer usually means changing registrars: the company that handles the domain’s registration and renewals. A registry, by contrast, is the organisation that manages an entire extension, such as NASK for .pl. The registrant is the person or entity entitled to use the domain under the terms of the agreement.
Changing registrars is not the same as changing the registrant, commonly referred to as selling or assigning a domain. Nor does it mean moving website files, mailboxes or a database to another hosting provider. These tasks can be carried out together, but each has its own procedure.
This distinction matters in practice: a restriction on changing the registrant does not always prevent a change of registrar. Similarly, a working website does not prove that its domain can currently be transferred—services may continue to operate despite an administrative lock.
When might a lock be justified?
The most common reasons for restrictions are protection against unauthorised domain takeovers, an inability to verify the applicant’s authority, and particular stages in the domain’s lifecycle. A domain dispute, a court ruling or an applicable dispute resolution procedure may also be relevant.
Many generic domains, such as .com, are subject to the transfer policy of ICANN, the organisation that coordinates, among other things, the rules governing these domains. This policy includes restrictions during the first 60 days after registration and for a period following a previous transfer. Changes to registrant details may also trigger a 60-day lock, depending on the type of change and the available procedure for opting out of that lock.
However, these rules should not be treated as universal. Country-code domains, such as .pl, have their own regulations. Before changing details or starting a transfer, check the current ICANN policy applicable to the domain or its registry’s rules.
The domain’s status is also useful. clientTransferProhibited means that the registrar has set a transfer lock, often as a security measure that the registrant can disable through the control panel or support team. serverTransferProhibited indicates a lock imposed by the registry; removing it usually requires resolving the underlying reason, rather than simply changing a setting in the control panel.
How can you check the rules for .pl and .com?
For .pl, check the procedures for transferring a domain and issuing the AuthInfo code in the current materials from NASK and the instructions provided by both registrars. AuthInfo is an authorisation code used to approve a transfer. Receiving the code alone does not establish that all conditions for transferring the domain have been met.
For .com, check the current ICANN transfer policy, the domain’s status, and the dates of registration, its most recent transfer and any changes to registrant details. Also establish what authorisation method the new registrar requires. Button labels and messages in control panels may differ even when they refer to the same action.
For example, a .com domain was registered three weeks ago, and the registrant wants to move it to a cheaper provider. A refusal may stem from the transfer restriction during the first 60 days, rather than a commercial decision by the current company. If a similar situation involves .pl, citing this ICANN rule alone is not enough—the applicable basis for refusing a .pl transfer must be identified.
What should you do if the registrar refuses?
Ask for a written explanation of the refusal, its basis in the terms and conditions or registry policy, and the conditions for unlocking the domain. A message saying “transfer unavailable” does not tell you whether the problem is technical, procedural or legal.
Then work through this short checklist:
- Confirm that you are applying as the registrant or an authorised person.
- Check the domain’s status and the dates of any actions that may have triggered a lock.
- Verify that you have access to the account and the contact details needed for authorisation.
- Establish whether the domain is subject to a dispute or is at a particular stage of the expiry process.
- Compare the reason given for the refusal with the relevant registry’s current rules.
Outstanding payments require a separate assessment. You cannot assume that every unpaid invoice entitles a registrar to withhold a domain transfer; the type of debt and the applicable policy matter. Similarly, a promotional hosting agreement does not, in itself, explain why a technical domain transfer should be prohibited, although it may involve separate financial obligations.
If the explanation remains inconsistent with the rules, submit a complaint to the registrar. The next steps depend on the extension: domains covered by ICANN policy may have a transfer complaint procedure available, while for .pl you should check the appropriate way to contact NASK. This is general procedural information, not an individual legal assessment of an agreement or dispute.
How can you avoid service interruptions?
Do not start a transfer at the last moment before the domain expires. Expiry does not always automatically rule out a transfer, but later stages of the lifecycle may require the domain to be restored first. You need to confirm the exact process and costs for the extension concerned.
Before changing registrars, save the DNS configuration—the records that direct traffic to your website and email services. Check whether the current company will continue to operate the DNS servers after the transfer; do not assume that the service will remain active indefinitely.
The best first step is to get a specific answer: what is blocking the transfer, and what needs to be done to remove the obstacle. Only then decide whether unlocking the domain, waiting for the specified period or submitting a complaint will resolve the issue.
See also: What is Java?
Read also
