24/7 local support available.
Guides / Domains
Domains

How to Transfer a .in Domain From BigRock, GoDaddy or Any Registrar

October 14, 2026 • 4 min read • HostBible Team

To move a .in domain you ask your current registrar for the authorisation (auth) code, give it to the registrar you are moving to, and that registrar starts the transfer. According to the .in registry (NIXI), the transfer then completes within five 24-hour periods. The steps are the same whether the current registrar is BigRock, GoDaddy or someone else, but the screens differ.

How does a .in registrar transfer work?

NIXI publishes the procedure on its registrar-to-registrar transfer page. First you obtain the authorisation code from the current sponsoring registrar of the domain. Then you give that code to the winning (new) registrar, which initiates the transfer. Once it is initiated, NIXI says the transfer will be completed in five 24-hour periods.

Two details from the same page matter. The auth code is a code of 6 to 16 characters assigned by the registrar, and registrars are contractually required to provide it when the registrant asks. NIXI itself does not give auth codes to registrants, so there is no point asking the registry. NIXI also advises changing the auth code after the transfer, through the new registrar.

If you are unsure who your current registrar is, the WHOIS record shows it. Our WHOIS lookup will show the sponsoring registrar and the current status codes. For the general idea of transfers across all extensions, see how a domain transfer works.

What should you check before asking for the auth code?

Start with the domain's lock status. The registry's FAQ explains that the statuses Client Update Prohibited and Client Transfer Prohibited mean the domain is locked, and that a status set by the registrar can only be removed by the registrar. If your domain is locked, ask the current registrar to unlock it or find the lock toggle in the account, otherwise the transfer will not start.

Next, make sure the domain is not on a verification hold. A .in domain whose registrant has not completed eKYC can be suspended and stop resolving, as explained in the guide to .in eKYC suspensions. Registrars commonly report that a transfer can itself trigger a fresh verification, so complete or confirm eKYC first and keep the registrant email reachable during the move.

Finally, check the expiry date. Do not start a transfer a day before expiry. Renew first if it is close, and read the notes on domain expiry and renewal if you are unsure what the registrar will do.

Is there a 60 day lock on .in transfers?

A 60 day lock after registration or a transfer applies to some other extensions, so people often ask about it for .in. NIXI's transfer page does not mention any waiting period, so there is no registry-documented lock to point to. What is documented is that individual registrars apply their own rules. GoDaddy's .in help page, for example, says transfers to another GoDaddy account are blocked for 10 days after registration, which is a rule about moving between GoDaddy accounts, not a registry timer.

The practical advice is simple. If you registered or moved the domain recently and the registrar refuses to release the code, ask them to state the exact rule in writing and its end date, as of October 2026 the registry's public transfer page does not show a lock period.

How do you ask BigRock, GoDaddy India or another registrar for the code?

The auth code is normally requested from the domain's settings in your registrar account, where it may be labelled authorisation code, EPP code or transfer key. Menus differ between registrars and change often, so this guide does not describe exact buttons. Search your registrar's help centre for the phrase transfer out or auth code, or raise a ticket asking for the code for the named domain.

Because registrars must provide the code on request, a refusal is something to challenge. Keep the request in writing so you have a date. If the registrar says the code has been emailed, check the registrant email address, which is also where verification messages go.

What do you do about DNS, email and the website during the transfer?

A registrar transfer does not move your website. Nameservers normally stay as they are unless you change them, so if your DNS is hosted by the old registrar, copy every record before the move: A records, MX records, TXT records for SPF and DKIM, and any CNAMEs. Then decide whether to keep DNS where it is, or recreate it at the new registrar or at your host first. The guide to migrating DNS walks through the order.

The safe pattern is to leave nameservers untouched until the transfer shows as complete, then change them as a separate, deliberate step. Doing both on the same day makes it hard to know which change broke what. After a nameserver change, use the DNS propagation checker to watch it spread.

If you are leaving GoDaddy altogether, how to leave GoDaddy covers hosting and email as well as the domain. After the transfer completes, change the auth code through the new registrar, as NIXI advises.

What can go wrong?

The common failures are an expired or suspended domain, a locked domain, a wrong or outdated registrant email, and an auth code typed with a stray space. If the transfer fails, the usual first step is to ask the new registrar what error it received, since it is the one that initiated it.

This is general information rather than legal or registry advice. Confirm the current procedure and any registrar fees with the registry's published tariff or with your registrar before you start.

Related guides

Sources and further reading

Moving your website as well as the domain?

A domain transfer only changes the registrar. If you are also changing hosts, HostBible's migration team moves the files, databases and email, and the old site stays live until you switch DNS.

See website migration