Dental practice domain ownership should be verified as a separate part of a digital handoff. The buyer or authorized practice owner needs control of the registration, renewal, and recovery process—not merely permission to edit the website.
Keep this task distinct from changing the site's design, moving hosting, or replacing email. Those changes can affect patient access and should not happen accidentally during an ownership transfer.
Distinguish the assets
A domain registration, registrar account, DNS service, website host, email service, and website content are different assets. They may be controlled by different parties.
Create an inventory identifying the domain, current registrar, registrant arrangement, administrative owner, expiration date, renewal method, recovery contacts, and dependent services. Keep authentication secrets in the approved password-management system, not in the acquisition checklist.
Use the website review to identify public contact pathways that must remain reachable.
Confirm what the seller can transfer
Ask for evidence that the seller or its authorized entity has the right to transfer the registration. A developer may manage the account without owning the business's contractual rights; a domain may also sit in an agency account containing unrelated clients.
Have counsel resolve ownership and agreement questions. Do not accept a shared login as the entire transfer.
ICANN distinguishes a change of registrant from a transfer between registrars. Its guidance also describes circumstances in which transfer locks may apply. Confirm the current sequence and requirements with the registrar before making changes. ICANN registrant transfer FAQs
Plan the sequence around continuity
Decide whether the immediate goal is changing registrant control, moving to another registrar, or both. Ask the current and receiving registrars what authorizations, contacts, timing, and restrictions apply.
Do not change nameservers, mail records, or hosting settings merely because the registrar interface offers to set them up. Preserve the existing service configuration unless a separately approved migration requires a change.
Keep a record of the current DNS configuration through authorized technical staff. The record supports verification and recovery; it should not contain secret credentials.
Establish business-controlled recovery
Set up approved owner and backup access, multifactor authentication where supported, and recovery contacts controlled by the practice. Avoid leaving the former owner or a departing contractor as the only person able to renew or recover the account.
Confirm renewal responsibility and the payment arrangement. A transfer completion email does not prove that future renewals are funded or that recovery messages reach the right person.
Follow the registrar's supported delegation process rather than circulating one password among staff.
Verify control without disturbing the site
After the authorized transfer, verify:
- the registrar reports the intended registration and account control;
- the approved owner and backup can access their assigned functions;
- renewal and recovery settings are correct;
- the website and contact pages still load;
- business email works through an authorized test;
- patient-facing links still lead to the expected destinations.
Use fictional test information and avoid transmitting patient data for verification.
Connect any related record export to the data-migration workstream, but do not treat a successful website copy as proof of domain ownership.
Retain the handoff evidence
Save the agreement reference, provider confirmations, verified responsible people, completion date, and unresolved restrictions. Remove former access only after the new control and recovery paths have been tested and the removal is authorized.
A complete domain handoff leaves the practice able to maintain its address independently while keeping existing patient contact routes intact.
