Look at your company's domain and separate two questions: who is listed as the registrant, and who can access the account that manages it. Having the password does not prove registration rights; being listed as the registrant does not settle every access issue either.
Your inventory should include the domain, hosting, email and external accounts your system uses. For each, record the holder or contracting party, administrator, access recovery method and person receiving payment notices. That is a more useful check than simply finding an old invoice.
What a public lookup can tell you
ICANN Lookup retrieves registration data through RDAP. The registrant is the person or entity holding rights to the registered domain, as ICANN explains in its account of the registration process.
The lookup may not display the name you are looking for. ICANN's FAQs explain that some data may not be publicly available or may be redacted. A hidden field does not prove that the domain belongs to someone else. Nor should you confuse the registrar's name — the company providing the service — with the registrant.
If the domain ends in .es, use the lookup and procedures provided by Dominios.es. Its management follows its own rules. In any case, if a public lookup does not resolve the question, ask for confirmation from the registrar or from the account panel showing the registration holder's details. A screenshot can help, but should be checked against the account and service documentation.
Control does not end with the name
Review these four parts with whoever manages the domain:
- The account: who can recover it and where its notices go. Keep the access procedure somewhere safe; passwords do not need to circulate by email.
- DNS: where the records directing the website and email are managed, and who has permission to change them. Keep an export or an up-to-date inventory before changing anything.
- Renewal: the date, planned payment and destination of notices. Check who will investigate a failed charge; automatic renewal needs follow-up too.
- The handover: what documentation, access and data will be delivered if the provider changes. Transferring a domain to another registrar and changing its registrant are different operations.
Do not change DNS records just to experiment: reviewing access does not require interrupting your website or email.
A clause worth agreeing at the start
Under my contract, domains, accounts with external providers used by the system and any digital asset owned by the client are registered and billed in the client’s name, and the client grants me delegated administrative access. If you compare with another provider, ask for their contract to say the same and explain how that access is withdrawn and what is handed over when the service ends.
The clause needs to match the actual accounts. If the contract says one thing and the panel another, there is administrative work left to do. There is no universal deadline for resolving it, nor does a transfer always depend on just one person: each registrar and extension has its own procedure.
This week, you can request the inventory in writing and choose the domain as your first check. The aim is to know who is listed in the registration record, who controls the account and what you would need to keep operating when changing providers.
Sources
- ICANN · Registration data lookup — Public registration data lookup through RDAP.
- ICANN · Domain registration process — The registrant holds rights to the registered domain.
- ICANN Lookup · FAQs — Redacted or nonpublic data alone cannot identify the registration holder.
- Dominios.es · FAQs — Lookup and procedures specific to .es domains.
If you want to review who holds your business’s digital assets and who can access them, let’s talk.