Domain ownership and transfer risks: what to check

Separate registration from hosting

A domain registration, authoritative DNS, website hosting and email hosting are separate responsibilities, even when one supplier invoices for all of them. Identify the registrant, registrar, renewal contact and the person who can approve changes. CIPC advises using the company’s name as registrant to reduce ownership disputes.

Use a business-controlled account and recovery contact that remains available if the domain’s own email service is interrupted. Keep access protected and shared through an approved business process rather than one employee’s personal mailbox.

Inventory dependencies before changing anything

Request an export of current DNS records and identify which services rely on them. A registrar transfer and a nameserver change are different operations: decide explicitly whether either is needed. Moving the website should not silently remove mail-routing or sender-authentication records.

• Confirm renewal date, payment responsibility and access to authorisation channels.
• Check the current transfer procedure with the registrar for the specific domain suffix.
• Preserve mail, website, verification and other service records in the migration plan.
• Agree a change window, rollback instructions and a responsible contact on each side.
• Test the website, inbound and outbound email, and important subdomains after the change.

Make the exit arrangement explicit

Before appointing a provider, ask what happens on cancellation: who releases access, what fees remain payable and how long handover takes. Keep a record of business authority to act for the registrant. A domain should not become an undocumented dependency on an agency relationship.

Bring your current registrar and DNS inventory to a domain-services discussion. Do not post passwords, transfer credentials or full private account screenshots in a support thread or public case study.