Skip to content

When the domain is registered by the previous web designer

By The Onbo team · Updated

Short answer

Have the client look up where the domain is registered, then ask the previous designer to transfer it into an account the client owns. If they don't respond, the client contacts the registrar with proof of identity and ownership. You guide the process, but the client owns and controls the domain; you should never need their password.

You’re ready to launch a new website, and then you discover the client’s domain isn’t in their account at all. Years ago their previous designer registered it on their behalf, in the designer’s own account, and the client has no login. Now the domain renewal, DNS settings and launch all depend on someone the client hasn’t spoken to in a long time. It’s more common than it should be, and usually solvable with a calm, step-by-step approach.

Why does this happen?

Usually with good intentions. A designer offered to “sort out the domain” to save the client a task, registered it in their own reseller or personal account, and handled renewals. That works until the relationship ends. The client then has a domain they pay for, or think they own, but can’t control. Sometimes the previous designer has simply moved on and forgotten; occasionally they’re unhelpful. Either way, the domain should end up in an account the client owns.

How do you find out who controls the domain?

Start with a public domain lookup, which shows the registrar the domain is held with and when it expires. Then check what the client has: renewal emails, invoices and any old account details. If a renewal date is close, act quickly; recovery is far easier before a domain expires than after. Note what the website and email currently depend on, because changing DNS carelessly can break the client’s email.

How does the client get the domain back?

The client leads this; you guide them. The steps usually go in this order:

  1. The client asks the previous designer to transfer the domain into an account in the client’s name, or to the client’s chosen registrar. A short, friendly message explaining that the business is taking over its own accounts works well.
  2. If there’s no reply, the client contacts the registrar directly, explaining that they’re the business the domain represents, with proof such as business registration, invoices and correspondence.
  3. For country-code domains, the relevant registry may have its own dispute process if the registrar can’t help.
  4. If the previous designer refuses, the client may need legal advice; their original contract with that designer may say who owns the domain.

This is general guidance, not legal advice; the details vary by registrar and country.

Situation Next step
Designer cooperative Transfer into the client’s own account
Designer unresponsive Client contacts the registrar with proof
Country-code domain dispute Registry’s own process
Designer refuses Client seeks legal advice
Renewal date close Act now; ask the registrar about renewal options

How do you keep the project moving meanwhile?

You can usually finish the build on staging while the domain is resolved. If it takes longer, the new site can sometimes launch once the domain’s DNS is pointed to the new host, which the current account holder can do. Agree with the client in writing how the delay affects the launch date. Keep anything involving accounts arranged directly with the client, and never take on their passwords; see how to get website access from clients.

For example, a web studio might find, two weeks before launch, that a client’s domain sits in a former designer’s account. The client emails the designer using wording the studio suggests, the designer starts the transfer within two days, and the studio confirms the new account belongs to the client before pointing the domain at the new site.

How do you prevent it on future projects?

Check domain ownership during onboarding, not at launch: ask who owns the domain, which email it’s registered to, and when it renews. Make sure new domains are registered in the client’s own account. Write domain and hosting responsibilities into your agreement; the web design contract checklist lists the clauses, and the website project kickoff is where to confirm them.

A domain recovery checklist

  • Domain looked up: registrar and expiry date
  • Renewal risk checked
  • Current website and email dependencies noted
  • Client asks the previous designer to transfer
  • Transfer goes to an account in the client’s name
  • Registrar contacted with proof if needed
  • Launch date impact agreed in writing
  • No passwords shared with you
  • Domain ownership checked at onboarding next time
  • Domain responsibilities in the agreement

Where Onbo fits

Onbo helps you catch this at the start. Your website questionnaire, sent after the client accepts your agreement and pays, can ask who owns the domain, where it’s registered and when it renews. Onbo never collects passwords or logins, so access stays a direct arrangement between you and your client. Try it free for 30 days; see pricing.

Questions

What if the client's domain is registered by their old designer?

Help the client ask the previous designer to transfer it into an account in the client's own name. Most designers who registered it on the client's behalf will cooperate.

What if the previous designer won't respond?

The client can contact the registrar directly with proof of identity and of the business the domain represents. For country-code domains, the relevant registry may have its own dispute process.

Should I register the client's domain in my account?

No. Register it in the client's own account, with their email, and get access through delegated roles or invites if you need it.

Start your next client relationship with everything in place.

Collect the first steps in one link. Try Onbo free for 30 days, no card required.

Start free