A Domain Ownership Handover Checklist for Businesses

A business can lose access to its website, email or online identity when a developer, former employee, agency or other third party controls the domain account. The problem may not become visible until a renewal is due, a website needs to move, or an urgent DNS change is required.

A domain handover is the process of transferring control and essential information from one person or service provider to the business owner or a new responsible administrator. It should leave the business with working access, accurate records and a clear understanding of how the domain connects to the website and email.

This checklist is useful when changing developers, moving to a new hosting provider, taking over an existing business, ending an agency relationship or reviewing who controls your digital assets. It applies to Nigerian businesses and organisations using a local or international domain, business email and a hosted website.

1. Confirm which domain names the business owns

Start by creating a complete list of domains connected to the business. Do not record only the domain used on the website. A company may also own domains for email, redirects, campaigns, older websites, alternative spellings or different locations.

  • Primary website domain, such as yourbusiness.com or a suitable Nigerian domain.
  • Alternative extensions and common spelling variations.
  • Domains used for landing pages, online stores or special campaigns.
  • Domains connected to staff or customer email accounts.
  • Expired, parked or unused domains that may still be important to the brand.

For each domain, note its exact spelling, extension, registrar, expiry date and current purpose. This simple inventory can reveal domains that were registered separately by different people.

2. Identify the registrar and the real account owner

The registrar is the company through which the domain was registered. It may be a hosting company, domain specialist, web agency or another service provider. Hosting and domain registration are often purchased together, but they are separate services. A website can move to new hosting while the domain remains with the same registrar.

Ask for the registrar name and the account login used to manage the domain. The business should control this account, rather than relying permanently on an individual developer’s personal email address.

Check whether the account contains other customers’ domains. If it does, avoid taking over a shared account without understanding the risks. A cleaner arrangement is for the business domain to be held in an account dedicated to the business, using an organisation-controlled email address.

3. Replace personal contact details

Review every contact associated with the domain and registrar account. Important notices may be sent to the registrant, administrative, technical or billing contacts, depending on the provider and domain extension.

Update details that belong to a former employee, freelancer or agency, including:

  • Account email address.
  • Registrant or organisation name.
  • Phone number.
  • Billing contact.
  • Recovery email address.

Use an email address that the business can retain over time, such as an address managed by the organisation. Avoid using a temporary staff mailbox as the only recovery method. Make sure the organisation name is accurate and keep a copy of any registration information or confirmation messages.

For businesses using a Nigerian domain or another country-specific extension, record any provider-specific requirements separately. Domain rules and transfer processes can vary, so do not assume that a process used for one extension will work for another.

4. Secure the registrar account

Once access has been confirmed, change the password and remove people who no longer need access. Use a long, unique password that is not reused for hosting, email, WordPress or social media.

Where the registrar supports it, enable multi-factor authentication. Review recovery methods as well as active sessions, delegated users and API access. A former administrator may still be able to enter the account through a saved session or an old recovery address even after the main password is changed.

Store the credentials in a secure password manager or another controlled business process. Do not leave the only password in a chat message, spreadsheet shared with many people or a personal notebook that may be lost.

5. Record renewal dates and payment arrangements

An expired domain can interrupt a website, email and other services that depend on it. During the handover, record the expiry date for every domain and decide who is responsible for renewal.

  • Confirm whether automatic renewal is enabled.
  • Check which payment method is attached to the account.
  • Set more than one renewal reminder.
  • Assign a named person or team to monitor notices.
  • Keep billing details current and accessible to the business.

Automatic renewal is useful, but it should not replace monitoring. A failed payment, expired card or incorrect billing email can still interrupt the process. Businesses should also know how to renew manually if necessary.

6. Document the DNS records before making changes

DNS records tell the domain where different services are located. They can connect the domain to a website, business email provider, verification service, online store or other platform. Changing them without documentation can make a website or email stop working.

Request a current copy or screenshot of the DNS zone, including relevant records such as:

  • A and AAAA records pointing the domain to web servers.
  • CNAME records used for subdomains or connected services.
  • MX records that direct incoming business email.
  • TXT records used for verification and email security settings.
  • Nameservers showing which provider manages the DNS zone.

Do not delete records simply because their purpose is unclear. Ask the hosting or email provider before changing anything. A practical handover document should explain what each important record supports, such as the website, email, customer portal or marketing platform.

7. Confirm control of hosting and website files

Domain ownership does not automatically provide access to website hosting. Obtain the hosting account details, control panel access and information needed to manage the site.

Confirm where the following are stored:

  • Website files and databases.
  • WordPress administrator accounts, if applicable.
  • Backups and instructions for restoring them.
  • SSL certificate or HTTPS configuration.
  • Scheduled tasks, integrations and staging environments.
  • Server, control panel or managed support contacts.

Test the access instead of accepting a list of credentials without checking. For a WordPress website, confirm that the business has an administrator account and remove unnecessary former users. If the site is being moved to a new host, take a verified backup before migration and confirm that the restored version works.

8. Protect business email during the handover

Email deserves special attention because it may be more important to daily operations than the website. A DNS mistake can prevent staff from receiving enquiries, invoices, order notifications or customer support messages.

List the current mailboxes, forwarding addresses, aliases and shared inboxes. Record which service hosts them and who administers that service. Before changing nameservers or MX records, confirm the correct replacement settings with the email provider.

Also review email security records such as SPF, DKIM and DMARC where they are in use. These settings help receiving mail systems assess whether messages are authorised, but they must match the actual email service. Copying records from an old provider after switching services can create delivery problems.

9. Check transfer and access restrictions

If the business plans to move the domain to another registrar, first check whether a transfer lock, pending change or verification requirement applies. The process may require an authorisation code or approval from the current account. Keep control of the current registrar until the transfer is complete and tested.

Do not treat a transfer as the only handover option. Sometimes retaining the domain at the current registrar and changing DNS is simpler and less disruptive. The right choice depends on account control, support, pricing, renewal arrangements and the technical needs of the business.

10. Test everything before closing the handover

A handover is complete only when the business can operate without depending on the previous administrator. Run a short test after access and settings have been updated:

  • Open the website on a phone and computer.
  • Confirm that HTTPS works correctly.
  • Send and receive test business emails.
  • Test important contact forms and customer actions.
  • Check that DNS records resolve as expected.
  • Verify that backups exist and can be restored or accessed.
  • Confirm that the business can log in to the registrar and hosting accounts.

Keep a dated handover record containing domain details, account owners, renewal dates, DNS notes, service providers and escalation contacts. Store it securely and review it whenever staff, vendors or hosting arrangements change.

A simple ownership rule for every business

The business should own the domain account, control the recovery email, monitor renewals and retain access to the website, hosting and business email. A developer or hosting provider can manage technical work without becoming the permanent owner of the organisation’s essential digital assets.

For a small business, this does not require becoming a server administrator. A reliable hosting or managed WordPress provider can handle complex technical tasks while the business keeps clear ownership and receives understandable guidance. The key is to separate technical support from ownership.

A well-documented handover protects more than a website address. It helps preserve customer communication, online credibility and the stable digital home that a business builds over time.