Domain name being held hostage? How to get it back, step by step
Find out who really holds your domain, get the transfer code if it's yours, and what to do when a former web designer won't let go: demand letter, UDRP, ACPA and a plan B.
Find out who holds your domain, hosting and Google accounts, move each one into your name, and learn what to do if your developer refuses to hand over access.
If your web developer disappeared, you can usually get your website back, because the accounts it runs on (domain, hosting, Google) belong to companies that have recovery processes. Start with the domain. Look it up in ICANN Lookup to see the registrar and the expiry date, then get the domain moved into an account in your name. Everything else follows from that.
This guide is a 7-day plan for the "my web developer disappeared" problem, plus what changes when the developer refuses to hand over logins. A site nobody holds the keys to keeps running until something changes: a renewal notice lands in the developer's inbox, the contact form breaks, or the card on the hosting account expires. That is when the calls stop.
Work one layer a day, in order.
| Day | What to do | Why it comes here |
|---|---|---|
| 1 | Send one written request, then list every account | You can't recover what you haven't named |
| 2 | Get control of the domain | It controls your site and email, and can expire |
| 3 | Get into the hosting or site builder | It holds the files and database |
| 4 | Reset the website admin, take a full backup | So the site stops depending on one person |
| 5 | Reclaim Google accounts and email | Several can be proven through the domain |
| 6 | Escalate in writing if they refuse | A paper trail speeds up any dispute |
| 7 | Lock it down, brief the next developer | So it doesn't happen twice |
Send one short, polite message by email and text. Ask for the logins to your domain, hosting and website admin, or for those accounts to be moved into your name, within 7 days. Say you only need access, not more work. Keep a copy.
Then list every account your site and leads depend on. This is the checklist we use when we take over a site:
To find accounts you didn't know about, search your inbox for your domain name plus invoice, renewal or receipt, and check 2 years of card statements. Save those statements, your contract and the developer's invoices in one folder as your proof of payment.
Send your website and we will record a free 2 minute video showing the 3 fixes we would make first.
ICANN Lookup shows the registrar, dates and name servers, but usually not the owner. Under ICANN's Registration Data Policy, where redaction applies, the registrar hides the registrant's name, street and phone and publishes an email address or web form instead. That form is another way to reach a developer who has gone quiet.
The registrant holds the rights to the name, and it may not be you. ICANN's registrant FAQ explains that a developer may have registered the domain with their own contact details even though you paid, making them the registrant of record. It suggests checking with your registrar and showing proof of your payment to the developer. To make the handover easy, send the developer the exact steps.
The holder opens Domain List, clicks Manage, then uses Change Ownership on the Sharing & Transfer tab and enters the username or email of your own Namecheap account. Namecheap's account change guide says the move is free, no 60 day waiting period applies, DNS settings stay the same, and the change is final. An expired domain must be renewed first.
If the domain is close to expiring, Namecheap lets a third party pay for the renewal from a prefunded Namecheap account, through Live Chat. If the account holder doesn't object within 24 hours, it's renewed. The domain stays in their account, but you buy time.
Only the current owner can start the move. They invite you as a domain manager, open the domain's Permissions and choose Transfer Domain Ownership, then you accept from the email and add your payment method. Squarespace's domain ownership guide says DNS settings stay the same, but contact details don't update on their own, and changing the registrant name, organization or email needs approval from both the old and new email, so ask the developer to approve that too.
At GoDaddy, a listed registrant locked out of the account can file an account recovery request with a color copy of a government photo ID, plus business documents if a company is on the account. Elsewhere, search the registrar's help center for "account recovery" and ask support what proof it accepts. If the developer is the registrant and won't act, use the dispute route below.
Under ICANN's expired registration rules, renewal reminders go to the registrant email on the domain, which may be the developer's inbox, so put the expiry date in your own calendar. Before anyone changes the name servers, note where your email is hosted so mail keeps arriving.
Hosts and site builders deal with the account holder, not the business named on the site. Squarespace, for example, will only provide account details to the account holder, and its regain access form asks for a bank statement showing the accountholder name and the latest Squarespace charge. So the question is whose card paid.
On WordPress, try the "Lost your password?" link first. It sends the reset to the email on that admin account, which is often the developer's. If you have hosting access, WordPress documents other ways to reset the password, including phpMyAdmin, FTP and WP-CLI. Once you're in, create an administrator account with your own email, then remove or downgrade the developer's.
Then take a full backup, files and database, stored outside the hosting account.
If the hosting account is gone or the site was deleted, you rebuild from, best first: a backup the host kept, a copy from the developer, your own photos and text, and the Wayback Machine. It only collects publicly accessible pages, skips password-protected ones, and won't contain the original site's functionality, such as working forms. Treat it as a record of your words and images, not a site you can restore.
If the site is custom-coded, the host won't talk to you, or an archive is all you have, DIY stops making sense. A developer should map the old pages, redirects and forms before anything moves; taking over sites like this is part of our web design work.
Once the domain is yours, its DNS lets you prove ownership to Google for some accounts.
Sometimes the developer replies but refuses to hand over the logins, perhaps over an unpaid invoice. Here is how to get your website back from a web designer in that case:
Who owns the design and code is a separate question that depends on your contract; see our guide to whether you own your website.
Every account in your name, with the developer added as a user. Put this list in the contract:
Keep one access sheet somewhere safe and share it with a second person at your business.
Today, look up your domain in ICANN Lookup and send one polite written request. This week, get the domain into your account, then the hosting, then the website admin and a full backup. After that, reclaim your Google accounts and keep every new account in your name.
Once you're back in, send us your site and we'll record a free 2 minute video audit showing the 3 fixes we'd make first.
Often, yes. The registrant listed on the domain holds the rights to it, and ICANN suggests checking with your registrar and showing proof that you paid the developer. The fastest route is still the developer moving it to your account. If they refuse, use the registrar's process or legal action.
Not right away. The site keeps running while the hosting and domain stay paid. The risk is renewal time: if the developer's card or account lapses, the site or domain can go offline, and renewal reminders go to the registrant email, which may be theirs. Check the expiry date in ICANN Lookup today.
Only if they can confirm you are the account holder, meaning whoever opened and paid for it. Squarespace, for example, asks for a bank statement showing its charge. If you paid, ask support what proof they accept. If the developer paid, you need their cooperation or a rebuild on a new host.
If the developer cooperates, the domain move can be close to instant at some registrars, such as Namecheap with automatic acceptance turned on. If they vanished, plan on about a week to work through the registrar, host and Google, longer if support asks for documents. A dispute takes much longer.
Only if recovery is blocked or the old site wasn't bringing in work. Get the domain back first either way, because your email, your Google verification and every listing that points to you depend on it. A brand new domain is the last resort.
The 3 fixes we'd make first on your site, within 1 business day.