How to Transfer Your Domain Name to AlexHost: A Complete Technical Guide

Transferring a domain name to a new registrar is one of the most consequential administrative tasks a website owner or systems administrator performs. Done correctly, it is seamless and causes zero downtime. Done incorrectly, it can result in DNS propagation failures, locked domains, expired authorization codes, or even accidental service interruptions lasting days.

This guide covers the entire domain transfer process to AlexHost end-to-end — from ICANN policy compliance and EPP authorization codes to DNS record updates and bulk transfer procedures — with the technical depth required to execute the process without errors.

What Is a Domain Transfer and How Does EPP Enable It?

A domain transfer is the process of moving administrative control of a registered domain name from one accredited ICANN registrar to another. The transfer does not affect the domain's registration expiration date negatively; in most cases, it adds one year to the existing registration term.

The technical backbone of every inter-registrar domain transfer is the Extensible Provisioning Protocol (EPP), defined in RFC 5730. EPP is a stateful, XML-based client-server protocol that standardizes how registrars communicate with domain registries. It handles domain provisioning commands — including <create>, <delete>, <renew>, <update>, and critically, <transfer> — in a structured, authenticated, and auditable way. Every ICANN-accredited registrar is required to support EPP, which is why the authorization code you obtain from your current registrar is universally recognized by the receiving registrar.

ICANN Transfer Policy: What You Must Know Before Starting

Before initiating any transfer, you are legally and technically bound by ICANN's Inter-Registrar Transfer Policy. Two clauses are especially critical and frequently misunderstood:

ICANN Policy Section 3.7.5 prohibits a transfer if the domain was created within the last 60 days. If you registered a domain yesterday, you cannot transfer it today — the registry will reject the EPP transfer command outright.

ICANN Policy Section 3.7.6 prohibits a transfer if the domain has already been transferred within the last 60 days. This prevents registrar-hopping abuse and protects domain owners from unauthorized sequential transfers. The only exception is a transfer back to the original registrar, provided both registrars mutually agree or a dispute resolution body directs it.

Additional ICANN-mandated transfer locks apply in these scenarios:

• The domain is under a Registrar Lock (status: clientTransferProhibited or serverTransferProhibited)
• The domain is involved in an active UDRP dispute
• The domain's WHOIS contact email is invalid or unverifiable, blocking the confirmation workflow
• The domain is within 60 days of expiration — some registrars refuse outbound transfers in this window

Verifying your domain's current status against all of these conditions before submitting a transfer request saves significant time and prevents failed transfer attempts.

Pre-Transfer Checklist: Five Steps Before You Submit Anything

Rushing into a transfer without preparation is the single most common cause of failed or delayed domain migrations. Complete every item on this checklist first.

Step 1: Verify the domain is eligible under ICANN policy

Check the domain's creation date and last transfer date in the public WHOIS record. Both must be more than 60 days in the past. Use a reliable WHOIS lookup tool or query the registry directly via whois yourdomain.com from a terminal.

Step 2: Unlock the domain at your current registrar

Every domain registered through a reputable registrar is locked by default to prevent unauthorized transfers. This lock appears in the WHOIS record as the EPP status code clientTransferProhibited. You must log into your current registrar's control panel and explicitly disable this lock. The option is typically labeled "Transfer Lock," "Registrar Lock," or "Domain Lock." After disabling it, allow a few minutes for the registry to update the status before proceeding.

Step 3: Verify and update WHOIS contact information

The administrative contact email address in the WHOIS record is where the transfer confirmation request will be sent. If this email address is outdated, bouncing, or protected by a privacy proxy that does not forward messages, the transfer will stall or fail entirely. Update the administrative contact email to an actively monitored inbox before initiating the transfer. If WHOIS privacy is enabled, either temporarily disable it or confirm that your registrar's privacy service forwards transfer-related emails.

Step 4: Disable DNSSEC if active

If your domain has DNSSEC (DNS Security Extensions) enabled, you must remove the DS records from the parent zone before transferring. Failing to do so can cause DNS resolution failures after the transfer, because the new registrar's nameservers will not have the corresponding DNSKEY records. Disable DNSSEC at your current registrar, confirm the DS records are removed from the registry, then proceed with the transfer.

Step 5: Obtain the EPP Authorization Code (Auth-Code)

Request the EPP auth-code (also called the transfer authorization code, auth-info code, or domain secret) from your current registrar. This is a unique alphanumeric string — typically 8 to 16 characters — that cryptographically confirms you are the authorized domain holder initiating the transfer. Most registrars deliver this code instantly via the control panel or by email upon request. The code is time-sensitive; many registrars expire it after 7 to 30 days.

Guard this code carefully. Anyone who possesses it can initiate a transfer of your domain.

How to Initiate a Domain Transfer to AlexHost

Once all pre-transfer conditions are satisfied, the actual submission process through AlexHost is straightforward.

Single Domain Transfer

1. Log into your AlexHost account and navigate to the Domain Registration section.
2. Select the Transfer Domain option.
3. Enter your domain name in the provided field.
4. Enter the EPP authorization code obtained from your current registrar.
5. Review the transfer details, confirm the administrative contact email, and submit the request.

At this stage, AlexHost's systems send an EPP <transfer op="request"> command to the relevant registry, including your domain name, the auth-code, and the gaining registrar's credentials. The registry validates the auth-code against its records.

Configuring DNS Records During Transfer

After submitting the transfer request, you can pre-configure your DNS records within the AlexHost control panel. This is a significant operational advantage — by setting up your A records, MX records, CNAME records, and TXT records (including SPF, DKIM, and DMARC entries) before the transfer completes, you minimize the window during which DNS resolution could be inconsistent.

If you are also hosting your website or email with AlexHost, this is the moment to point your DNS to the correct infrastructure. For teams managing email infrastructure, Email Hosting from AlexHost integrates directly with your domain's DNS management panel.

Bulk Domain Transfer

For organizations managing large domain portfolios, AlexHost supports bulk domain transfers. This is particularly useful for agencies, resellers, and enterprises consolidating domains from multiple registrars into a single management interface.

The bulk transfer input format is:

yourdomain.com:AuthCode1
anotherdomain.net:AuthCode2
thirddomain.org:AuthCode3

Enter each domain on a separate line, followed immediately by a colon and its corresponding EPP auth-code — no spaces. Submit the entire list in a single operation. AlexHost processes each transfer request individually against the respective registry, so different domains may complete at different times depending on the losing registrar's response speed.

Transfer Timeline: What Happens After Submission

Understanding the technical timeline prevents unnecessary support tickets and anxiety during the waiting period.

Key insight: Many losing registrars offer an "expedited release" option in their control panel. If your current registrar supports this, approving the transfer immediately rather than waiting for the 5-day auto-approval window can cut the total transfer time to under 24 hours.

TTL management tip: Before initiating a transfer, lower the TTL values on your critical DNS records (A, MX, CNAME) to 300 seconds (5 minutes) at your current registrar. Do this at least 24–48 hours before the transfer — long enough for the lower TTL to propagate. When the transfer completes and you update records at AlexHost, the changes will propagate globally in minutes rather than days.

Domain Transfer vs. DNS Change vs. Domain Registrar Change: Clarifying the Terminology

These three concepts are frequently confused, and conflating them leads to incorrect actions.

Changing your nameservers at your current registrar to point to AlexHost's DNS infrastructure is not a domain transfer. It is a DNS delegation change. The domain remains registered at your current registrar. A full transfer moves the registrar relationship entirely.

Post-Transfer: DNS Configuration and Infrastructure Setup

After the transfer completes and AlexHost becomes your authoritative registrar, updating and verifying your DNS records is the most operationally critical task.

Essential DNS Records to Verify

• A record: Points your root domain (@) to your server's IPv4 address
• AAAA record: Points your root domain to your server's IPv6 address (if applicable)
• CNAME record: Typically used for www subdomain aliasing
• MX records: Direct inbound email to your mail servers, with correct priority values
• TXT records: SPF policy, DKIM public keys, DMARC policy, and domain verification tokens for third-party services
• NS records: Confirm AlexHost's nameservers are listed as authoritative

If your domain points to a VPS Hosting environment, verify the A record reflects the correct public IP address of your VPS instance. For high-traffic or resource-intensive workloads, Dedicated Servers provide dedicated resources with full control over network configuration, making post-transfer DNS alignment straightforward.

SSL Certificate Continuity

A domain transfer does not invalidate existing SSL/TLS certificates. However, if your certificate is domain-validated (DV) and tied to your previous hosting environment, you may need to reissue it after updating your DNS records. Ensure your SSL certificate covers both the root domain and the www subdomain (or use a wildcard certificate). AlexHost provides SSL Certificates that can be issued and managed directly from your account panel after the transfer completes.

Control Panel Access

Once the domain is under AlexHost management, you gain access to a centralized control panel for DNS management, WHOIS updates, domain locking, auto-renewal configuration, and nameserver management. For teams that prefer cPanel-based management, VPS with cPanel integrates domain and hosting management into a familiar interface.

Common Transfer Failures and How to Resolve Them

Even experienced administrators encounter transfer failures. These are the most frequent causes and their solutions.

Auth-code rejected by registry

The auth-code is case-sensitive and expires after a set period. Request a fresh code from your current registrar and submit immediately. Confirm there are no leading or trailing spaces in the code field.

Domain status is clientTransferProhibited

The domain is still locked. Return to your current registrar's panel, disable the transfer lock, wait 5–10 minutes, and verify the status change in WHOIS before resubmitting.

Transfer confirmation email not received

Check the administrative contact email in WHOIS. If it is incorrect or protected by a privacy service, update it first. Also check spam folders — transfer confirmation emails are frequently misclassified.

Registry rejects transfer due to 60-day lock

This is a hard ICANN policy restriction. There is no workaround. Wait until the 60-day period elapses from the domain's creation or last transfer date.

DNSSEC validation failures after transfer

Remove DS records from the registry before initiating the transfer. After the transfer, re-enable DNSSEC at AlexHost and add the new DS records to the parent zone.

Losing registrar denies the transfer

A registrar can only legitimately deny a transfer if there is an active UDRP dispute, a court order, or a documented fraud report. If the denial is unjustified, file a complaint with ICANN's Registrar Compliance department.

Decision Matrix: When to Transfer vs. When to Change DNS Only

Use this matrix to determine the correct action for your situation.

Technical Key Takeaways

• Unlock the domain and verify WHOIS contact email before requesting the auth-code — not after.
• Lower DNS TTL values to 300 seconds at least 24 hours before the transfer begins.
• Disable DNSSEC and remove DS records from the registry before submitting the transfer request.
• The EPP auth-code is case-sensitive and time-limited; use it within 24 hours of receipt for best results.
• Bulk transfers use the format domain.com:AuthCode — one per line, no spaces.
• The 5-day ICANN transfer window can be shortened by approving the transfer immediately at the losing registrar.
• Post-transfer, verify all DNS record types — not just the A record — before considering the migration complete.
• SSL certificates may need reissuance after DNS changes; handle this proactively to avoid HTTPS errors.
• For new domains registered through AlexHost, explore Domain Registration to manage everything from a single panel from day one.

Frequently Asked Questions

How long does a domain transfer to AlexHost take?

The technical transfer completes within 24 hours of the losing registrar approving the request. The losing registrar has up to 5 days to respond before the transfer auto-approves. DNS propagation after the transfer can take an additional 24–72 hours depending on TTL values. Total elapsed time is typically 1–7 days.

Will my website go down during the domain transfer?

Not if you prepare correctly. Pre-configure your DNS records in the AlexHost panel before the transfer completes, and lower your TTL values 24–48 hours in advance. If your nameservers and DNS records are correctly set up at AlexHost before the transfer finalizes, visitors experience no interruption.

What is the EPP auth-code and where do I find it?

The EPP auth-code (also called transfer authorization code or auth-info code) is a unique alphanumeric string that proves you are the authorized holder of the domain. Obtain it from your current registrar's control panel under domain settings, or request it via their support. It is typically delivered instantly or within a few hours.

Can I transfer a domain that was just registered or recently transferred?

No. ICANN policy mandates a 60-day lock period after initial domain registration and after any inter-registrar transfer. Attempting a transfer during this window will result in a registry-level rejection regardless of which registrar you use.

What happens to my DNS records after the transfer completes?

Your existing DNS records are not automatically migrated. You must manually recreate or import them in the AlexHost DNS management panel. This is why pre-configuring DNS records before the transfer completes — and lowering TTL values in advance — is a critical best practice that prevents downtime.