Buying a domain requires two separate outcomes: control of the name and continuity of the services using it. A registrant change, a move between registrars and a DNS cutover are different operations. Plan them separately before sending the purchase money. Inventory the website, email and dependent services, agree who performs each change and define how the buyer will demonstrate control. A message saying that credentials have been sent is not a useful acceptance condition for a live business domain.
Ask for evidence through the registrar's official interface and reconcile the seller, contracting party and authorised representative. Do not ask the seller to display passwords during a screen share. Public registration data may be restricted or redacted. Missing public identity information is not proof of wrongdoing, but it also does not replace a check of authority and the registrar's transfer process.
Confirm the purchase boundary. A domain name, website files, brand rights and a mailbox archive are separate assets. Record which ones are included and which agreements govern them. If your objective is to acquire an operating website, a domain-only contract can leave the most valuable materials outside the handover.
For each dependent service, note the account holder, billing owner, technical contact and proposed destination. Save an export of the current zone and explain the entries in plain language. Where registration and DNS are sold by the same provider, do not assume that changing the registrant also transfers every other product in that provider account.
Set up a contact address outside the domain being acquired. It should remain available if the domain's email stops working. Also identify who can restore the previous configuration. A rollback plan that relies entirely on the seller's access becomes unusable if that access is removed during the same handover.
Each row also needs a reviewer, test time, failure condition and recovery action. For example, a missing test email should trigger checks of the intended mailbox and service logs before changes are made. A single delayed message does not prove that all mail has been lost. At the same time, a functioning website is not a reason to ignore a mail delivery failure.
A commercial arrangement might release one part of the price when registrar control is established and another after a separately purchased mail migration. The amounts should reflect the parties' actual scope and risk. No universal retention percentage makes all domain transactions safe. A suggested split must not be presented as an ICANN requirement or an operator's confirmed payment rule.
Avoid promising a fixed handover duration before the restriction check. If the seller proposes bypassing a lock through an unrelated person's account, stop and seek an official explanation. If expiry is approaching, agree who renews the name and what evidence establishes that renewal. Urgency can affect the calendar, but it should not remove the authority check.
Refusal to demonstrate control through official channels, an offer to hand over only a shared account password or pressure to delete the entire zone should stop final payment. Redacted public data or differing DNS observations, however, may have legitimate explanations. Record the discrepancy and investigate rather than treating every unusual result as proof of fraud.
If the registrar blocks the transfer, preserve the official response and revise the timetable. Starting a transfer is not the same as completing it. If the buyer controls the domain but lacks website content, return to the asset schedule and determine whether that content was included. Do not solve a scope dispute by making unplanned DNS changes.
Use the website's asset-category overview to frame the enquiry, then ask explicitly whether any DNS or mail work is included.