Will my website or email go down during the transfer?

No, as long as the nameservers answering for your domain don't change. A registrar transfer moves who the domain is registered with; DNS resolution continues uninterrupted throughout. Downtime only happens if you change nameservers to an empty or misconfigured zone.

How long does a transfer to Route 53 take?

For common gTLDs like .com it can take up to five days, but it's often much faster if you approve the confirmation email and also approve the outbound transfer in your current registrar's dashboard. Some ccTLDs follow different timelines.

Do I lose the registration time I already paid for?

No. The transfer adds one year to your existing registration, and you keep the remaining time you'd already purchased (subject to some TLD-specific rules). You're not starting the clock over.

How to Transfer a Domain to Amazon Route 53 Registrar

VigilDog Team · October 12, 2026 · 6 min read

Moving a domain to Amazon Route 53 is one of those tasks that feels risky because your entire web and email presence rides on getting it right. It doesn't have to be. If you separate the two things people constantly conflate, transferring the registrar versus hosting the DNS, and prepare the domain properly first, the actual transfer is anticlimactic and your site never blinks. Here's the full sequence.

Registrar transfer vs DNS hosting, know which one you're doing

Route 53 does two separate jobs. As a *registrar*, it's where the domain is registered and renewed. As a *DNS host*, it answers queries for your records via a hosted zone. These are independent. You can move your DNS hosting to a Route 53 hosted zone without changing registrars at all, and you can transfer the registrar to Route 53 while leaving DNS hosted somewhere else.

This distinction is what keeps a transfer downtime-free. Your site stays reachable as long as the nameservers answering for your domain keep answering, the registrar change underneath is invisible to visitors. Understanding how DNS delegation works makes the whole process far less nerve-wracking, because you can see exactly which layer you're touching at each step.

How a domain name resolves to a server

The pre-transfer checklist

Most failed transfers fail before they start, on eligibility rules the gaining registrar can't override. Run through this at your current registrar first:

The domain is at least 60 days old and hasn't been transferred or had a registrant change in the last 60 days (an ICANN rule, not an AWS one).
The domain is unlocked, turn off the registrar/transfer lock in your current provider's dashboard.
You have the authorization code (also called the EPP or auth code), which you request from the current registrar.
WHOIS/privacy is set so the confirmation email reaches you; some registrars block the auth email while privacy is on.
The registrant email on file is one you can actually access, the approval step goes there.
The TLD is supported by Route 53 (most common gTLDs and many ccTLDs are; a few aren't), and the domain isn't within a few days of expiry.

Set up the hosted zone first (this is what prevents downtime)

If your DNS is currently hosted at the losing registrar, create the Route 53 hosted zone and replicate every record before you initiate the transfer. Copy over your A/AAAA, CNAME, MX, and TXT records exactly, pay special attention to MX and the SPF/DKIM/DMARC TXT records, because a missed one means silent mail delivery failures. Lowering your record TTLs a day ahead of time makes any later cutover propagate faster.

If your DNS already lives somewhere you're happy with (Cloudflare, your host, etc.), you can transfer the registrar to Route 53 and simply choose to keep your existing nameservers. Nothing about resolution changes and there's no hosted zone to build. Decide which of these two paths you're on before touching the transfer wizard.

Run the transfer in the Route 53 console

In the Route 53 console, go to Domains → Registered domains → Transfer in. Enter the domain, and Route 53 checks it's unlocked and eligible. Paste the authorization code, choose your nameserver option (use the Route 53 hosted zone you built, or keep your current nameservers), confirm the contact details, and pay, the transfer fee includes one year of registration added to your existing time.

AWS then emails the registrant for confirmation; approve it promptly. You can usually speed things up by also approving the outbound transfer in your current registrar's dashboard instead of waiting for its timers. For gTLDs like .com the process typically completes within five days, sometimes much faster once both sides approve. Your site and email keep working the entire time because the nameservers never stopped answering.

After the transfer completes

Once AWS shows the domain as registered with Route 53, verify resolution end to end with the DNS record checker, confirm A, MX and your TXT records resolve to the values you expect from multiple locations, not just your own cached view. Then re-enable the transfer lock, turn on auto-renew, and confirm the WHOIS contact details are correct.

The one thing new Route 53 owners forget is renewal visibility, AWS won't chase you the way some registrars do. Set up expiry monitoring so a lapsed card or a missed notification can't cost you the domain. You can sanity-check the current registration window any time with the domain expiry checker.