Transferring a domain between registrars without breaking anything

A transfer moves the registration from one registrar to another. That is all it moves. Done in the right order, visitors notice nothing, email keeps arriving, and you usually gain a year on the expiry date. Transfers go wrong for three reasons, and they are always the same three: someone moved before copying their DNS records, someone left DNSSEC switched on, or someone started the whole thing a week before expiry.

Here is the sequence that avoids all of it.

The registration travels; your website stays where it is

What changes is who bills you and who speaks to the registry on your behalf. Your site, your mailboxes and your DNS zone are separate matters entirely.

• Goes with you: the registration record, the expiry date, the contact details, and control of the nameserver delegation.
• Stays behind: DNS records held in the losing registrar's own DNS service. A, AAAA, CNAME, MX, TXT and SPF records live in whichever nameservers the domain points at. If those nameservers belong to the registrar you are leaving, the records can be deleted the moment the domain departs.
• Also stays behind: email hosting, web hosting, SSL certificates, URL forwarding and any parked page sold as an add-on.

This is where most self-inflicted downtime comes from. If your nameservers already sit with a third party, whether that's Cloudflare, Route 53 or your host, the transfer is close to invisible. If your DNS lives at the registrar you're walking away from, deal with that before anything else.

Do all of this before you press anything

• Check the 60-day locks. ICANN blocks the transfer of a gTLD within 60 days of initial registration, and within 60 days of a previous transfer. Changing the registrant name or email can trigger its own 60-day lock unless the registrar offers an opt-out and you take it. Just bought the name? You're waiting.
• Look at the expiry date. Don't start a transfer inside roughly 15 days of expiry. Renew, then move. A transfer that lands late, or one that gets tangled up in redemption, costs far more to unpick than a renewal ever would.
• Export the zone. Every record: A, AAAA, CNAME, MX, TXT including SPF, DKIM and any domain-verification strings, plus SRV and CAA. Note the TTLs while you're there.
• Lower those TTLs to 300 seconds a day or two ahead if you intend to change nameservers, so any mistake you make propagates out of existence quickly.
• Switch DNSSEC off. With DNSSEC enabled, the DS record at the registry has to match the signing keys at your DNS provider. Carry a stale DS record through a transfer and you get hard resolution failure: validating resolvers return SERVFAIL and your domain simply ceases to exist for a large slice of the internet. Disable it, wait for the DS record to clear the registry, transfer, then re-sign at the new provider.
• Make sure the admin email works. Approval messages go to the registrant or admin contact on the WHOIS record. If it's an address from two jobs ago, fix it first, and mind the 60-day lock that fix might trigger.
• Unlock and fetch the auth code. Remove clientTransferProhibited and request the EPP or authorisation code. Codes expire, so get yours when you're ready to move, not a fortnight in advance.
• Drop WHOIS privacy if the gaining registrar asks. Privacy proxies mask contact data the new registrar needs, and transfers fail over it.

Approving the second email is what saves you five days

At the gaining registrar, start the transfer, enter the domain, paste the auth code. Then the details.

• You pay a transfer fee, usually the equivalent of one year's registration. For most gTLDs it adds a year to the existing expiry rather than resetting the clock. Some ccTLDs reset the term instead.
• The gaining registrar sends a Form of Authorisation. Approve it.
• The losing registrar then sends its own confirmation. Approve that too. This is the step that converts a five-day wait into a same-day transfer. Ignore both and the transfer auto-completes after five days anyway.
• You'll be asked whether to keep the current nameservers. Keep them. Change them after the transfer has landed and the new zone has been built and checked.

Not every extension follows the gTLD script. .uk uses an IPS tag change rather than an auth code, and it's effectively instant. .de works on an AuthInfo plus a KK request. Country-code domains may also carry residency or trustee requirements that the gaining registrar has to satisfy first. Read the registry's rules rather than assuming.

Registrars can say no, but only for listed reasons

Losing your business is not one of them. The legitimate grounds are narrow:

• Non-payment for the current term, or a chargeback on the registration.
• Evidence of fraud, or a live UDRP or court order.
• The domain sitting within 60 days of registration or a prior transfer.
• A lock still in place, or an auth code that's wrong or expired.
• Registry status codes such as pendingDelete or serverTransferProhibited.

Refused for something outside that list? Ask for the denial reason in writing, then escalate. ICANN runs a Transfer Dispute Resolution Policy and a complaint form for registrar conduct. Requesting the written reason tends to resolve the matter on its own.

When the transfer is part of the purchase

Acquiring a name on the aftermarket changes the mechanics. The transfer happens inside the sale, and the sequencing is the entire point.

On Names.com, completed purchases go through escrow, so nobody has to pay first or hand over first. Depending on where the name currently sits, the handover is either a push into your account at the same registrar, which is near instant with no auth code and no five-day wait, or a conventional registrar-to-registrar transfer following the process above. Pushes are quicker and have fewer ways to fail, which is why they're the default wherever they're possible.

Two things buyers forget. A freshly transferred domain sits inside its own 60-day lock afterwards, so any onward move has to be planned around that. And on a monthly payment plan, the name usually stays in a holding arrangement until the final instalment clears; full transfer control arrives at completion, not at payment one. Read the terms so the timing doesn't ambush a launch date.

Still deciding on the name itself? Find out what's genuinely available before you fall for something. The category domain finder shows live options faster than poking at a registrar search box.

The confirmation email proves nothing

Verify it yourself:

• The domain shows in the new account with the expiry date you expected.
• Nameservers are right and the zone resolves. Test A, MX and TXT specifically.
• Send a test email, then receive one. MX and SPF failures are quiet and expensive.
• Auto-renew is on. It seldom survives the move.
• Registrar lock is back on, and DNSSEC re-signed if you use it.
• Contacts are current and two-factor authentication is enabled on the new account.

Put your TTLs back up and you're finished. Nobody outside your team will have any idea it happened.