Domain Transfers In and Out – EPP Codes and Registrar Locks

A domain transfer moves your registration from one registrar to another. Hosting doesn’t move automatically — they’re separate concerns, and you can transfer the domain while hosting stays put. The process is standardized across registrars but involves several specific steps and email confirmations that trip people up. This guide walks through transferring a domain IN to iWebVault, transferring OUT to another registrar, and what to do when things stall.

Transfer vs. moving hosting — clarify the difference

• Domain registration — who you pay the annual fee to, and who controls DNS by default.
• Hosting — where your website files live.

Common setups:

• Registered at Registrar A, hosted at Registrar A. (single-vendor)
• Registered at Registrar A, hosted at iWebVault. (separate)
• Registered at iWebVault, hosted at iWebVault. (consolidated)

Transferring domain registration doesn’t affect hosting. Your site keeps running at iWebVault while the registration moves between registrars.

Prerequisites at the current registrar

Before initiating a transfer, the domain must be in a transferrable state at the current registrar:

• Older than 60 days. Newly registered domains can’t transfer for 60 days (ICANN rule).
• Not within 60 days of expiration on most TLDs. Renew first, then transfer.
• Registrar lock disabled. Lock prevents transfers; must be off.
• Privacy protection considered. Some registrars don’t transfer domains under WHOIS privacy. Disable temporarily, transfer, re-enable at new registrar.
• Admin contact email accessible. You’ll receive critical confirmation emails there.

Transferring TO iWebVault — step by step

At the current registrar (sending side)

1. Log into your account at the current registrar.
2. Find domain management → your domain.
3. Disable registrar lock (also called Transfer Lock or Domain Lock). Toggle from locked to unlocked.
4. Get the EPP code (also called authorization code, auth code, or transfer key). Usually shown or emailed to you on request.
5. Disable WHOIS privacy (if enabled) — for the duration of the transfer only.
6. Verify the admin contact email is one you can read right now. Some registrars send the confirmation here.

At iWebVault (receiving side)

1. iWebVault → Domains → Transfer.
2. Enter the domain → it checks if transferrable.
3. Enter the EPP code from previous step.
4. Pay for the transfer (transfer = one year of registration + transfer fee, typically the cost of a year of registration).
5. Confirm.

The transfer process (3-7 days)

1. iWebVault notifies the current registrar of intent to transfer.
2. Current registrar emails the admin contact for confirmation. You must approve this email. Look for it within hours of initiating transfer.
3. Once approved, current registrar releases the domain (usually 5-7 days, sometimes faster).
4. Domain appears in your iWebVault account.
5. You’re added a year onto the registration. Domain works normally throughout — no downtime.

Post-transfer

• Re-enable registrar lock at iWebVault (transferring domain is now locked here for 60 days regardless — ICANN rule).
• Re-enable WHOIS privacy if you use it.
• Verify DNS records came across correctly — if you’d customized records at the previous registrar, they should be preserved, but verify.

Transferring OUT of iWebVault

Reverse process — same standards apply.

1. Log into iWebVault client area.
2. Domains → your domain → Management.
3. Disable registrar lock.
4. Get EPP code (request it; sent to admin contact).
5. Verify admin contact email is current.
6. Go to the new registrar and initiate transfer there using the EPP code.
7. Approve confirmation email when it arrives.
8. Wait 5-7 days; domain appears at new registrar.

We don’t block transfers out. The ICANN process is what it is — provide the EPP code, you transfer.

The EPP code explained

• EPP code = Extensible Provisioning Protocol authorization code. Other names: auth code, transfer authorization code, AuthInfo, transfer key.
• Looks like a random string: aB3#kL9$mN2qPxYzW or similar.
• Acts as a password proving you authorize the transfer.
• One-time use — once a transfer completes, the receiving registrar generates a new EPP code for the next time.
• If your code doesn’t work, request a fresh one from the current registrar.

EPP codes for many TLDs (.com, .net, .org) are full ASCII strings. Some country-code TLDs use simpler formats.

When transfers fail or stall

“Domain is locked at current registrar”

Most common stall. Go back to current registrar, disable the lock, retry transfer.

“EPP code doesn’t work”

EPP codes can have special characters that get mangled when emailed. Get the code freshly, copy carefully, paste directly. If it still fails, request a fresh code.

“Approval email not arriving”

Goes to the admin contact email on the WHOIS record. If that email is wrong or inaccessible:

• Update admin contact email at current registrar first, wait for the update to propagate (24-48 hours).
• Then initiate transfer.

If using WHOIS privacy and emails are routed through a privacy email, those usually still forward — check spam folder.

“Current registrar is dragging their feet”

Some registrars deliberately make outbound transfers slow. Per ICANN rules:

• They have 5 days to respond to a transfer request.
• If they don’t respond, transfer auto-completes after the wait period.
• If they actively block without legitimate reason, you can complain to ICANN.

Most legitimate registrars don’t drag deliberately. Some smaller ones do. Patience usually wins.

“Domain expired during transfer”

Transfer doesn’t pause expiration. If domain expires mid-transfer, things get complicated. Always renew well before initiating a transfer near expiration.

Special cases

Country-code TLDs (.uk, .de, .ng etc.)

ccTLDs have varying transfer procedures. Some don’t use EPP codes — they use registry-specific change-of-registrar codes, different waiting periods, or require physical paperwork.

• .uk: uses a “tag change” instead of EPP. Current registrar changes the IPS tag to the new registrar’s tag.
• .de: EPP code but check the DE-NIC process.
• .ng: standard EPP, similar to .com.

For ccTLD transfers, check the specific registry’s documentation, or ask the receiving registrar. ccTLD guide.

Premium / aftermarket domains

Domains bought from auctions or premium markets sometimes have special transfer restrictions. Check with the selling marketplace.

Recently renewed domains

Some registrars apply a “renewal lock” preventing transfer for a period after renewal (15-30 days typically). If you renewed recently, wait the period out.

What you keep vs. what you might lose

• ✓ Domain name itself.
• ✓ Expiration date (plus one year added by transfer fee).
• ✓ DNS records (usually copied over, but verify).
• ✗ Free addons from current registrar (privacy, SSL, email) — those don’t follow.
• ✗ Domain forwarding rules — usually need to recreate at new registrar.
• ✗ Any tied services (email, hosting at the old registrar continue, but managed in their own UI).

Why consolidate registration with hosting

• One bill, one renewal date, one vendor.
• Easier troubleshooting (we can check both registration and hosting on issues).
• Less risk of expired domain due to changing email addresses.

That said, some users intentionally split for security (compromise of hosting doesn’t compromise domain control). Both approaches are valid.

What’s next

• DNS basics (relevant whenever transferring): DNS records.
• Country-code TLD specifics: ccTLDs guide.
• If transferring out of iWebVault: just open a support ticket if you want help with the process.

Domain transfers are standardized and usually uneventful once you know the steps. Disable the lock, get the EPP code, initiate at the receiving registrar, approve the confirmation email, wait. The waiting is the longest part — be ready to be patient for 5-7 days while the domain quietly changes hands.