How to transfer a domain to a new registrar

Transferring a domain to a new registrar is common — you might be chasing better renewal pricing, consolidating everything in one dashboard, or leaving a provider you've outgrown. The process is well-defined and, done right, causes no downtime. Here's the full walkthrough.

Before you start: the eligibility rules

A few ICANN rules govern transfers, and knowing them saves frustration:

• 60-day lock after registration or a previous transfer. A domain registered or transferred within the last 60 days can't be transferred again yet.
• The domain must be unlocked. Registrars apply a "registrar lock" to prevent unauthorised moves; you lift it yourself.
• You need a valid admin email. The transfer approval goes there, so make sure it's current.

Step 1: Prepare at your current registrar

At the registrar you're leaving:

1. Unlock the domain. Find the domain in the control panel and disable the registrar/transfer lock.
2. Disable WHOIS privacy temporarily if the transfer process requires it — some do, some don't. You can re-enable it afterward at the new registrar.
3. Get the auth code. This is the EPP code (also called an authorization or transfer code) — a unique password that proves you own the domain. Request it and copy it exactly.

Step 2: Start the transfer at the new registrar

At the registrar you're moving *to*:

1. Enter the domain name and choose "transfer."
2. Paste the EPP/auth code when prompted.
3. Pay the transfer fee. Here's a nice detail: a transfer almost always adds a year to your registration, so you're not losing time — you're extending it.

Step 3: Approve and wait

The transfer needs your confirmation:

• You'll usually get an approval email at the admin contact — click to confirm.
• The losing registrar may take a few days to release the domain (they're allowed a window, and you can often approve immediately to speed it up).
• A full transfer typically completes in 5 to 7 days, though it can be faster.

Avoiding downtime

This is the part people worry about, and it's easily handled:

> Your DNS records travel with your domain only if you replicate them. Before transferring, note your existing DNS records — A, CNAME, MX, TXT — and make sure the new registrar's DNS has the same records set up. Then the switch is invisible to visitors.

If your nameservers point to a third-party DNS provider (not the registrar), your DNS doesn't change at all during the transfer — only the registrar of record does. Either way, plan the records so nothing skips a beat.

Step 4: Tidy up

Once the transfer completes:

• Re-enable WHOIS privacy at the new registrar.
• Re-lock the domain to protect it from future unauthorised transfers.
• Confirm auto-renew is on so you don't lose it later.
• Verify DNS with a quick check:

dig example.com +short
whois example.com | grep -i registrar

Why people transfer to Nxeon

The usual reasons are consolidation and pricing. If your domain lives at one company and your server at another, you're juggling two logins and copying IPs between them. Bringing the domain to Nxeon (registered through name.com) puts your DNS records right next to the server they point at — one dashboard, one bill, and no cross-account guesswork. Transfer once, and everything's in one place.