Безопасная сделка - Гарант

Buying a live domain without disrupting the website or email

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.

Establish what the seller is entitled to transfer Website administration does not necessarily establish authority over the domain registration. Someone may maintain the site while another company holds the name. Alternatively, the domain may be in the right account but recovery channels may belong to a former employee. Looking at a working website does not settle either issue.

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.

Prepare a dependency map before touching DNS List the existing DNS records and the purpose of each group. Identify the main site, inbound email, support subdomains, outbound mail services and service-verification records. An unfamiliar entry may support a business-critical integration even if deleting it leaves the home page working. Record its owner before deciding that it is redundant.

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.

Use a six-step handover sequence 1. The buyer confirms the applicable procedure with the current registrar. Check the exact domain, transfer type, registration term and any restrictions. Do not start a process from an old forum guide while assuming it applies to the current name.

  1. Both parties capture the starting state: nameservers, DNS zone, critical URLs and test mailboxes. They agree which dependent subscriptions are included in the price. Any work outside the domain transfer receives its own owner and completion condition.
  2. The buyer prepares a secured destination account with independently controlled recovery methods. The seller performs the registrar-supported transfer action. Save confirmations without placing authorisation codes, identity documents or other sensitive data in a public project folder.
  3. The buyer verifies control in their own registrar account. Agree safe checks such as inspecting settings, reviewing contact management and confirming renewal capability. Avoid changing production DNS solely to prove that a button works when a less disruptive check establishes the required control.
  4. The parties execute any separately planned DNS or hosting cutover. After each change, test the agreed website paths, inbound and outbound email, and selected service endpoints. Compare results with the initial dependency map instead of accepting the handover because one page opens.
  5. The buyer records acceptance for the specified assets. The payment decision follows the agreed evidence and observation window. Where hosting migration is a separate service, distinguish an unfinished migration task from whether the domain registration itself has been transferred.

Create a compact acceptance matrix Use four rows: registration, DNS, website and email. The registration row identifies the buyer's account, expiry information and verified management actions. The DNS row records the saved zone, change owner and control-query results. The website row lists the chosen paths and a representative business operation. The email row records a test in both directions.

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.

Check transfer constraints rather than promising a closing time ICANN's registrant guidance describes restrictions on inter-registrar transfers for domains within the relevant policy framework, including some transfer locks and registrant-change effects. It is not a universal instruction for every country-code domain. Ask the registrar which registry rules and procedures apply to the actual name and intended operation.

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.

Respond to a cutover problem without making it larger If email breaks while the website remains available, investigate the mail dependencies in your map. Repeating the domain transfer is not a substitute for checking the affected service. Capture the current state and restore the agreed settings if the recovery plan calls for it. Then work through the cause with the relevant provider.

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.

Write a payment condition around an observable outcome A conditional settlement arrangement may link release to demonstrated registrar control and specifically agreed service tests. It cannot establish the seller's rights in a trademark or make website content part of a domain-only purchase. The acceptance protocol needs adjustment for the registry, registrar and transaction documents involved.

Use the website's asset-category overview to frame the enquiry, then ask explicitly whether any DNS or mail work is included.