Our website is in Dutch; support is available in English.

Transferring a domain name without downtime

The auth code, your rights as the holder, and the difference between transferring the registration and changing DNS.

Updated 4 minute read

Contents of this article
  1. Two actions that are often confused
  2. The auth code
  3. Keeping the switchover calm
  4. Where it usually goes wrong
  5. What we don't do here
  6. Further reading

Transferring a domain name to another provider doesn't have to affect your website or email. Things go wrong when two separate actions get mixed up. This page explains which two.

Two actions that are often confused

This is the most important sentence on this page: transferring the registration and changing the DNS are two different things. They can happen at the same time, but they don't have to, and it is usually wiser to keep them apart.

Transferring the registration

This only changes which registrar your domain name is administratively held at. The holder stays the same. Nothing changes technically: your website stays on the same server, your email arrives at the same place. Visitors don't notice a thing.

Changing the DNS

This changes where your website and email point to. This is the action that can cause an interruption. If you move the nameservers or the A, AAAA and MX records to an environment that isn't ready yet, your site becomes unreachable or your mail arrives at the wrong server, regardless of which registrar the domain is with.

The auth code

To move a domain name to another provider, the new provider needs an auth code, also called a token, transfer code or EPP code. The code belongs to the domain and is issued by the provider where the domain currently is.

The holder of the domain is entitled to that code. A provider may not use issuing it as leverage to make you stay, nor attach conditions to it that have nothing to do with the domain. If you request the code, you should get it.

In practice, many providers show the code in their control panel. If it isn't there, request it in writing, by email or through a ticket, so that you can point to a dated request if things don't go smoothly later.

If it doesn't work for a .nl domain

.nl domains are managed by SIDN. If you don't get the auth code, or the transfer gets stuck, you can report it to SIDN; SIDN has a procedure for that. For other extensions this lies with the registry concerned, and the rules differ per extension.

Keeping the switchover calm

The order below is not an official procedure; that differs per extension and per provider. It is the way of working that keeps interruptions small in practice.

  1. First write down what is currently in the DNS: A, AAAA, CNAME, MX and TXT records, with their values. If you don't, you will have lost that information at the moment you need it.
  2. Set the TTL of the records you are going to change low a day or two beforehand. A change is then known everywhere within minutes instead of hours.
  3. Set up the new environment and test it before anything points to it. Hold off on pointing to it until the website and mailboxes really work there.
  4. Then transfer the registration with the auth code. Technically, nothing changes here.
  5. Change the DNS to the new environment last. Then check: website, outgoing mail, incoming mail.
  6. Set the TTL back to its normal value once everything has been stable for a few days.

What a transfer requires exactly depends on the extension and on how your current environment is set up. If you want to know what is needed in your case, email info@hostage.nl with your domain name.

Where it usually goes wrong

  • The DNS is changed before the new environment is ready. That causes an immediate interruption.
  • The MX records are forgotten. The website moves neatly, but email keeps arriving at the old server, or stops arriving anywhere.
  • The SPF record isn't updated, so outgoing mail from the new server is marked as spam.
  • The TTL was high, so a correction only takes effect hours later.
  • The old hosting package is cancelled too soon, while it still holds the only copy of the website or the old mailboxes.

What we don't do here

We don't give you legal advice and can't act on your behalf towards your current provider: an auth code is issued to the holder, not to us. And we don't claim that a transfer always goes without interruption: with complex email setups or third-party services on subdomains, a brief hiccup is sometimes unavoidable. In that case we tell you beforehand.

What we do: help you even if you want to leave us. You get your auth code and, if you wish, help with the switch to the other party. You can read more about that on no lock-in (in Dutch).

Further reading

Was this article helpful?

Still stuck?

Send us a message. We will help you, usually within one working day.