A business can use a domain every day without knowing who controls its registration. The website works, email arrives and renewal invoices appear, so the arrangement feels settled. The uncertainty often surfaces when the business appoints a new agency, replaces a member of staff or needs urgent access after an account problem.
Checking domain ownership means more than finding the company that hosts the website. You need to identify the registered holder, the registrar, the people with account access and the arrangements for renewal and recovery. These roles may sit with different organisations. A short, documented audit can make future changes much easier.
Separate registration from website and email hosting
The registrant is the person or organisation recorded as registering the domain. The registrar provides the registration service. DNS determines where services for the domain are directed, while website and email hosting provide those services. One supplier may offer all of them, but they remain separate responsibilities.
Distinguish the domain registrant from the registrar providing the registration service. Check whether the registered holder and account arrangements match the organisation's intended position. Paying an invoice or accessing a website dashboard does not answer every part of that question. Our domain ownership guide explains the records and permissions to verify.
Start by making a list of domains the business relies on. Include the primary website domain, email domains, alternative spellings, campaign domains and names that redirect elsewhere. Mark which are operationally important and which are simply retained for future use.
Use official lookup tools to identify the registration route
For a UK domain, Nominet provides a registration lookup service. ICANN provides registration data lookup for supported generic domains such as .com. Record the registrar and available status or date information, then compare it with supplier records. The domain administration guide covers using these findings alongside account evidence.
Public registration data can be limited or redacted, including a holder's name or address. The absence of a visible name does not prove that the domain is unowned, wrongly registered or controlled by the person who built the website. Use the domain ownership checks to investigate the actual arrangements rather than relying on public display alone.
Treat lookup results as the beginning of the audit. They can help locate the correct registrar, but they do not give you access to a private account or settle a dispute between parties. Ask the registrar for the relevant process if the account records are unclear.
Check the registrant record inside the authorised account
Use an existing authorised login or ask the responsible supplier to provide the registration details securely. Review the holder's name, contact information and organisation details. Compare them with the business's current records, especially after a restructure, acquisition or change of trading name.
Be precise about what you are checking. A contact person named on an account may be an administrator rather than the registered holder. A billing contact may pay for renewals without controlling registration decisions. Ask the registrar to explain the meaning of fields that are ambiguous.
If the recorded holder differs from the intended holder, document the discrepancy and investigate the appropriate correction or transfer process. Do not assume that editing a contact field transfers registration rights. The required process depends on the registrar, domain extension and circumstances.
If there is a disagreement over entitlement, preserve the relevant records and seek suitable advice. A technical audit can establish access and recorded information, but it should not be presented as a definitive legal ruling.
Find out who can access and recover the account
Identify the account owner and authorised users. Check whether access depends on a former employee's personal email address, an agency's shared account or a device that the business no longer controls. These arrangements may work until a password reset or security check becomes necessary.
Use appropriate organisation-controlled accounts and individual access where the registrar supports them. Keep credentials in the business's approved password manager rather than in a general project document. Enable the available account protections and record who manages recovery information.
Consider whether recovery depends entirely on email using the same domain. If that email service becomes unavailable during an incident, the business may struggle to receive account recovery messages. Review supported recovery routes with the provider and make sure an authorised person can use them.
Give access according to responsibility. A developer updating DNS does not automatically need authority to transfer or cancel every domain. Review supplier permissions when a project ends and retain the access the business needs for ongoing administration.
Verify renewal responsibilities and payment arrangements
Record the next renewal information shown by the registrar and identify who receives notices. Check whether automatic renewal is enabled, how it is paid and who will act if payment fails. A setting labelled automatic renewal is useful only if the account and payment arrangements remain valid.
Use an internal reminder as an additional operational check. Assign it to a role that will still exist if a particular employee leaves. Include a sensible review period before the provider's deadline so that the business can resolve access or billing issues without urgency.
Ask the provider to explain its actual renewal and recovery procedures. Do not rely on a remembered grace period or assume that every extension follows the same timeline. Keep a link to current provider guidance with the inventory rather than copying rules that may later change.
Review unused domains separately from essential ones. Before deciding not to renew, check whether the domain still supports email, redirects, printed material or customer recognition. A domain that receives little website traffic can still be important to the business.
Record DNS and service dependencies before making changes
An ownership audit is not automatically a migration project. Establish the current arrangement before changing registrar, nameservers or hosting. Record where DNS is managed and which provider supports the website, business email and other services.
Ask the technical owner to document important DNS records and their purpose. Include mail delivery and authentication records, verification records for business tools and any subdomains used by customer portals or third-party platforms. Store the information securely where appropriate.
Changing nameservers can affect several services at once if required records are not present in the new DNS zone. A registrar transfer and a hosting move are also separate operations. Plan any proposed change with the relevant technical owner rather than using the audit as a reason to alter everything together.
Agree how changes are approved and recorded. A short change log showing the request, person responsible, affected services and checks after completion is valuable when troubleshooting later. It also reduces the chance that two suppliers make conflicting updates.
Resolve agency and staff handovers clearly
Where an agency manages the domain, ask for a written description of the arrangement. Identify the registered holder, access available to the business, renewal responsibility and process for ending the management service. A good arrangement can leave day-to-day administration with a supplier while preserving clear business control.
During a handover, request the records and permissions needed for continuity. Confirm access before removing the previous administrator. Check that renewal notices, support contacts and recovery routes no longer depend on someone who has left.
Use a checklist tied to actual services. The website login, registrar account, DNS dashboard and email administration console may all be separate. Receiving one password does not establish that the handover is complete.
Keep correspondence and invoices that explain the arrangement. These records can support a future account recovery request and help a new supplier understand the history. Avoid relying solely on informal assurances that someone else has everything covered.
Create a domain register the business can maintain
A practical domain register should record the name, business purpose, registrar, intended registrant, verified account owner, renewal responsibility, DNS provider and associated services. Add the date of the last check and links to the relevant account records or guidance. Do not include passwords in the register.
Assign an owner to keep it current. Review it when staff or suppliers change, when a new domain is registered and when a service moves. The value lies in maintaining the information through ordinary business changes rather than producing a document once and forgetting it.
Connect domain administration to the wider digital operation. Giraffe Digital's digital strategy service considers how websites, hosting, domains, email and business tools work together. If an audit leads to rebranding or a website move, involve the relevant website design and SEO planning early. Knowing who holds and controls the domain gives the business a firmer basis for those decisions.
Frequently asked questions
How should we separate registration from website and email hosting?
The registrant is the person or organisation recorded as registering the domain. The registrar provides the registration service. DNS determines where services for the domain are directed, while website and email hosting provide those services. One supplier may offer all of them, but they remain separate responsibilities. Distinguish the domain registrant from the registrar providing the registration service. Check whether the registered holder and account arrangements match the organisation's intended position. Paying an invoice or accessing a website dashboard does not answer every part of that question. Our domain ownership guide explains the records and permissions to verify. Start by making a list of domains the business relies on. Include the primary website domain, email domains, alternative spellings, campaign domains and names that redirect elsewhere.
How should we check the registrant record inside the authorised account?
Use an existing authorised login or ask the responsible supplier to provide the registration details securely. Review the holder's name, contact information and organisation details. Compare them with the business's current records, especially after a restructure, acquisition or change of trading name. Be precise about what you are checking. A contact person named on an account may be an administrator rather than the registered holder. A billing contact may pay for renewals without controlling registration decisions. Ask the registrar to explain the meaning of fields that are ambiguous. If the recorded holder differs from the intended holder, document the discrepancy and investigate the appropriate correction or transfer process. Do not assume that editing a contact field transfers registration rights.
How should we verify renewal responsibilities and payment arrangements?
Record the next renewal information shown by the registrar and identify who receives notices. Check whether automatic renewal is enabled, how it is paid and who will act if payment fails. A setting labelled automatic renewal is useful only if the account and payment arrangements remain valid. Use an internal reminder as an additional operational check. Assign it to a role that will still exist if a particular employee leaves. Include a sensible review period before the provider's deadline so that the business can resolve access or billing issues without urgency. Ask the provider to explain its actual renewal and recovery procedures. Do not rely on a remembered grace period or assume that every extension follows the same timeline.
How should we record DNS and service dependencies before making changes?
An ownership audit is not automatically a migration project. Establish the current arrangement before changing registrar, nameservers or hosting. Record where DNS is managed and which provider supports the website, business email and other services. Ask the technical owner to document important DNS records and their purpose. Include mail delivery and authentication records, verification records for business tools and any subdomains used by customer portals or third-party platforms. Store the information securely where appropriate. Changing nameservers can affect several services at once if required records are not present in the new DNS zone. A registrar transfer and a hosting move are also separate operations. Plan any proposed change with the relevant technical owner rather than using the audit as a reason to alter everything together.
How should we create a domain register the business can maintain?
A practical domain register should record the name, business purpose, registrar, intended registrant, verified account owner, renewal responsibility, DNS provider and associated services. Add the date of the last check and links to the relevant account records or guidance. Do not include passwords in the register. Assign an owner to keep it current. Review it when staff or suppliers change, when a new domain is registered and when a service moves. The value lies in maintaining the information through ordinary business changes rather than producing a document once and forgetting it. Connect domain administration to the wider digital operation. Giraffe Digital's digital strategy service considers how websites, hosting, domains, email and business tools work together.
