Si të Transferoni një Emër Domaini: Kriteret, Kodi EPP, Kohëzgjatja, Kostoja

Shikime:18 Koha:2026-08-19 18:12:40 Autori: windy

Last verified: August 2026

Transferring a domain name means moving its registration from one registrar to another. For most standard domain transfers, you first confirm that the domain is eligible, unlock it at the current registrar, obtain the authorization code, submit the transfer to the new registrar, and complete any required approval steps.
A registrar transfer normally changes where the domain is managed. It does not, by itself, mean that your website, hosting provider, email service, or DNS records must change.
The details matter, however. A transfer can be delayed or blocked by a 60-day restriction, registrar lock, incorrect authorization code, domain status, an unresolved dispute, or TLD-specific rules. Country-code domains can also use transfer procedures that differ from the standard gTLD process.
This guide explains what to check before transferring, what happens during the transfer, how long it can take, how transfer fees and renewal periods work, and how to reduce the risk of website or email interruption.

Quick Answer: How Do You Transfer a Domain?
For a standard registrar-to-registrar domain transfer:

• Confirm the domain is eligible to transfer.
• Check whether a 60-day transfer restriction applies.
• Unlock the domain at the current registrar.
• Obtain the Auth Code, EPP Code, AuthInfo Code, or transfer code.
• Check your DNS and email configuration before making other changes.
• Submit the transfer request to the new registrar.
• Complete any required authorization or approval.
• Monitor the transfer until it completes.
• After completion, confirm the registrar, expiration date, nameservers, DNS, email, DNSSEC, and contact settings.

If you already have an eligible domain and its authorization code, you can start a transfer through the NiceNIC Domain Transfer page.

What Actually Changes When You Transfer a Domain?
A domain transfer is often confused with changing hosting, changing nameservers, or moving a website.
They are different operations.
If your goal is simply to move the domain registration from Registrar A to Registrar B, you normally need a registrar transfer.
If your goal is to move your website to a different host while keeping the same registrar, you probably need a DNS or hosting change, not a registrar transfer.
If both people use the same registrar and you only need to move the domain between accounts, an account push may be the correct operation.
This distinction matters because many avoidable transfer problems begin when several different changes are made at the same time.

Before You Transfer: Domain Transfer Eligibility Checklist
Before paying for or submitting a transfer, check these items. If you are preparing a domain specifically for an incoming transfer to NiceNIC, see our step-by-step domain transfer instructions.
Do not assume that every extension follows the same transfer workflow.
The standard process described in this guide is most relevant to domains governed by ICANN's inter-registrar transfer framework. Some country-code registries use different authorization methods, registry contacts, account identifiers, IPS tags, registry handles, documentation, or manual procedures.

Step 1: Check Whether a 60-Day Transfer Restriction Applies
One of the most common reasons a domain cannot be transferred is a 60-day restriction.
Under ICANN's current Transfer Policy, a registrar may deny an inter-registrar transfer when the domain is within 60 days of its creation date or within 60 days of a previous inter-registrar transfer. A separate 60-day inter-registrar transfer lock can apply following a qualifying Change of Registrant.
A Change of Registrant can involve changes to the registrant:

• name;
• organization;
• email address; or
• Administrative Contact email address when no registrant email address exists.

Some registrars may allow the registrant to opt out of the Change of Registrant 60-day lock before the registrant change is completed. Registrars are not required to offer that option.
Practical rule
If you intend to both:

• change important registrant information; and
• transfer the domain to another registrar,

check the transfer implications before changing the registrant information.
ICANN itself recommends considering the transfer first when the ultimate goal is to move the domain to another registrar.

Step 2: Unlock the Domain
Domains are commonly protected with a registrar lock.
You may see a status such as:
clientTransferProhibited
This is normally a registrar-controlled transfer lock designed to prevent unauthorized transfers.
Before transferring, sign in to the current registrar and look for an option such as:

• Unlock Domain;
• Registrar Lock;
• Transfer Lock;
• Domain Lock; or
• Transfer Protection.

ICANN's Transfer Policy requires registrars to provide a reasonably accessible method for an authorized registrant to remove a registrant-requested transfer lock.
Do not confuse:
a registrar lock
with
an ICANN-policy 60-day restriction.
Removing clientTransferProhibited does not override a valid 60-day restriction.
It also does not override a registry-level status such as serverTransferProhibited.

Step 3: Get the Auth Code or EPP Code
For domains that use the standard authorization-code transfer process, you need a code from the current registrar.
It may be called:

• Auth Code;
• Authorization Code;
• EPP Code;
• AuthInfo Code;
• Auth-Info Code; or
• Transfer Code.

These names often refer to the transfer credential used to authorize the registrar change.
ICANN states that if the registrar does not provide a self-service method for generating the AuthInfo code, the registrar must provide it within five calendar days after the registrant requests it.
Before using the code
Check that:

• you requested it for the correct domain;
• you copied the complete code;
• no spaces were accidentally added;
• the registrar has not regenerated or invalidated it;
• the domain is unlocked;
• the TLD actually uses an Auth Code.

Treat the code like a sensitive credential.
Do not post it publicly or send it to anyone who is not involved in the authorized transfer.

Step 4: Check DNS, Website and Email Before the Transfer
A registrar transfer and a DNS change or account push are different operations.
In most cases, moving the registration to another registrar does not require changing the domain's existing nameservers.
That is why a properly prepared registrar transfer can normally take place without moving the website or email service.
The risk increases when the current registrar is also providing the DNS service.
Before the transfer, identify the authoritative nameservers and make sure you know where the DNS zone is hosted.
At minimum, record the DNS settings your services depend on.
Website records
Check:

• A;
• AAAA;
• CNAME;
• important TXT records.
• Email records

Check:

• MX;
• SPF;
• DKIM;
• DMARC;
• mail-related CNAME or verification records.

Other services
Also review:

• CAA;
• verification TXT records;
• subdomains;
• SRV records;
• custom application records.

DNS records determine how the domain connects users and services to the correct systems. Incorrect or missing records can make a website, application, or email service unavailable.

Safer migration principle
When possible, avoid combining all of these into one uncontrolled change:
registrar transfer + nameserver change + hosting migration + email migration
Making one controlled change at a time makes it much easier to identify and reverse a problem.

Step 5: Submit the Transfer to the Gaining Registrar
Once the domain is eligible, unlocked, and prepared, submit the transfer to the registrar you want to move to.
If you are transferring to NiceNIC, use the NiceNIC Domain Transfer page and enter the requested transfer information.
NiceNIC's current transfer workflow accepts a domain and authorization code and also provides a bulk transfer option for multiple domains.
For standard transfers, the gaining registrar initiates the process and the transfer then passes through the relevant registrar and registry workflow.
Depending on the TLD and current policy requirements, you may receive authorization or confirmation requests associated with the transfer.
Follow those instructions carefully.

Step 6: Monitor the Transfer Instead of Repeatedly Starting It Again
Once the transfer has been submitted successfully, do not repeatedly submit duplicate transfer orders unless the previous request has actually failed or been cancelled.
A transfer can pass through several states before completion.
For NiceNIC incoming transfers, the account currently shows transfer progress under domain management and can display a pending transfer state before completion.
If a transfer appears stuck, first identify:

1. whether the request reached the registry;
2. whether approval is still required;
3. whether the Auth Code was rejected;
4. whether a transfer lock still exists;
5. whether the registry has imposed a blocking status;
6. whether a TLD-specific process is required.

For a more detailed symptom-by-symptom diagnosis, use the Domain Transfer Troubleshooting Guide.
The useful question is not simply: Why is the transfer taking so long?
It is: Which transfer stage is currently incomplete, and who controls that stage?

How Long Does a Domain Transfer Take?
For many standard gTLD transfers, users commonly see completion within several days, and five to seven days is a commonly documented transfer window. Some transfers can complete sooner when the necessary approvals are made promptly.
However, there is no single completion time that applies to every TLD.
Transfer time can depend on:

• the registry;
• the losing registrar;
• the gaining registrar;
• authorization timing;
• the domain status;
• manual review;
• local registry requirements;
• documentation requirements;
• whether the TLD uses the standard EPP process.

Therefore:
“5–7 days” should be treated as a common standard-transfer expectation, not a universal promise.

Who Controls Each Part of a Domain Transfer?
This is why a support team at the gaining registrar may not be able to directly remove a lock imposed by the current registrar or a registry.
The fastest solution is usually to identify who controls the blocked step.

Will a Domain Transfer Affect Your Website?
Normally, not by itself.
A registrar transfer changes the company responsible for managing the domain registration.
Your website normally remains hosted where it already is.
If the domain continues using the same working nameservers and DNS records, website traffic can continue to resolve to the same server.
Problems are more likely when:

• the nameservers are also changed;
• the old registrar stops providing DNS after the transfer;
• DNS records were never copied to a new DNS provider;
• A, AAAA or CNAME records are wrong;
• the new web server has not been configured for the domain;
• DNSSEC is changed incorrectly.

Before transferring a business-critical domain, verify the DNS path rather than assuming that “domain transfer” and “website migration” are the same action.

Will a Domain Transfer Affect Your Email?
Again, normally not if the DNS remains intact.
Email delivery depends heavily on DNS records such as:

• MX;
• SPF;
• DKIM;
• DMARC.

If those records remain available at the authoritative DNS provider, changing the registrar does not automatically mean changing your email provider.
Email problems after a transfer usually indicate that another change occurred at the same time—for example, nameservers changed and the new DNS zone did not contain the necessary mail records.
For business domains, back up or document mail-related DNS records before making registrar or nameserver changes.

What Happens to the Domain's Expiration Date?
For many gTLD transfers, the transfer fee includes an extension of the domain's registration term.
But this should not be presented as a universal rule for every extension.
TLD rules can differ.
There is also an important timing issue for some domains that:

1. expired;
2. were renewed at the previous registrar; and
3. are then transferred shortly after that renewal.

In some circumstances, a transfer during the applicable auto-renew grace period may not produce the additional year a user expects. Major registrars document the commonly encountered 45-day scenario for affected domains.
Before transferring immediately after renewing an expired domain, check:

• the TLD's registry policy;
• the current expiration date;
• whether the previous renewal occurred after expiration;
• the gaining registrar's transfer-term rules.

For NiceNIC, use the current Domain Pricing page to check the applicable transfer price and term for the extension before ordering.

How Much Does a Domain Transfer Cost?
There is no universal domain transfer price.
The cost depends on:

• TLD;
• registry wholesale price;
• transfer term;
• whether the TLD adds a renewal period;
• Premium status;
• registry-specific rules;
• registrar pricing.

Do not assume that:
registration price = renewal price = transfer price.
Check the current transfer price for the exact extension before submitting the transfer.
For NiceNIC, the current transfer price can be checked through the domain pricing and transfer pages.

Can You Transfer an Expired Domain?
Sometimes, yes.
Expiration by itself is not always enough to prevent an inter-registrar transfer. ICANN's Transfer Policy limits the circumstances in which transfers may be denied.
The important question is the domain's actual lifecycle status.
Country-code TLDs can follow different lifecycle and transfer rules.
Always check the specific extension before acting.

Why Does a Domain Transfer Fail?
Most failures can be diagnosed by checking the domain's status and the step where the transfer stopped.
If you already have a failed or pending transfer, work through the transfer troubleshooting checklist before submitting another request.
Common causes include:
ICANN also lists specific circumstances in which a registrar may or must deny an inter-registrar transfer, including fraud concerns, identity disputes, certain unpaid prior registration charges, an express registrant objection, applicable 60-day restrictions, UDRP/URS proceedings, court orders and transfer disputes.

clientTransferProhibited vs serverTransferProhibited
These two statuses should not be treated as the same problem.
clientTransferProhibited
Usually indicates a registrar-level transfer lock.
The registrant may often be able to remove it through the current registrar.
serverTransferProhibited
Usually indicates a registry-level restriction.
This generally cannot be removed simply by clicking “Unlock Domain” in the registrar control panel.
The registrar may need to investigate or communicate with the registry.
This distinction can save considerable troubleshooting time.

Do All TLDs Use an EPP Code?
No.
Many gTLDs and numerous ccTLDs use an authorization-code workflow, but not every TLD uses exactly the same transfer procedure.
Examples of variations can include:

• registry account or handle systems;
• IPS tags;
• manual registry approval;
• registrant documentation;
• local contact requirements;
• different authorization formats;
• no conventional EPP/Auth Code.

Before publishing or following transfer instructions for a specific ccTLD, check the registry's current rules.
A generic .COM transfer workflow should never be assumed to apply unchanged to every country-code extension.

Should You Change Nameservers During the Transfer?
Usually, the safest approach is:
If the current DNS is working, do not change it merely because you are changing registrars.
If you also need to move DNS, hosting, or email, decide whether those changes should happen before or after the registrar transfer.
NiceNIC's current incoming-transfer guidance advises customers who need urgent DNS changes to make them before initiating the transfer, because nameserver changes may not be available during the pending transfer workflow.
For a business-critical domain, document the current DNS configuration first.

A Safer Zero-Downtime Transfer Checklist
Before the transfer:

• confirm eligibility;
• check registration and previous-transfer dates;
• check whether a Change of Registrant lock applies;
• unlock the domain;
• obtain the Auth Code;
• identify authoritative nameservers;
• record important DNS entries;
• verify MX, SPF, DKIM and DMARC;
• confirm website hosting;
• review DNSSEC;
• check expiration status;
• check TLD-specific requirements;
• confirm the transfer price.

During the transfer:

• do not make unrelated changes without a reason;
• monitor the transfer status;
• complete required approvals promptly;
• do not repeatedly submit duplicate transfers;
• keep current DNS service active.

After the transfer:

• confirm the new registrar;
• confirm the expiration date;
• confirm nameservers;
• verify website resolution;
• send and receive test email;
• check DNSSEC;
• review WHOIS/RDAP contact information;
• enable appropriate account security;
• review renewal settings.

Transferring One Domain vs Hundreds of Domains
The basic rules remain similar, but the operational risk changes substantially when moving a portfolio.
For one domain, you can manually check:

• lock;
• Auth Code;
• expiration;
• DNS;
• approval.

For 100, 500 or more domains, that same process needs to become a structured migration workflow.
A bulk migration should normally include:

1. domain inventory;
2. TLD grouping;
3. expiration-date review;
4. eligibility screening;
5. Auth Code collection;
6. DNS and email backup;
7. exception-TLD identification;
8. transfer-price review;
9. staged submission;
10. failed-transfer queue;
11. post-transfer audit.

If you are moving a portfolio, follow NiceNIC's bulk domain transfer process to prepare each domain and its Auth Code correctly.
For larger portfolios, operational planning matters as much as the transfer form itself.

When Should You Transfer a Domain?
A transfer may make sense when you want:

• clearer long-term pricing;
• easier portfolio management;
• better bulk tools;
• API or reseller integration;
• different payment options;
• stronger account-management controls;
• consolidated renewals;
• access to support better suited to your use case.

But transferring simply because another registrar advertises a lower first-year price may not improve your long-term cost.
Compare:
registration + transfer + renewal + privacy + redemption + operational cost
rather than only the initial transfer price.

When Should You Not Start a Transfer Yet?
Delay the transfer and investigate first if:

• the domain has an unresolved eligibility restriction;
• you have just changed registrant information and a lock may apply;
• you cannot obtain the Auth Code;
• the domain has a registry-level transfer restriction;
• you do not understand where DNS is currently hosted;
• the domain is in redemption;
• an important website/email migration is already in progress;
• the TLD uses a special transfer procedure you have not verified;
• the domain is involved in an active dispute or legal restriction.

The goal is not to start the transfer as quickly as possible.
The goal is to start it when the domain is actually ready.

How to Transfer a Domain to NiceNIC
For an eligible domain using a standard authorization-code transfer:
Step 1
Unlock the domain at your current registrar.
Step 2
Request the current Auth/EPP Code.
Step 3
Review the current nameservers and important DNS records.
Step 4
Go to the NiceNIC Domain Transfer page.
Step 5
Enter the domain and requested authorization information.
Step 6
Review the applicable transfer price and term.
Step 7
Submit the order and complete any required authorization.
Step 8
Monitor the transfer status from your NiceNIC account.
NiceNIC's current account workflow allows incoming transfers to be monitored from the domain-management area, including pending and completed states.
If you manage many domains, use the bulk transfer workflow rather than submitting hundreds of individual forms.

Frequently Asked Questions
1. Can I transfer a domain immediately after registering it?
For domains governed by ICANN's Transfer Policy, a registrar may deny an inter-registrar transfer during the first 60 days after the domain's creation.
2. Can I transfer a domain immediately after transferring it once already?
A registrar may deny another inter-registrar transfer within 60 days of the previous transfer, subject to the applicable policy.
3. Does changing contact information create a 60-day lock?
A qualifying Change of Registrant can create a 60-day inter-registrar transfer lock. Relevant changes include the registrant name, organization or email address, or the Administrative Contact email when no registrant email exists. Some registrars may offer an opt-out before the change.
4. Can ICANN remove my 60-day lock?
No. ICANN explains that it does not place or lift the domain's 60-day lock. The applicable registrar process and Transfer Policy determine the restriction.
5. How do I get my EPP/Auth Code?
Check your current registrar's control panel first. If it is not available through a self-service tool, request it from the registrar. Under the ICANN Transfer Policy framework, the registrar must provide the AuthInfo code within five calendar days of the request.
6. Will a domain transfer change my nameservers?
A registrar transfer does not inherently require a nameserver change. Keep the working nameservers in place unless you intentionally need to move DNS.
7. Will my website go offline?
Normally not if the existing DNS and hosting remain correctly configured. Downtime risk rises when DNS, nameservers or hosting are changed at the same time.
8. Will my email stop working?
Normally not if the authoritative DNS continues serving the correct MX and related email records.
9. How long does a transfer take?
Many standard transfers complete within several days, with five to seven days being a commonly documented range. Some can finish sooner after prompt approval; TLD-specific processes can take different amounts of time.
10. Does a transfer add one year to my domain?
Many gTLD transfers include an extension of the registration term, but this is not universal. TLD rules and timing can affect the result. Always check the current transfer terms for the exact extension before ordering.
11. Can I transfer an expired domain?
Possibly. Expiration alone does not automatically mean every transfer is prohibited. The actual lifecycle state—such as expired grace, redemption or pending delete—and the TLD's rules determine what is possible.
12. Can I transfer hundreds of domains at once?
Yes, if the gaining registrar provides bulk-transfer functionality and the individual domains meet their transfer requirements. NiceNIC currently allows up to 500 domains in a single bulk-transfer submission.

The Most Important Rule Before Moving a Domain
A successful transfer begins by separating four questions:

• Where is the domain registered?
• Where is DNS hosted?
• Where is the website hosted?
• Where is email hosted?

Those services can all be provided by different companies.
Once you know which part you actually want to move, the transfer becomes much easier to plan—and much easier to troubleshoot.
If your goal is to move the registrar, prepare the domain first, keep working DNS stable where possible, verify the TLD-specific rules, and then submit the transfer.

Start a domain transfer: NiceNIC Domain Transfer
Transfer multiple domains: NiceNIC Bulk Domain Transfer
Check current transfer pricing: NiceNIC Domain Pricing
Need help with a blocked transfer: NiceNIC Support

How Domain Transfers Work (And How to Avoid Common Problems)

Domain Transfer Guide：How to Transfer Your Domain Smoothly and Securely

How Domain Transfer Works

Domain Transfer | Quickly and easily transfer your domain to Nicenic

Why Domain Transfers Fail and How to Fix Them

Lajmet e Ardhshme: NiceNIC shqyrtimi i sigurisë për 50 domenet e UNC6671 nga Google