domaindetails.com
Knowledge Base/Domain Management/How to Change Domain Registrant (Transfer Ownership) (2025)
Domain Management

How to Change Domain Registrant (Transfer Ownership) (2025)

Step-by-step guide to changing domain ownership/registrant. Covers the 60-day lock implications, verification requirements, and registrar-specific processes.

14 min
Published 2025-12-01
Updated 2025-12-01
By DomainDetails Team

Quick Answer

To change a domain's owner (registrant), log into your registrar account, navigate to domain management, update the registrant contact fields (name, organization, or email), and complete the required email verification from both the old and new registrant. Warning: Changing the registrant name, organization, or email triggers a 60-day transfer lock on gTLDs under ICANN policy, preventing you from transferring the domain to another registrar during that period. Many registrars allow you to opt out of this lock before making changes---use this option if you need to transfer soon after the ownership change.

Table of Contents

When Do You Need to Change Domain Ownership?

Changing the domain registrant (owner) is required in several common scenarios:

Domain Sale or Purchase

When selling a domain, the registrant contact must be updated to reflect the new owner. This is a formal "Change of Registrant" (CoR) that legally transfers ownership rights.

Process for sales:

  1. Agree on sale terms with buyer
  2. Use escrow service for payment protection (recommended)
  3. Update registrant information to buyer's details
  4. Complete verification process
  5. Optionally transfer to buyer's preferred registrar

Business Entity Changes

Company restructuring:

  • Merger or acquisition (Company A buys Company B's domains)
  • Parent company taking over subsidiary's domains
  • Spinning off a division with its domains

Business name change:

  • Legal entity renamed (e.g., "ABC Corp" to "XYZ Corp")
  • Rebranding effort requiring updated registrant

Important change for August 2025: Starting August 21, 2025, if the "Organization" field contains a company name, ICANN will recognize that organization as the legal domain owner. The individual listed becomes merely a contact person, not the owner. This makes accurate organization field data more critical than ever.

Fixing Registration Errors

Common errors that need correction:

  • Typos in registrant name
  • Wrong organization name
  • Outdated email address
  • Employee registered domain under personal name instead of company

Personal Life Changes

  • Name change due to marriage or divorce
  • Moving from personal to business ownership
  • Transferring to a family member

Employee Departure

When the person who registered the domain leaves the organization:

  1. Update registrant to company-controlled contact
  2. Change from employee's personal email to company email
  3. Ensure organization field shows company name

Understanding the 60-Day Transfer Lock

ICANN's Transfer Policy requires registrars to impose a 60-day lock preventing inter-registrar transfers after certain registrant changes. This policy went into effect December 1, 2016, and remains active through 2025.

Why the Lock Exists

The 60-day lock is a fraud prevention measure designed to protect domain owners:

Scenario the lock prevents:

  1. Attacker compromises your registrar account
  2. Changes registrant email to attacker's email
  3. Immediately initiates transfer to their registrar
  4. Original owner loses domain before noticing

With the 60-day lock:

  • Contact changes trigger the lock
  • Original owner has 60 days to notice unauthorized changes
  • Transfer is blocked, giving time to recover the domain

Which Domains Are Affected

gTLDs (Generic Top-Level Domains) - AFFECTED:

  • .com, .net, .org, .info, .biz
  • New gTLDs: .io, .co, .app, .dev, .xyz, .online, .store, etc.

ccTLDs (Country-Code Domains) - NOT AFFECTED by ICANN policy:

  • .uk (uses IPS tag system)
  • .eu, .de, .ca, .au, .us, .in, .fr, .nl
  • These follow their national registry rules instead

The Future: ICANN May Eliminate the 60-Day Lock

At ICANN 82 in Seattle (late 2024), the GNSO Council voted to accept recommendations that include eliminating the 60-day transfer lock entirely. However, this change won't take effect immediately:

  • GNSO Council approved recommendations in late 2024
  • Must go to ICANN Board for final approval
  • Policy drafting and registrar implementation follow
  • Earliest implementation: 2026 or later

For 2025: Current 60-day policies remain fully in effect. Plan accordingly.

What Triggers the Lock vs What Doesn't

Understanding exactly which changes trigger the 60-day lock helps you plan updates strategically.

Changes That TRIGGER the 60-Day Lock

Field Changed Lock Triggered?
Registrant Name Yes
Organization Name Yes
Registrant Email Yes
Admin Contact Email (if no registrant email) Yes

Examples:

Changes That DO NOT Trigger the Lock

Field Changed Lock Triggered?
Physical Address No
Phone Number No
Billing Contact No
Technical Contact No
Admin Contact (except email in some cases) No
Nameservers No
DNS Records No
WHOIS Privacy Settings No

You can safely update these without triggering a transfer restriction:

  • Update your mailing address
  • Change phone numbers
  • Modify billing contact details
  • Update technical contact information
  • Switch DNS providers or nameservers

Multiple Changes Strategy

If you need to change triggering AND non-triggering fields:

Recommended order:

  1. Make non-triggering changes first (address, phone)
  2. Then make triggering changes (name, email) all at once
  3. This way you only trigger one 60-day lock period

Not recommended:

  • Making registrant email change today
  • Making registrant name change in 2 weeks
  • This could extend/restart the lock period

How to Opt Out of the 60-Day Lock

ICANN allows registrars to offer registrants the option to opt out of the 60-day lock when making registrant changes. This is optional for registrars---they may choose not to offer it.

Critical Timing

You must opt out BEFORE making the change. You cannot retroactively remove a lock already in place.

Correct process:

  1. Find opt-out option in registrar settings
  2. Select opt-out checkbox
  3. THEN make your registrant changes
  4. Complete verification
  5. Domain remains transfer-eligible

Incorrect (won't work):

  1. Make registrant changes
  2. Try to find opt-out option
  3. Lock already applied---too late

When to Use Opt-Out

Use opt-out when:

  • Selling a domain and buyer wants to transfer to their registrar
  • Planning to consolidate domains at a new registrar soon
  • Updating for legitimate business reasons with no fraud concern
  • You have strong account security (2FA enabled)

Keep the lock when:

  • No immediate plans to transfer
  • Security is more important than flexibility
  • Domain is high-value or business-critical
  • Account security is uncertain

Security Trade-offs

Risks of opting out:

  • Attacker who gains account access can change ownership AND transfer immediately
  • Less time to notice and respond to compromises
  • Reduced protection window

Mitigate risks by:

Registrar-Specific Processes

Each registrar implements ownership changes slightly differently. Here's how to change registrant at major registrars:

GoDaddy

Change of Registrant Process:

  1. Go to your GoDaddy Domain Portfolio
  2. Select the domain to access Domain Settings
  3. Select "Edit" next to Contact Info
  4. Enter the new registrant details
  5. When Domain Privacy is OFF, you'll receive an approval email

60-Day Lock Opt-Out: When approving changes, GoDaddy offers two options:

  • "Lock domain transfers for 60 days" (domain locked)
  • "Do not lock domain transfers for 60 days" (no restrictions)

Transfer to Another GoDaddy Account:

  1. Go to Domain Settings
  2. Under Transfer section, select "Transfer to another GoDaddy account"
  3. Enter recipient's email address
  4. Recipient has 10 days to accept

Important: Domains bundled cannot be transferred within 120 days of new registration.

August 2025 change: GoDaddy announced that effective August 21, 2025, only Registrant contact details will be required and publicly displayed for most domains.

Namecheap

Change Ownership Between Accounts:

  1. Go to Domain List and click "Manage" next to your domain
  2. Navigate to "Sharing & Transfer" tab
  3. Find "Change Ownership" section
  4. Enter the new owner's email address or Namecheap username
  5. Fill in your account password for authorization
  6. Select "Registrant Contact" in the modal window
  7. New owner receives an invitation email to approve

Key benefits:

  • Process is free of charge
  • No 60-day wait to move between Namecheap accounts
  • DNS settings are preserved (no downtime)
  • Cannot move expired domains (renew first)

Special TLDs: For .asia, .au, .ca, .ch, .de, .tel, .es, .eu, .fr, .is, .li, .nl, .nu, .nyc, .sg, .uk, and .us domains, choose "Use Current Contacts" as these may have Extended Attributes or registry restrictions.

Opt-Out: Available during contact changes in domain settings.

Cloudflare Registrar

Update Registrant Contact:

  1. In Cloudflare dashboard, go to "Manage domains"
  2. Find "Default contact" and select "Edit"
  3. Update relevant information, select "Save"
  4. Or: Select specific domain > "Manage" > "Contacts" tab > Edit

Change of Registrant Approval: If you change name, organization, or email, Cloudflare sends an approval email to the current registrant. Both old and new email addresses must approve if email changes.

60-Day Lock Opt-Out:

  • Select "Accept" to approve with 60-day lock
  • Select "Do not apply 60 day transfer lock" checkbox to opt out
  • Only the current registrant can opt out (new registrant's approval page won't show this option)

Important: If registrant contact is updated again while in the 60-day lock period, the lock expiration extends another 60 days from the most recent update.

Dynadot

Change Ownership (Domain Push):

Initiated by current owner:

  1. Sign in and select "My Domains" > "Manage Domains"
  2. Check the domain(s) you want to move
  3. Select "Change Account" from the "Action" drop-down
  4. Enter Recipient Push Username
  5. Recipient receives email to confirm

Initiated by recipient (Domain Pull):

  1. Owner unlocks domain and confirms it's not expiring
  2. Recipient goes to Change Domain Ownership page
  3. Submits domain pull order
  4. Owner receives authorization email
  5. Once authorized, domain moves automatically

60-Day Lock Opt-Out: Dynadot allows opting out when updating WHOIS information. Select the opt-out option before making changes.

Notes:

  • Custom DNS settings don't carry over between accounts (unless moving to sub-account)
  • Domain pushes allowed even within 60 days of registration (just can't transfer to another registrar)

Comparison Table

Registrar Opt-Out Available Cost Within-Account Transfer Notes
GoDaddy Yes Free Yes (10-day window) Bundles locked 120 days
Namecheap Yes Free Yes (instant if auto-accept on) DNS preserved
Cloudflare Yes Free Requires support Only current registrant can opt out
Dynadot Yes Free Yes (push or pull) Custom DNS not preserved
DNSimple No Free Contact support Cannot opt out of lock
NameSilo Yes Free Yes Clear interface
Porkbun Yes (case-by-case) Free Contact support May require support

Required Verification Steps

ICANN mandates verification when changing registrant information to prevent unauthorized ownership transfers.

The Dual Verification Process

When you change registrant details (especially email), verification typically requires confirmation from both parties:

Step 1: Notification to Current Email

  • Registrar sends alert to the original registrant email
  • Confirms someone is attempting to change ownership
  • May include option to reject unauthorized changes

Step 2: Confirmation to New Email

  • Registrar sends verification to the new registrant email
  • Link must be clicked to confirm new owner accepts
  • Some registrars require explicit approval

Step 3: Final Confirmation

  • Both approvals processed
  • Changes take effect
  • 60-day lock applied (unless opted out)

Verification Timeline

Stage Timeline Action Required
Email sent Immediate to few hours Check both email addresses
Approval deadline 14 days Click verification links
WHOIS update 24-48 hours after approval Verify changes propagated
60-day lock Starts at approval Cannot transfer to another registrar

What Happens If Verification Fails

If old registrant doesn't approve:

  • Changes may be rejected
  • Domain stays with original owner
  • Legitimate sales/transfers blocked

If new registrant doesn't approve:

  • Transfer incomplete
  • May need to restart process
  • Changes reverted at some registrars

If no one responds in 14-15 days:

  • Depends on registrar policy
  • Some revert changes
  • Some may suspend domain
  • Contact registrar support

Avoiding Verification Problems

Before initiating change:

  • Confirm access to current registrant email
  • Verify new registrant email is correct (no typos)
  • Check spam folders for verification emails
  • Add registrar to email safelist

Common issues:

  • Verification email in spam folder
  • Old email no longer accessible
  • Typo in new email address
  • Corporate email filters blocking messages

Corporate vs Personal Registrant Considerations

The type of registrant (individual vs organization) has important legal and practical implications.

Registering as an Individual

When appropriate:

  • Personal blog or portfolio
  • Side project domains
  • Domains you own personally, not through a business

Registrant fields:

Registrant Name: John Smith
Organization: (blank)
Email: [email protected]

Implications:

  • You personally own the domain
  • Domain is a personal asset
  • Can be transferred in estate planning
  • Subject to personal liability

Registering as an Organization

When appropriate:

  • Business websites
  • Company-owned domains
  • Organizational projects
  • Any domain owned by a legal entity

Registrant fields:

Registrant Name: John Smith (contact person)
Organization: ABC Corporation
Email: [email protected]

August 2025 ICANN Change: Starting August 21, 2025, if the Organization field contains a valid company name, that organization legally owns the domain. The individual in Registrant Name becomes only a contact person.

Current situation: Before this change takes effect, ownership can be ambiguous when Organization is filled but Registrant Name differs.

Best Practices for Business Domains

Do:

  • Use company name in Organization field
  • Use generic company email ([email protected])
  • Designate responsible employee in Registrant Name
  • Document domain ownership in company records

Don't:

  • Register company domains under employee's personal name with blank Organization
  • Use employee's personal email
  • Leave Organization blank for business domains
  • Rely on verbal agreements about ownership

Transitioning Personal to Corporate

Scenario: Employee registered domain personally, company wants to own it.

Steps:

  1. Update Organization field to company name
  2. Update Registrant Name to authorized contact
  3. Update email to company domain
  4. Complete verification
  5. Document the transfer in company records
  6. Note: This triggers 60-day lock

Legal considerations:

  • May want written agreement documenting transfer
  • Consider intellectual property implications
  • Consult legal counsel for valuable domains

Bulk Ownership Changes

Managing ownership changes across many domains requires planning and the right tools.

When Bulk Changes Are Needed

  • Company acquisition (inheriting hundreds of domains)
  • Rebranding (updating organization name across portfolio)
  • Consolidating domains to new management contact
  • Moving domains to company email from personal

Registrar Bulk Tools

Realtime Register:

  • Bulk update Admin, Billing, Tech, and Registrant contacts
  • Submit contacthandles for multiple domains
  • Option to act as Designated Agent
  • Privacy protect settings in bulk

Domain Helpdesk (various registrars):

  • Bulk Edit tool for multiple domains
  • Update Contact Information, DNS Servers, Auto Renew, Registrar Lock
  • Can use existing domain settings as template

AWS Route 53:

  • Custom script with update-domain-contact CLI command
  • Useful for programmatic bulk updates
  • Verification emails still required per domain

Bulk Change Best Practices

Planning:

  1. Export list of all domains to update
  2. Identify which changes trigger locks
  3. Determine if opt-out is needed
  4. Plan verification process (who monitors emails?)

Execution:

  1. Update in batches (not all at once)
  2. Monitor verification emails closely
  3. Track which domains completed successfully
  4. Document completion for records

Verification challenges:

  • Each domain sends verification email
  • Hundreds of emails to process
  • Set up email filters or dedicated inbox
  • Consider spreading over multiple days

60-Day Lock Implications for Bulk Changes

If planning portfolio consolidation:

Wrong approach:

  1. Change registrant across all domains
  2. Wait 60 days for lock to expire
  3. Then initiate transfers

Better approach:

  1. Transfer domains to new registrar first (if they don't need registrant updates)
  2. Update registrant information at new registrar
  3. Or opt-out of lock before making changes

If opt-out not available:

  • Stagger changes by priority
  • Update non-critical domains first
  • Update critical domains when 60-day lock is acceptable

Common Mistakes and How to Avoid Them

Mistake 1: Updating Registrant Right Before Transfer

The problem: You sell a domain, update registrant to buyer's info, and immediately try to transfer to buyer's registrar. Transfer is blocked for 60 days.

The solution:

  • Opt out of 60-day lock before making changes, OR
  • Transfer to buyer's registrar first, then update registrant, OR
  • Push domain within same registrar (if both parties use same registrar)

Mistake 2: Typo in New Email Address

The problem: You enter "[email protected]" instead of "[email protected]." Verification email never arrives. Process stalls.

The solution:

  • Triple-check email addresses before submitting
  • Use copy-paste from verified source
  • Test new email address first by sending yourself a message

Mistake 3: Not Having Access to Old Email

The problem: Employee who registered domain left company. Verification sent to their personal email. Can't complete change.

The solution:

  • Update registrant email to company address BEFORE employees leave
  • Use company domain emails ([email protected]), not personal
  • Document registrar credentials centrally
  • Request registrar support intervention (requires identity verification)

Mistake 4: Changing Fields One at a Time

The problem: You update registrant email on Monday, triggering 60-day lock. You update organization name on Wednesday, potentially extending lock period.

The solution:

  • Make all triggering changes (name, org, email) in a single session
  • Only one lock period applied

Mistake 5: Forgetting to Re-Enable Security

The problem: You disabled domain lock and WHOIS privacy to complete ownership change. You forget to re-enable them. Domain is vulnerable.

The solution:

  • Create post-change checklist
  • Set calendar reminder to verify settings
  • Re-enable transfer lock after changes complete
  • Re-enable WHOIS privacy if desired

Mistake 6: Not Documenting the Change

The problem: Domain ownership dispute arises years later. No records of when or why registrant changed.

The solution:

  • Screenshot before/after WHOIS data
  • Save verification confirmation emails
  • Document date and reason for change
  • For sales, keep transaction records

Best Practices

Before Making Changes

  • Verify you have access to both old and new registrant emails
  • Check if you need to transfer soon (plan around 60-day lock)
  • Screenshot current WHOIS data for records
  • Confirm Organization field is correct for your situation
  • Enable 2FA on registrar account if not already

During the Change

  • Make all triggering changes at once (name, org, email together)
  • Opt out of 60-day lock if you need transfer flexibility
  • Use exact legal names (match business registration for companies)
  • Double-check email addresses before submitting

After the Change

  • Complete verification immediately (don't wait)
  • Verify changes in WHOIS after 24-48 hours
  • Re-enable transfer lock at new owner's discretion
  • Re-enable WHOIS privacy if desired
  • Document the change with screenshots and dates
  • Update your records (domain inventory, password manager)

For Domain Sellers

  1. Agree on terms with buyer first
  2. Use escrow service for payment protection
  3. Opt out of 60-day lock before changing registrant
  4. Update registrant to buyer's information
  5. Complete verification with buyer
  6. Transfer to buyer's registrar (if different) after changes complete
  7. Confirm buyer received domain before releasing escrow

For Domain Buyers

  1. Verify seller has authority to sell
  2. Use escrow service (Escrow.com, etc.)
  3. Provide accurate registrant information
  4. Monitor email for verification requests
  5. Complete verification promptly
  6. Initiate transfer to your registrar after ownership change (if desired)
  7. Verify domain in your account before releasing escrow payment

Frequently Asked Questions

What is the difference between changing registrant and transferring a domain?

Changing registrant (ownership) updates who legally owns the domain---the name, organization, or email in WHOIS. The domain stays at the same registrar. Transferring moves the domain's registration from one registrar to another (e.g., GoDaddy to Cloudflare). You can do either independently, or both together. Changing registrant triggers a 60-day transfer lock; transferring also triggers a separate 60-day lock.

Can I change the domain owner without triggering the 60-day lock?

Only if your registrar offers an opt-out option and you select it before making the registrant change. Not all registrars offer opt-out (DNSimple, for example, does not). Also, you can update non-triggering fields (address, phone, billing contact) without any lock.

How long does a registrant change take?

The actual change happens quickly after verification---usually within minutes to hours once both parties confirm. The verification process can take 1-14 days depending on how quickly people click the verification links. After completion, WHOIS propagation takes 24-48 hours to reflect changes publicly.

What happens if the old registrant doesn't approve the change?

The change may be blocked or reverted. For legitimate ownership transfers, coordinate with the old registrant beforehand. For disputed situations, you may need legal action or the old registrant's cooperation. Some registrars have processes for proving ownership if the registered email is inaccessible.

Does changing registrant affect my website or email?

No. Changing registrant contact information only updates WHOIS/ownership data. It does not affect DNS records, nameservers, website hosting, or email. Your site continues working normally throughout the process.

Can I change just the email without changing the name?

Yes, but changing the email alone triggers the 60-day lock. If you're also planning to change the name or organization, do them all at once in a single update to avoid multiple lock periods.

What if I need to transfer the domain to a new registrar AND change ownership?

Option 1: Change registrant first (triggers 60-day lock), wait 60 days, then transfer. Best if buyer will manage at your current registrar temporarily.

Option 2: Opt out of 60-day lock, change registrant, then transfer immediately. Best if buyer needs domain at their registrar quickly.

Option 3: Transfer first, then change registrant at new registrar. Best if registrant info update can wait 60 days.

Option 4: If buyer has account at same registrar, "push" domain to their account (avoids inter-registrar transfer lock).

Is there a fee to change domain ownership?

Most registrars do not charge for registrant changes or account-to-account transfers. The process is typically free. However, if you transfer to a different registrar, the standard transfer fee (equal to 1 year renewal, typically $10-15 for .com) applies.

Key Takeaways

  • Changing registrant (name, organization, or email) updates domain ownership in WHOIS and triggers ICANN's 60-day transfer lock for gTLDs

  • The 60-day lock prevents inter-registrar transfers, not ownership changes---you can still update registrant info during a lock, just can't transfer away

  • Opt-out is available at many registrars (GoDaddy, Namecheap, Cloudflare, Dynadot, NameSilo) but must be selected BEFORE making changes

  • Verification requires confirmation from both old and new registrant email addresses---ensure access to both before starting

  • Non-triggering fields (address, phone, billing/tech contacts, nameservers) can be updated freely without causing a lock

  • Starting August 2025, ICANN will treat the Organization field as determining legal ownership---ensure this is accurate

  • ccTLDs (.uk, .eu, .ca, etc.) don't follow ICANN's 60-day policy and have their own registry rules

  • For domain sales, use escrow services, opt out of the lock, and coordinate verification timing with the buyer

  • For bulk changes, plan verification workflow carefully and consider staggering updates to manage email volume

  • ICANN approved eliminating the 60-day lock in late 2024, but implementation won't happen until 2026 at earliest

Next Steps

If You Need to Change Domain Ownership

  1. Determine if 60-day lock is acceptable---do you need to transfer the domain soon?
  2. Check if your registrar offers opt-out---see the registrar comparison table above
  3. Coordinate with all parties---ensure both old and new registrant can complete verification
  4. Make all triggering changes at once---combine name, org, and email updates
  5. Complete verification promptly---click those email links immediately
  6. Document everything---screenshot WHOIS before and after

Monitor Your Domains

Use DomainDetails domain monitoring to track changes to your domains' WHOIS data, ownership status, and registration details. Get alerts when registrant information changes unexpectedly.

Research Sources

This article was researched using current information from authoritative sources: