How to move your domain to another registrar

To move a domain away from Just Domain: open it in your dashboard, switch the transfer lock off, confirm it is you, and copy the authorization (EPP) code that appears on screen. Download your DNS records from the same place, then give the code to the registrar you are moving to. There is no fee for leaving and no step where we try to change your mind.

Open your dashboard →

Before you start

Two things are worth settling first, because both are easier before the domain moves than after.

• Know where your DNS is going. A transfer moves who manages the name. It does not carry the records that point the name at your site and your mail. If Just Domain answers DNS for this domain, download the records from the Advanced tab and have somewhere to put them.
• Check the timing rule for your ending. Some endings will not accept a transfer request yet if the domain was registered, transferred or had its registrant details changed recently. That rule belongs to the ending, not to us, and it never blocks the unlock or the code.

Not sure whether the domain is ready to move? The domain transfer checker reads the public registry record and tells you what, if anything, is standing in the way. It is free, it needs no account, and it changes nothing.

Move your domain in six steps

1. Open the domain in your dashboard. Sign in at justdomain.ai, open the domain you are moving, and go to its Advanced tab. The transfer lock sits at the top, with the state we read from the registry and the time we last read it. If we could not reach the registrar, it says Unknown rather than guessing.
2. Start the unlock and code step. Select Unlock and get transfer code. If the domain is already unlocked the button reads Get transfer code instead, because there is nothing to unlock. One flow handles both, so you are never left half way with an unlocked domain and no code.
3. Confirm it is you. Type the domain name to confirm, and sign in again if your session is not recent. An authorization code lets somebody move the name, so this step guards the code, not the lock. Switching the lock on or off by itself is a single click with no confirmation.
4. Copy the code from the screen. The code appears in your browser, once. We do not store it and we never email it, so copy it before you close the sheet. If you lose it or it goes stale, come back to the same screen and get a fresh one.
5. Take your DNS records with you. On the same screen, download your records as a BIND zone file or as a plain list. A transfer moves who manages the name, not the records attached to it, so recreate them at the new provider before the move lands.
6. Hand the code to your new registrar. Paste the domain and the code into the transfer form at the registrar you are moving to. They start the transfer with the registry from there. Nothing else is needed from us.

Where the transfer lock lives, and what it means

The transfer lock is a flag on the domain at the registry. While it is on, the registry refuses a transfer request, which is what stops somebody else moving your name while you are not watching. On the public record it shows up as clientTransferProhibited. Almost every registrar sets it by default, and so do we.

You will find it at the top of the domain’s Advanced tab, as a switch with the state beside it and the time we last read that state from the registrar. If the read did not go through, the state reads Unknown and says so in words, rather than showing you an off switch we cannot stand behind. Flipping the switch is a single click with no confirmation step: putting friction on a lock only teaches people to leave their own domain unprotected.

Why we ask you to confirm it is you

Unlocking a domain and issuing its authorization code are two different levels of risk. An unlocked domain still needs a code before anything can happen to it. A code, on its own, is enough to move the name. So the confirmation sits on the code: you type the domain name, and if your sign-in is not recent we send you through sign-in again and bring you straight back to the same step.

It costs you a few seconds, and it is the difference between a session someone else picked up and a decision you actually made.

The code shows once, and you can always get a fresh one

When the code appears, copy it. It exists on that screen and nowhere else: not in our records, not in an email, not in a link. Close the sheet and it is gone.

That is not a one-shot trap. Open the same screen again whenever you want and get another code. A new one replaces any code issued for that domain before it, so if the registrar you are moving to reports the code as invalid, or you started the move a while ago, get a fresh one and use that.

Taking your DNS records with you

Next to the code you will find two downloads: a BIND zone file, which most DNS providers can import directly, and a plain record list for typing records in by hand. Take one before you go.

Records live with whoever answers DNS for the name, so if that is us today, the new registrar or DNS provider starts with an empty zone. Recreating the records there before the transfer completes is the step that keeps a site and a mailbox from going quiet. Nothing on our side is deleted the moment you leave, but plan as though the switch is the moment it matters. See DNS records, explained if you want a plain-language read on what each record does.

What the receiving registrar does next

Once you hand over the domain and the code, the registrar you are moving to submits the transfer to the registry. On gTLDs such as .com, .net and .org, ICANN’s Transfer Policy gives the registrar currently holding the domain five calendar days to answer that request; if it does not answer, the registry approves the transfer by default. So a gTLD transfer that nobody stops usually completes about five days after it is started. Endings outside that policy, including .ai and .uk, run to timings their own registry sets.

Those clocks belong to the registry and to the registrar receiving the domain. We are not in the middle of them, and we do not add a queue of our own.

What we email you, and why you cannot switch it off

Whenever the transfer lock on a domain changes, or an authorization code is issued for it, we email your account address and the registrant address on the domain. That notice cannot be turned off. It is how you find out if somebody else tries it.

The email tells you what happened and when. It never carries the code itself, for the same reason we do not store one: a credential in a mailbox is a credential in every forward of that mailbox.

What we do not do when you leave

No exit fee, no survey, no retention offer, and no downgrade required. There is no phone call and no cooling-off screen between you and the code. The only things that can hold a transfer up are the rules the registry sets for that ending, or a legal hold such as a domain dispute or a court order.

Moving a domain in to Just Domain is the half that is not self-service yet: it starts with an email to support@just-done.ai and we arrange it by hand. We would rather say that plainly than let you find it out halfway through. How transfers in work covers that direction.

I want to move my domain away from Just Domain to another registrar. Walk me through it.

1. Tell me to sign in at justdomain.ai, open the domain, and go to its Advanced tab - that is where the transfer lock and the authorization (EPP) code both live.
2. Remind me to download my DNS records from that same screen before the move, and help me plan where to recreate them.
3. Explain that I will be asked to type the domain and to sign in again before the code is shown, and that the code appears once in my browser.
4. Do not ask me to paste the authorization code into this chat, and do not offer to fetch it - only I can see it.
5. Once I have it, help me fill in the transfer form at the registrar I am moving to, and tell me what to expect while the transfer runs.