Domain Ownership Transfer: What Clients Need to Know Before Requesting a Handover
A domain name is one of the most important digital assets for any business. It represents your website address, brand identity, business email identity, online credibility, and sometimes years of marketing history.
When a client requests a domain ownership transfer, the process may sound simple: “Please give me my domain.” However, a domain transfer is not always the same as handing over a password or sending a login link.
In many cases, a domain may be registered or managed through a website designer, digital agency, hosting provider, freelancer, IT vendor, or reseller account. This means the transfer may involve registrar-level verification, account control, domain unlock, Auth/EPP code generation, DNS checks, renewal status checks, and administrative responsibility.
This article explains the most common questions clients ask when requesting a domain ownership transfer.
What is a domain ownership transfer?
A domain ownership transfer is the process of moving control of a domain name from one person, company, registrar account, or management account to another.
This may involve updating the domain owner details, moving the domain into the client’s own account, or transferring the domain to a different registrar such as GoDaddy, Namecheap, SiteGround, Cloudflare, Exabytes, or another provider.
In simple terms, it means making sure the rightful business owner has direct administrative control over the domain.
Is domain ownership the same as website ownership?
No. Domain ownership and website ownership are separate.
The domain is the website address, such as example.com. The website is the actual collection of files, pages, database, content, design, forms, and functionality hosted on a server.
A domain transfer does not automatically include:
- website files
- hosting access
- cPanel access
- email accounts
- webmail access
- website backups
- DNS management
- website maintenance
- plugin or CMS support
- troubleshooting or recovery
A client may own the domain but still need separate access or support for hosting, email, website files, or maintenance.
Is the current website designer or agency disputing ownership of the domain?
Usually, no.
In many domain transfer cases, the issue is not about disputing ownership. The matter usually relates to registrar account control, verification, and official procedure.
If a domain is currently registered or managed under a website designer’s, agency’s, hosting provider’s, or reseller’s account, certain actions can only be performed by the account holder of record.
These may include:
- registrant updates
- domain unlock
- Auth/EPP code requests
- transfer approvals
- administrative changes
- contact updates
- DNS or nameserver changes
The purpose of the process is to ensure the domain transfer is handled properly, securely, and with the correct verification.
Why can’t a domain be released informally?
A domain cannot be released informally because domain transfer is a sensitive administrative action.
A domain name can control a company’s website, email, leads, traffic, search presence, brand reputation, and digital identity. If a domain is released without proper verification, it could result in business disruption, unauthorized transfer, or loss of control.
Even for a simple “release-only” request, proper checks are usually required before any action is taken.
These checks may include:
- verifying the requester
- checking domain status
- checking renewal status
- confirming whether there are outstanding dues
- checking whether the domain is locked, expired, suspended, or restricted
- confirming the receiving registrar details
- coordinating with the registrar or hosting provider
- ensuring DNS or nameserver settings are not accidentally disrupted
This is why domain release should be handled as an official process, not an informal handover.
What does “release-only” mean?
A release-only domain handover means the client is not asking for full website support, hosting migration, email migration, or ongoing maintenance. The request is limited to domain administrative release.
Depending on the registrar and domain status, release-only may include:
- domain ownership or registrant update
- domain unlock
- Auth/EPP code request
- registrar coordination
- transfer-out approval
- confirmation once the transfer is initiated or completed
Release-only usually does not include website repair, hosting troubleshooting, email setup, DNS migration, backups, or ongoing technical support.
Why is there sometimes a handling fee for domain release?
A handling fee may apply because domain release often requires administrative work, verification, registrar coordination, and responsibility from the account holder of record.
Even if the client only needs the domain released, the current manager may still need to:
- verify the request
- review domain status
- check billing and renewal records
- coordinate with the registrar
- request unlock or Auth/EPP code
- monitor the transfer window
- approve transfer requests where required
- confirm completion from their side
This is official domain administration work and may not always be processed as a free or informal task.
What must be done before a domain transfer can begin?
Before a domain transfer begins, the client should complete the required verification and provide the necessary ownership details.
The current domain manager may request a transfer verification form or written confirmation. This helps confirm who is requesting the transfer and what exactly needs to be transferred.
The client may also need to provide:
- full name or company name
- contact email
- phone number
- billing address
- receiving registrar name
- receiving account email
- whether only the domain is being transferred
- whether hosting, email, DNS, or website files are also required
Without these details, the process may be delayed.
Can a domain be transferred if renewal is pending?
In many cases, no.
If the domain is expired, suspended, locked, or has unpaid renewal dues, the registrar may not allow the transfer until the issue is resolved.
Before processing a transfer, the domain should usually be:
- active
- renewed where required
- not suspended
- not restricted
- not under dispute
- not blocked by registrar lock
- not pending deletion
If the domain needs to be renewed before transfer, renewal should normally be completed first.
What is an Auth Code or EPP Code?
An Auth Code, also known as an EPP Code, is a security code used to authorize a domain transfer from one registrar to another.
Think of it like a transfer password for the domain. The receiving registrar will usually ask for this code when the client starts the transfer process.
The Auth/EPP code should be treated as highly confidential. Anyone with access to this code may be able to initiate a domain transfer request.
When is an Auth/EPP code required?
An Auth/EPP code is usually required when the client wants to transfer the domain from the current registrar to another registrar.
For example, if the domain is currently managed under one registrar account and the client wants to move it to Namecheap, GoDaddy, SiteGround, Cloudflare, or another provider, an Auth/EPP code may be required.
However, if the domain is only being moved internally within the same registrar or provider, the process may instead involve an account push, ownership update, or registrant contact change.
The exact process depends on the registrar.
What is domain unlock?
Domain unlock means removing the registrar lock that prevents unauthorized transfer.
Most domains are locked by default for security reasons. Before a transfer-out can happen, the domain usually needs to be unlocked by the current account holder.
Once unlocked, the client can use the Auth/EPP code to initiate the transfer at the receiving registrar.
Does the domain unlock stay active forever?
No.
For security reasons, a domain unlock may only remain active for a limited window. If the transfer is not initiated within that time, the domain may need to be unlocked again.
This is why clients should be ready with their receiving registrar account before requesting the unlock and Auth/EPP code.
Which registrar should the client use?
The client can choose their preferred registrar.
Common options include:
- GoDaddy
- Namecheap
- SiteGround
- Cloudflare
- Exabytes
- any other trusted domain registrar
The client should confirm the receiving registrar before the transfer is initiated. This helps avoid delays and confusion.
What happens after payment or approval is completed?
Once verification and any required payment or approval are completed, the domain transfer process can begin.
The usual steps are:
- Domain status is checked.
- Registrar or hosting provider is contacted.
- Domain unlock is requested, if needed.
- Auth/EPP code is requested, if needed.
- The code is shared securely with the client.
- The client initiates the transfer from the receiving registrar.
- The current account holder approves or verifies the transfer where required.
- The client confirms once the domain appears in the new account.
The timeline depends on registrar working hours, approval windows, and transfer rules.
How long does a domain transfer take?
A release-only process may take a couple of working days depending on the registrar or hosting provider’s response time.
Some steps may be completed quickly, such as requesting unlock or generating an Auth/EPP code. However, the full transfer between registrars can sometimes take several days depending on the registrar and transfer approval process.
Clients should allow time for:
- verification
- payment or approval confirmation
- registrar response
- unlock approval
- Auth/EPP code issuance
- transfer initiation
- transfer approval
- final completion
What should the client do after receiving the Auth/EPP code?
Once the Auth/EPP code is received, the client should log in to their receiving registrar account and start a domain transfer request.
The receiving registrar will usually ask for:
- the domain name
- the Auth/EPP code
- payment for transfer or renewal, if applicable
- confirmation of registrant details
After initiating the transfer, the client should inform the current account holder so the transfer can be confirmed or approved from the current side where required.
Can DNS or website access be affected during transfer?
Yes, if not handled carefully.
A domain transfer does not always change DNS automatically, but mistakes during the process can affect website or email service if nameservers or DNS records are changed incorrectly.
Before transfer, it is recommended to save a copy of:
- nameservers
- A records
- CNAME records
- MX records
- TXT records
- SPF records
- DKIM records
- DMARC records
- subdomain records
If the nameservers remain the same, the website and email may continue working normally. If DNS is changed or not copied properly, downtime may occur.
Does domain transfer include email migration?
No, not automatically.
Domain transfer only moves domain ownership or registrar control. Email hosting is separate.
If the client uses email accounts such as name@example.com, those emails may be hosted through cPanel, Google Workspace, Microsoft 365, Zoho, SiteGround, SuezHost, or another provider.
If the client also needs email support, they should request it separately.
Email-related support may include:
- webmail access
- email password reset
- SMTP settings
- IMAP settings
- MX record check
- mailbox migration
- Google Workspace setup
- Microsoft 365 setup
- email backup
These are outside a basic release-only domain handover.
Does domain transfer include hosting or cPanel access?
No, not automatically.
Hosting is separate from the domain. A domain points visitors to a website, but hosting is where the actual website files, database, and email accounts may be stored.
If the client requires hosting or cPanel access, this should be confirmed separately from the domain transfer request.
Hosting support may include:
- cPanel login
- server login
- webmail login
- database access
- file manager access
- FTP access
- website backup
- migration support
- SSL check
- website troubleshooting
These are not part of domain release-only unless specifically included.
Does domain transfer include website maintenance?
No.
Domain transfer does not include ongoing website maintenance.
Website maintenance may include:
- CMS updates
- plugin updates
- theme updates
- malware checks
- uptime monitoring
- backups
- bug fixing
- broken form checks
- speed optimization
- security hardening
- content updates
If a client needs ongoing support after the domain transfer, they should activate a separate website support or maintenance plan.
What happens after the domain transfer is completed?
Once the domain transfer is completed, the receiving account holder becomes responsible for future domain management.
This includes:
- renewal
- billing
- registrar login
- DNS settings
- nameservers
- transfer lock
- contact details
- recovery email
- future Auth/EPP requests
- website/email pointing
- registrar support
After the handover, the previous account holder is generally no longer responsible for future domain, DNS, hosting, email, or website issues unless a separate support agreement is active.
Can the previous website designer, agency, or hosting provider still help after the transfer?
Yes, but post-transfer support is usually separate.
After the release-only scope is completed, any additional support may be treated as a separate paid service. This may include consultancy, DNS checks, email setup, hosting support, website troubleshooting, backup recovery, or migration assistance.
Clients who want ongoing support should consider an active maintenance or support plan.
What is the safest way to request a domain transfer?
The safest way is to follow a structured process:
- Submit the official transfer request or verification form.
- Confirm the exact domain name.
- Confirm whether the request is domain-only or includes hosting/email.
- Clear any pending invoices or renewal dues.
- Confirm the receiving registrar.
- Confirm the receiving account email.
- Wait for review and handling fee confirmation, if applicable.
- Complete payment or approval where required.
- Allow registrar coordination.
- Receive unlock/Auth-EPP details where applicable.
- Initiate transfer from the receiving registrar.
- Inform the current account holder once transfer is initiated.
- Confirm once the domain is fully received.
This protects both the client and the current account holder from mistakes, unauthorized release, or service disruption.
Final takeaway
Domain ownership transfer is not just a password handover. It is an official administrative process involving verification, registrar responsibility, security checks, and sometimes billing or renewal clearance.
A release-only domain transfer can be simple when the domain is active, verified, and ready to move. However, it still requires proper handling to avoid downtime, unauthorized transfer, DNS issues, or loss of access.
For a smooth transfer, clients should be clear about what they need: domain only, domain plus hosting, domain plus email, or full website migration. Each scope is different and should be handled separately.
The safest approach is to complete the verification process, confirm the transfer scope, clear any outstanding dues, and allow the current account holder to coordinate the release through the correct registrar process.
