How to Transfer a Domain Away From GoDaddy

Point your nameservers at the new host before you transfer

A transfer only causes downtime if your domain is still using GoDaddy's default nameservers — the nsXX.domaincontrol.com pair. Namecheap's own transfer documentation is blunt about it: those nameservers stop responding to queries once the domain is transferred away. Your DNS zone lived on GoDaddy's infrastructure, and when the domain leaves, the zone stops being served. The website, the email and every subdomain go down together, and stay down until you rebuild the records at the new registrar.

That is a ten-minute problem to avoid and a bad afternoon to fix afterwards. Do this first:

1. Create the DNS zone at the destination and rebuild every record there. A records, CNAMEs, MX records with their priority numbers, and every TXT record — SPF, DKIM, DMARC and any verification strings for Google, Microsoft or a payment gateway.
2. Change the nameservers at GoDaddy. Domain Portfolio → the three-dot menu next to the domain → Edit DNS → Nameservers → Change Nameservers. Hostinger's are ns1.dns-parking.com and ns2.dns-parking.com; your own host will list theirs in the control panel.
3. Wait up to 24 hours and verify. Load the site, send yourself a mail from an outside address, and check anything that depends on a TXT record. Propagation is usually much faster, but 24 hours is the honest upper bound.
4. Only now request the authorisation code and start the transfer. With DNS already answering from somewhere other than GoDaddy, the registrar change becomes a billing event and nothing more.

If your domain already points at Cloudflare, at your host's nameservers, or anywhere that is not GoDaddy, none of this applies — skip straight to unlocking. And if you are moving the website as well as the domain, do the site first: migrating WordPress to a new host covers that half of the job.

Turn off WHOIS privacy first — GoDaddy declines transfers while it is on

Yes, you have to disable privacy, and it is policy rather than a glitch. Namecheap's transfer guide states it directly: while GoDaddy privacy protection is enabled, transfer requests are declined. This is the single most common reason a transfer “fails for no reason” — and it is why the Shopify and Wix support forums are full of identical threads.

GoDaddy sells privacy as two separate things, and both have to be off:

• The paid protection plans — Full Domain Protection or Ultimate Domain Protection & Security. Downgrade to basic privacy in the domain's settings.
• Domains By Proxy, the free privacy service that ships with registration. Turn it off from the same privacy panel; it is a separate switch from the paid plan.

The consequence nobody mentions: with privacy off, your registrant name, email and phone number sit in public WHOIS for the whole transfer window, and public WHOIS records are routinely harvested for “your domain is expiring” renewal scams — the kind that arrive as an official-looking invoice from a company you have never dealt with. Treat anything that lands in those few days with suspicion, and re-enable WHOIS privacy at the new registrar on the day the transfer completes — it is free at Namecheap, Porkbun and Dynadot, and included on eligible Hostinger domains.

The six steps

1. Save your DNS records first.

   Open the DNS management page at GoDaddy and screenshot or export everything — A records, CNAMEs, MX records for email, TXT records for verification and SPF. In most transfers these carry across, but if anything is going to go wrong, this is the file that saves you.

2. Unlock the domain.

   In GoDaddy's domain settings, find the registrar lock and turn it off. The lock exists to prevent unauthorised transfers, so nothing will proceed until this is done.

3. Request the authorisation code.

   Also called an EPP code or transfer key. GoDaddy emails it to the registrant address on file — which is worth checking is an address you still control. GoDaddy does not publish an expiry window for its codes, but plenty of registrars do expire theirs after about a month, so use it promptly rather than saving it for the weekend. If the new registrar rejects it, request a fresh one instead of retyping the old one.

4. Start the transfer at your new registrar.

   Enter the domain, paste the authorisation code, and pay for one year of registration at their price. That year is added to your existing expiry date.

5. Approve it from the GoDaddy side.

   GoDaddy will email asking you to confirm. Approving actively takes days off the process — if you ignore it, the transfer still completes, but only after the full five-day window expires. Expect a retention offer in that email; whether it is worth taking is your call.

6. Verify after it completes.

   Check the site loads, check email still arrives, and compare the DNS records against the ones you saved in step one. Then set a calendar reminder six weeks before the new expiry.

The timing mistake that costs a year

Will your email keep working? What happens to MX records

Your mailboxes survive the transfer, but your mail stops if the MX records do not come across. Nothing about a registrar change touches the mailbox itself — it changes where the world looks up your MX records, and if the answer comes back empty, mail bounces or silently queues at the sender. Google Workspace and Microsoft 365 support forums are full of “email stopped working after I transferred my domain” threads, and the fix is almost always in DNS rather than in the mailbox.

• Copy MX records with their priority numbers exactly. Priority is not decoration — Google Workspace expects its primary record to carry the lowest number, and getting the order wrong makes delivery erratic rather than broken, which is far harder to diagnose.
• Delete stale MX entries at the destination. Many hosts pre-create their own mail records on a new zone. Leave those alongside your real ones and mail splits between two providers depending on which server a sender happens to reach.
• Recreate SPF, DKIM and DMARC. These are TXT records and they do not move themselves. Miss them and mail still “works” — it just starts landing in spam, which people usually notice a week later after a lost invoice.
• Test from outside. Allow up to 48 hours, then send from an address on a completely different provider. Mailing yourself from your own domain proves almost nothing.

Check the real status with WHOIS, not the dashboard

Run a WHOIS lookup on your domain and read the “Domain Status” line. It comes from the registry itself, which is the only party whose opinion counts, and it will tell you the truth faster than either registrar's dashboard — both of which lag and both of which are optimistic.

Worth knowing that clientTransferProhibited is not an error. It is the standard anti-hijacking status, and the registry also applies it automatically for 60 days after a registration or a transfer — which is the same 60-day rule, seen from the registry's side.

On timing: ICANN gives the losing registrar up to five days to release the domain and GoDaddy generally uses the full window, which is why “five to seven days” is the realistic answer. Approve it actively from the GoDaddy side and the remainder collapses to roughly a quarter of an hour at the receiving registrar. When a transfer genuinely sticks, it is almost always one of two causes: the confirmation email went to a registrant address the owner no longer controls, or there is a registry-level lock that only the losing registrar's support team can remove.

How to avoid triggering the 60-day lock in the first place

You cannot lift a lock that has already fired, but you can avoid causing one. The lock is triggered by a change to the registrant's first name, last name, organisation or email address. Edit any of those and the domain is frozen for outbound transfers for 60 days from the edit — not from registration.

So the sequence matters more than anything else. Namecheap's guidance is the practical workaround: edit the Administrative contact rather than the Registrant, which does not trigger the lock. Better still, do the transfer first and correct the registrant details at the new registrar afterwards — the details follow the domain, and you avoid a two-month wait for no benefit.

Once it has fired, be sceptical of anyone promising a workaround. Namecheap's documentation does mention that GoDaddy operates a review address for 60-day lock opt-outs, available only with domain privacy disabled — but it is discretionary, not a right, and plenty of people are simply refused. There is no coupon, no escalation and no support ticket that reliably removes it. Plan around it instead: if you know you are leaving, do not touch the registrant fields on your way out.

Moving more than one domain: the bulk method

You do not have to click through domains one at a time. GoDaddy's Domain Portfolio has an export option that downloads your domains as a CSV, which at least gives you the list, the expiry dates and the lock status in one file instead of forty browser tabs. Whether the authorisation codes come with it depends on the account, so check the file before assuming you still have to request them one by one.

At the receiving end, Namecheap's Transfer to Us page has a bulk tab that takes one domain per line with the auth code after it, separated by a comma and a space — example.com, AUTHCODE — and accepts up to 50 domains in a single order. More than that means splitting it into several orders.

The part that catches people out is what isn't bulk: each domain still has to be unlocked individually at GoDaddy and have its privacy disabled individually, and each has its own auth code. And check expiry dates before you submit — a domain expiring within the next week or two can be rejected mid-transfer, so renew those at GoDaddy and move them on the next cycle rather than losing the request and the fee.

Cancelling a transfer and getting your money back

You can cancel while the request is pending, but once it is In Progress the gaining registrar cannot stop it. GoDaddy documents this rule for transfers coming in to GoDaddy, and it works the same way in reverse: an In Progress transfer has to be cancelled at the registrar that currently holds the domain. Moving away from GoDaddy, that means rejecting it from the GoDaddy side, not from the new registrar's dashboard.

Reject it and the domain simply stays where it is, with its original expiry date untouched. The year you paid for at the new registrar is refunded to the original payment method if the cancellation is approved — but the authorisation code is burned and has to be requested fresh, and you may have to wait before the registry will accept a fresh request.

There is really only one good reason to pull the handle: you started the transfer before pointing your nameservers, realised the site and email were about to go dark, and would rather spend an evening on DNS than take the outage. That is a sensible cancellation. Cancelling because the transfer is “taking too long” on day three is not — the five-day window is normal and restarting resets the clock.

GoDaddy to GoDaddy: changing a domain’s account or owner (a “push”)

Moving a domain between two GoDaddy accounts is not a registrar transfer at all. It is an account change: free, no authorisation code, no five-day ICANN window. It completes the moment the recipient accepts, which is usually minutes rather than days.

This is also how domain ownership changes hands inside GoDaddy — you would do it when you sell a domain, when you hand a client the domain you registered on their behalf, or when you split a portfolio across accounts. The sender opens the domain in Domain Portfolio, chooses the option to transfer it to another GoDaddy account, and enters the recipient's GoDaddy account email — adding their customer number is optional and speeds things up. The recipient accepts from the emailed link or from Pending Account Changes in their own account. If nobody accepts, the request lapses after about ten days and you start again.

Two caveats buyers get caught by. A push does not add a year or change the expiry date — no registration is being purchased, so whatever time was left is what you get. And it does not clear the 60-day out-transfer lock: that lock sits on the domain at the registry, not on the account, so if you buy a recently registered or recently transferred domain by push, the receiving account still cannot move it to a different registrar until the original 60 days are up.

What a GoDaddy domain transfer actually costs in India

A transfer costs one year at the new registrar's price, and nothing at all to GoDaddy. There is no exit fee, no charge for the authorisation code, no penalty for leaving mid-term. The number below is the whole bill — and it buys a year that is added to your existing expiry, not a year that replaces it.

Two things that make this table honest and that most comparison pages skip. First, GST. Every price an Indian registrar publishes is pre-tax, and 18% is added at checkout — so the ₹969 becomes about ₹1,143 on the invoice and a ₹1,400 GoDaddy renewal becomes about ₹1,652. Compare like with like or the gap looks bigger than it is. Second, forex. The dollar registrars bill in USD, so an Indian card adds a foreign-currency markup and the rupee cost moves with the exchange rate every year. A $10.88 domain is genuinely cheap; it is just not as cheap in rupees as the sticker suggests, and it is never a number you can budget exactly.

The caveat that matters more than the headline: only the transfer price is published anywhere. The renewal price a year later is the number that decides whether the move was worth it, and .com renewals sit in a similar band at most registrars because the registry sets a wholesale floor. Check the renewal rate on the checkout page before you commit, not the transfer rate.

Full five-year comparison in best domain registrars for India, the reason renewals jump in why GoDaddy renewals rise 2–4×, and the head-to-head in Namecheap vs GoDaddy. If hosting is moving too, the hosting cost calculator adds up the whole bill.

Where the domain can go

Transfer a domain from GoDaddy to Hostinger

₹969 for a .com, billed in rupees, a year added to your existing expiry, and free WHOIS privacy on eligible domains. The honest qualifier: this is the right call when your site already lives on Hostinger, because the domain then sits in the same hPanel as the hosting and the DNS zone is already there — which also removes the nameserver problem described above entirely. If your site is hosted somewhere else and you have no plans to move it, a registrar-only destination is the cleaner choice. Background in the Hostinger review and current India pricing.

Transfer a domain from GoDaddy to Namecheap

The default registrar-only move, and the one most guides assume. Free WHOIS privacy for the life of the domain, proper bulk transfer tooling if you are moving a portfolio, and a checkout that does not fight you. The downside for an Indian buyer is simply that it is billed in dollars, so your bank's forex markup rides along every year. Start a transfer to Namecheap →

Transfer a domain from GoDaddy to Dynadot or Porkbun

The pure-cost play: both price registration, renewal and transfer at roughly the same figure, year after year, so there is no renewal cliff to remember. Interfaces are utilitarian rather than friendly, and support is thinner than at the big brands — which is a fair trade if the domain is parked and you touch it twice a year. Transfer to Dynadot →

Transfer a domain from GoDaddy to Cloudflare

Cloudflare Registrar sells at what it pays the registry — its own documentation promises no markup and no surprise fees — which makes it the cheapest long-run home for a domain you intend to keep for a decade. Two real constraints, though. You must add the domain to Cloudflare and move it onto Cloudflare's nameservers first, because Cloudflare only accepts transfers of domains already active on a full setup. And it supports a large but not universal list of extensions, so check yours is on the list before you plan around it.

Transfer a domain from GoDaddy to Shopify or Wix

Both accept transfers, but only for domains you actually use on their platform — they are store and site builders that happen to hold your registration, not registrars you would choose on price. Their support forums are full of “transfer failed” threads, and the cause is nearly always the same one: GoDaddy privacy protection was still switched on. Turn it off, wait for the WHOIS record to update, then retry.

Should you pick Hostinger for the transfer?

The steps are identical wherever you go — unlock, auth code, paste, pay — so the only real question is which destination suits your setup. Here is the honest split rather than the sales pitch:

₹969 for a .com, includes a year added to your expiry · Free WHOIS privacy on eligible domains

Is it worth transferring away from GoDaddy?

In the year you move, almost always yes — and the honest answer for the years after that is “it depends on where you move to.” The transfer year is the clear win: ₹969 at Hostinger against a GoDaddy India renewal that typically lands between ₹1,000 and ₹1,400, and the year you buy stacks onto your existing expiry instead of replacing it. You are getting the same twelve months for less money, so the move pays for itself immediately.

The part most affiliate pages will not tell you: .com renewals are not wildly different between mainstream registrars, because the registry sets a wholesale floor that nobody sells far below. Hostinger's own .com renewals sit in roughly the same ₹1,000–₹1,400 band as GoDaddy's. If you are chasing a recurring saving rather than a one-off one, the flat-price registrars — Dynadot, Porkbun, Cloudflare at registry cost — are the honest recommendation, not a hosting company. Anyone quoting you a large permanent saving on a .com is quoting the transfer price and hoping you do not check the renewal.

The non-price reasons people actually cite are worth taking seriously too: a checkout that upsells hard, renewal pricing that differs from account to account depending on the promo you originally signed up under, and simply wanting DNS in the same panel as the hosting. If hosting is part of the decision, the numbers are in Hostinger vs GoDaddy vs Bluehost and best web hosting in India.

If the transfer fails

• “Domain is locked” — the registrar lock is still on. Go back to step two.
• “Invalid authorisation code” — it has expired or was copied with a trailing space. Request a fresh one.
• “Domain is within 60 days of registration” — nothing to be done but wait it out.
• No confirmation email — check the registrant contact address on the domain, not just your usual inbox. Old email addresses on WHOIS records are the most common cause.
• Privacy protection blocking it — the most common cause of all. GoDaddy declines transfer requests while privacy is active, so both the paid protection plan and Domains By Proxy have to be off before you retry.
• Site or email went down mid-transfer — the domain was still on GoDaddy's default nameservers. Rebuild the DNS zone at the new registrar immediately; the records are recoverable from the export you took in step one.

FAQ — domain transfers

Related reading

• Why GoDaddy renewals jump 2–4× — the numbers behind the decision.
• Best domain registrars — five-year cost compared.
• Migrating WordPress to a new host — if you are moving hosting as well.
• Hostinger domain prices in India — registration, transfer and renewal, in rupees.
• Hostinger vs GoDaddy vs Bluehost — if the hosting is moving too, not just the domain.
• Hosting cost calculator — total cost over the term, GST included.

Aage kya padhein