The Technical Process Behind Domain Transactions: A Step-by-Step Guide

The Technical Process Behind Domain Transactions: A Step-by-Step Guide

Reading time: 6 minutes

Domain transactions involve more than just signing a contract; they encompass a series of technical processes that must be executed correctly to ensure a smooth and secure transfer of ownership. As the editorial director for Domenemeglerskolen, I will detail the technical steps involved when a domain name changes hands, focusing on what Norwegian business owners and investors need to know.

1. Preparation for Transfer: Verification and Availability

Before the actual transfer can begin, certain preparations must be made. These are critical steps to avoid delays and complications.

1.1 Verification of the Domain and Ownership

• WHOIS Lookup: The buyer should always perform a WHOIS lookup to confirm the domain's current owner, registrar, registration date, and expiration date. This ensures that the seller actually has the right to sell the domain.
• Registrar Lock: Many domains are protected by a 'registrar lock' (also called 'transfer lock' or 'clientTransferProhibited'). This must be deactivated by the seller with their registrar before a transfer can be initiated.
• Privacy Protection Settings: If the seller has activated privacy protection (e.g., via services like WHOIS privacy), this must be temporarily deactivated for the buyer to verify ownership and for the new registrar's systems to retrieve correct information.

1.2 Obtaining the Authorization Code (EPP Code)

An EPP code (Extensible Provisioning Protocol), also known as an 'authorization code' or 'transfer code', is a unique alphanumeric code that acts as a password for the domain transfer. The seller must obtain this code from their current registrar and securely share it with the buyer or domain broker. Without this code, the transfer cannot commence.

2. Initiating the Transfer with the New Registrar (Buyer's Registrar)

Once the preparations are complete, the buyer can initiate the transfer process.

2.1 Ordering a Domain Transfer

The buyer selects their preferred registrar (or retains their existing registrar if they already have one) and orders a 'domain transfer' rather than a new registration. They will be asked to provide the domain name and the EPP code.

2.2 Approving the Transfer

After the transfer is initiated, the new registrar sends a request to the old registrar (via the registry, e.g., Norid for .no domains, or ICANN for generic top-level domains like .com). Often, both the seller and buyer will receive emails to confirm and approve the transfer. It is crucial to respond to these promptly, as they often have a time-limited validity (e.g., 5 days).

3. Technical Transfer and DNS Updates

The actual transfer of control and ownership occurs over a period.

3.1 Transfer Period

For generic top-level domains (.com, .net, .org), a transfer can take 5–7 days from initiation to completion, according to ICANN rules. For national top-level domains like .no, the process is often faster, typically 1–3 days, as Norid has specific rules that simplify the process. During this period, the domain is technically in a 'pending transfer' status.

3.2 DNS Changes and Pointing

This is a critical point to avoid downtime for any services associated with the domain (website, email).

• Before Transfer: If the domain is in use, the buyer should set up their own DNS servers with their registrar and copy all existing DNS records (A-records, MX-records, CNAMEs, etc.) from the seller's setup. This ensures that when the DNS pointing changes, services will point to the buyer's servers without interruption.
• After Transfer: Once the domain is transferred to the buyer's registrar, the buyer can change the nameservers (DNS) to their own. These are typically two or more URLs (e.g., ns1.yourregistrar.com, ns2.yourregistrar.com) that point to the DNS servers of the new registrar or a third-party DNS hosting service.
• Propagation: After changing nameservers, it will take time for these changes to propagate globally. This can take anywhere from a few minutes to 48 hours, depending on ISPs and DNS caching. During this period, some users may still see the old version of the website, while others see the new.

Example: A company acquires the domain companyname.com. Before the transfer, they copy all DNS records from the seller's DNS servers to their own. After the transfer, they change the nameservers for companyname.com with their registrar to ns1.newregistrar.com and ns2.newregistrar.com. This ensures their new website and email begin functioning seamlessly after propagation.

4. Verification and Post-Transfer Tasks

Once the transfer is technically complete, it is important to double-check everything.

4.1 Confirmation of Ownership

The buyer should perform a new WHOIS lookup to confirm that they are now listed as the registrant and that the new registrar is correct.

4.2 Security Updates and Settings

• Registrar Lock: Activate the registrar lock on the domain with the new registrar to prevent unauthorised transfers.
• Two-Factor Authentication (2FA): Enable 2FA on the registrar account for added security.
• Renewal Settings: Ensure the domain is set for automatic renewal to avoid accidental loss of the domain upon expiration.

Security in Domain Transactions

Security is paramount. Always use reputable domain brokers as recommended by Domenemeglerskolen, and an escrow service to hold the purchase funds securely until the domain is fully transferred. Be extremely cautious with email-based communication, as phishing and scams are common. Double-check senders and links, and never share sensitive information like EPP codes via unencrypted channels.

Conclusion

The technical process behind domain transactions can seem complex, but by systematically following these steps, both business owners and investors can ensure a safe and efficient transfer. A solid understanding of DNS, registrar transfers, and security protocols is key to success in domain brokerage.