A domain handover is an ownership and access task, not just a website move. Public registration information can help identify the registrar and nameservers, but it cannot replace proof that you control the correct registrar account.
Look up the exact domain
- Open the WHOIS / RDAP Lookup tool and enter the domain name.
- Run the lookup and save the public report.
- Record the registrar, any displayed dates, nameservers and status values.
- Compare them with the domain in your registrar dashboard. Do not publish private account screenshots or transfer codes.
Read fields as evidence, not instructions
RDAP provides structured registration data. Public records can include registrar information, events, nameservers and domain statuses. Some personal contact information is redacted. A missing person's name does not prove suspicious ownership, and an event date should be read with its event label rather than assumed to be a creation or expiry date.
Prepare an access checklist
- Who controls the registrar account and its recovery methods?
- Can the owner renew the domain independently of the web developer?
- Which provider manages the DNS zone?
- Where are the current website and email records documented?
- Are any transfer restrictions or account protections visible in the registrar dashboard?
If you only need to move hosting, changing the registrar may be unnecessary. Agree the minimum change that achieves the business goal. A website migration, nameserver change and registrar transfer are distinct operations with different failure points.
Example: taking over a website from a previous supplier
Begin with the public lookup to identify where the domain is registered. Ask the supplier to confirm account ownership and provide a safe transfer or account-change process through the registrar. Export the existing DNS zone and take a website backup. Avoid changing nameservers until the new zone includes the mail and verification records you still need.
After the handover, confirm access, renewal settings and recovery details in the dashboard. Then check the public DNS records, open the website and send external test email. Keep a dated handover document so the next person managing the site knows which account owns each service.
What this lookup cannot tell you
Public data cannot prove that a seller is authorised to transfer the domain, predict every transfer condition, or establish trademark rights. An unavailable registry response is inconclusive. For an important domain, verify directly with the registrar and use an appropriate transaction process. Bring the domain and access checklist to a website handover discussion before making irreversible account changes.
Example: making sense of a privacy-protected record
Suppose the RDAP result includes a registrar, creation date and registration status, but no owner contact. That does not automatically indicate that the record is invalid: personal registration fields can be redacted or withheld under privacy rules. Start with the registry-provided structured fields rather than relying on third-party summaries.
For a suspected expiry issue, inspect the status codes and dates, then verify them with the registrar. These dates are not proof of trademark ownership, and a listed registrar is not necessarily the website developer or operator.
Sources and further reading
Turn the next step into a project
Need help with a brand identity, business website or launch assets? Explore SOPIDOTECH services and client projects, or discuss your brief.