Transfer process guide
A domain transfer is a handover, not a single button.
Ownership, registrar location and DNS are related, but they are not the same thing. This guide shows which part changes at each stage and what the buyer should verify before moving on.
Keep these five points.
- An internal account push and a registrar-to-registrar transfer follow different routes.
- A domain can change owner without changing nameservers or taking the website offline.
- Transfer locks and registry rules can create legitimate delays; document them early.
- The buyer account should be secured before an authorization code or push is accepted.
- The process ends when the buyer controls the domain and verifies renewal and DNS settings.
What changes during a domain transfer?
A transfer changes who controls the domain or which registrar manages it. It does not automatically move the website, email inboxes, files or company. DNS can stay unchanged while registrar control moves to the buyer.
This distinction prevents unnecessary downtime. A domain is the registered address; DNS tells the internet where services live; hosting stores the site; email providers handle mail. Moving one layer does not require moving all four on the same day.
Before starting, write down the current registrar, nameservers, important DNS records and intended destination account. If the domain has no live service, the plan can be simple. If it carries email or a website, preserving the DNS configuration becomes a separate checklist item.
What information should the buyer prepare?
Prepare a destination registrar account, a working account email, strong authentication and the exact account identifier required for a push. Decide which person or legal entity should hold the domain before the seller initiates anything.
Use an organisational email address when the domain belongs to a company, but avoid creating a circular dependency where the only recovery address uses the domain being transferred. Keep a tested recovery method outside that domain until control and email are stable.
Provide only the information needed for the selected route. An internal push may require a customer number or account email. A registrar transfer normally uses an authorization code supplied by the current registrar. Passwords and one-time login codes should not be shared with the seller.
When is an internal registrar push better?
An internal push can be faster when buyer and seller use the same registrar. The domain changes accounts without moving to another registrar, so it may avoid some external transfer steps. The exact workflow still depends on the provider.
The seller initiates the move using the buyer's account identifier, and the buyer accepts if the registrar requires confirmation. Check whether contact data, privacy settings or nameservers will be copied. Do not assume that every setting follows the domain automatically.
After acceptance, the buyer should log in through the registrar's normal address—not a link forwarded by an unknown party—and verify that the domain appears in the correct account. Renewal billing and security settings then become the buyer's responsibility.
How does a registrar-to-registrar transfer work?
The current registrar unlocks the domain and issues an authorization code. The buyer starts a transfer at the destination registrar, enters the exact domain and code, then follows confirmation requests from the registrars or registry.
The authorization code is sensitive because it helps approve the move. Send it only through the agreed transaction channel and enter it at the destination registrar. If a code is unexpectedly rejected, ask the current registrar to issue or confirm it rather than repeatedly guessing.
Some transfers include an additional registration year; others behave differently by extension. Fees, renewal effects and supported extensions belong to the destination registrar's current terms. Check those terms instead of assuming that a rule for .com applies to every country-code domain.
Why can a transfer be locked or delayed?
A registrar or registry may apply locks after certain registrations, transfers or contact changes, or when a dispute or security review is active. A lock is a status to investigate, not proof by itself that the seller cannot deliver.
Ask for the lock reason and the earliest eligible date. The public registration lookup may show status codes, while the registrar account gives the owner more specific guidance. Do not ask someone to bypass a security control; adjust the documented delivery schedule instead.
Country-code extensions may use local procedures, trustee rules or registry portals. The responsible approach is to follow the rule for the exact extension. A seller should not promise a universal number of hours when the registry controls part of the timeline.
How do you keep the website and email online?
Keep nameservers and DNS records unchanged during the ownership move unless a planned migration requires a change. Registrar transfer and DNS migration can be separate maintenance events, which makes failures easier to diagnose.
Before changing DNS, save the existing A, AAAA, CNAME, MX, TXT and verification records. Email needs particular care because SPF, DKIM and DMARC records may not be visible in a simple website checklist. Lowering TTL in advance can help a planned move, but it is not a substitute for copying the right records.
After any DNS change, test the apex domain, www host, HTTPS certificate, incoming mail and outgoing authentication. A page loading successfully does not prove that email or every subdomain works. Keep the old hosting active until the agreed verification window has passed.
How do you verify final buyer control?
Log in to the destination registrar and confirm the domain is listed in the intended account. Verify the expiration date, auto-renewal choice, nameservers, security lock, recovery methods and any organisation access rules.
Save the payment invoice and registrar confirmation together. If the buyer is a company, record who has administrative access and how recovery works. Avoid leaving the only control with a freelancer, former employee or personal email that the organisation cannot recover.
Finally, check the public domain and services from outside the registrar dashboard. Confirm that HTTPS and DNS resolve as intended. The handover can be marked complete only when the commercial record and technical control agree.
Official starting points
Rules and database interfaces change. Use the current official source for the exact extension and market involved.
Quick answers
Questions buyers ask before they commit.
How long does a domain transfer take?
An internal registrar push may complete quickly, while an external transfer can take several days. Extension rules, locks and confirmation timing can change the result.
Will a domain transfer take my website offline?
Not by itself. If nameservers remain unchanged, the existing website and email can continue operating. Downtime usually comes from an unplanned DNS or hosting change.
What is a domain authorization code?
It is a code issued by the current registrar to help approve a registrar-to-registrar transfer. Treat it as sensitive transaction information.
Does the buyer need the seller's registrar password?
No. A legitimate push or transfer uses account identifiers, approvals or an authorization code. The seller should not hand over a full registrar login.