Web Developer Won't Give You Website Access? What to Do
Written by Kamran, Founder, 3xRevenue. Published · 10 min read.
If your web developer won't give you access, secure the domain first. If the domain is in your name, your registrar must give you the transfer code within 5 calendar days. The design, code and other logins come next, and your contract decides most of those.
It is Monday morning. Your site shows an old price, and you need a new page up by Friday. You email the person who built it. No reply. You call. Voicemail. Then you find out the domain, the hosting and the Google listing all sit in their accounts, not yours.
It is fixable, and you can do most of it yourself. If you would rather hand it off, our website rescue and migration service takes on recovery and moves. Either way, the order you work in matters more than how angry the emails get.
Who owns each part of your website?
Your website is not one thing. It is 5 or 6 separate assets, and each one has its own owner and its own rules. Sort them before you send a single angry email.
| Part of your site | What decides who controls it | Who you ask | Typical wait |
|---|---|---|---|
| Domain name | The registrant name in the registrar's records | The registrar | 5 calendar days for the transfer code |
| Email on your domain | Whoever controls the domain's DNS (MX records) | The registrar or DNS host | Follows the domain |
| Hosting account | The name on the account and the card that pays | The hosting company's support | Varies by host |
| Design and code | Your contract, and any signed copyright transfer | The developer | Depends on the contract |
| Text and photos you supplied | You created or bought them | Nobody; copy them from the live site | Same day |
| Google Business Profile | The owner listed inside Google | Google's ownership request | 3 days for the owner to reply |
Source: ICANN Transfer Policy and Name Holder FAQ; Google Business Profile Help; US Copyright Office Circular 30. Hosting waits are our estimate.
The table shows the real priority. Lose the code and you can rebuild. Lose the domain and you lose your address, your email and years of links.
Find out whose name is on your domain
The registrant is the legal holder of the domain. You can look it up yourself before you contact anyone.
Run your domain through the ICANN Lookup tool. It shows the registrar, the dates and the status codes. Many records hide the registrant name for privacy, so you may only see the registrar. That still tells you where to call.
Then search your own inbox and card statements. Look for the registrar's name, "domain renewal" or "hosting invoice". If the receipts come to you, you have strong proof even if the developer set up the account.
Check one more thing. Our free tool above shows which platform and host your site runs on. WordPress on shared hosting means calling a host. A Wix or Squarespace site means contacting that platform.
Six moves that get your domain and logins back
Work through these in order. Each one builds proof for the next.
1. Gather your paper trail
Collect the contract, the invoices and proof of every payment. Note any balance you still owe.
Example: a signed quote, 3 paid invoices and a bank line that says "Domain renewal, $22".
Quick check: can you show what you paid for, and when?
2. Ask once, in writing, for a specific list
Send one short email. List each item and give a reply date 7 days out.
Example: "Please send by May 14: the domain transfer code, the hosting login and the site admin login. Please also send a full backup and admin access to Google Analytics and Search Console."
Quick check: is every request a thing they can hand over, not a feeling?
3. Go to the registrar if the domain is in your name
If you are the registrant, contact the registrar directly. Ask them to verify you, unlock the domain and send the transfer code. The ICANN Name Holder FAQ sets a deadline of 5 calendar days for that code.
Example: you call the registrar and confirm your identity. The code arrives by email that afternoon.
Quick check: does the registrar's record list your name or your company?
4. Protect your email before anything changes
Your business email runs through the domain's DNS records. Before you move anything, write down the current settings. Our DNS and email record checker shows the MX, SPF and DMARC records in one place.
Example: your MX records point to Google Workspace. You copy them so the new DNS host uses the same values.
Quick check: does test mail still arrive after each change?
5. Claim the Google accounts
Google Business Profile has its own ownership request. The current owner gets 3 days to respond. If they don't, you may get the option to claim it. Google says that option is not always offered.
For Search Console, verify your domain again with a DNS record once you control the domain. Analytics history stays in whichever account created it, so ask for admin access in your written request.
Quick check: can you log in to each Google tool with your own email?
6. Escalate only when the deadline passes
If nothing arrives by your date, move up one step at a time. A lawyer's letter comes first. If the registrar will not follow the policy, ICANN accepts formal transfer complaints.
Quick check: did you keep copies of every message and reply?
Example: a landscaping owner whose developer went silent
This is an example built from common cases, not a real client.
Dana runs a 4-person landscaping company. A local developer built her site 3 years ago and has not answered for 6 weeks. The renewal notice for the domain went to his email, not hers.
Before: Dana has no logins. Her site still works, but she can't change a price. Her email works only because nobody has touched the DNS.
What she did: On day 1 she ran an ICANN lookup and found the registrar. Her company name was the registrant, because she had paid with her own card. She sent the developer one written request with a 7-day deadline. No reply. On day 8 she called the registrar, passed their identity check and got the transfer code. She copied her MX records before moving anything.
After: By day 12, the domain sat in an account in her name. She asked Google for the Business Profile and claimed it after the 3-day window. She chose to rebuild the 6-page site rather than chase the old files.
The order is what saved her. Domain first, email second, the site last.
Should you fight for the old site or rebuild it?
Rebuild if the old site is small and the developer is silent. Fight only for things you can't recreate, like a custom booking system or years of store data.
Remember that you already own your text and photos. Copy them from the live site today, while it still loads. The Internet Archive's Wayback Machine may also hold older copies of your pages.
| Factor | Fight for the old files | Rebuild on accounts you own |
|---|---|---|
| Time to a working site | Unknown; depends on the developer or a court | 7 days on our website build plan |
| Cost | Lawyer fees, which vary widely | From $3,000 for a business website with us |
| What you end up with | The same old site, maybe without updates | A new site, with every login in your name |
| Risk | The files may arrive broken or incomplete | You must set up redirects from old page addresses |
| Best when | The site holds custom features or store data | It is a 5 to 10 page brochure site |
Source: our published website pricing; lawyer cost and time are not something we can estimate for you.
If you rebuild, keep the same page addresses where you can. Where a page moves, add a 301 redirect from the old address. That keeps old links and bookmarks working.
What if the domain is in the developer's name?
Then the registrar sees the developer as the legal holder. They will not hand the domain to you on request alone.
Your options, in order:
- Ask for a registrant change. This is cleaner than a transfer. Under current ICANN rules it can trigger a 60-day lock on moving registrars, unless an opt-out was chosen.
- Show the registrar your proof. Some registrars will help when you can prove you paid. They don't have to.
- Send a lawyer's demand letter. It puts your claim on record and sets a clear deadline.
- Take a contract claim to court. Small claims court may fit if the amounts are low. Ask a local lawyer first.
The code and design follow the contract. Under US law, the person who creates a work is usually its author. The US Copyright Office's Circular 30 sets a narrow rule. A commissioned work is "made for hire" only if it fits 1 of 9 categories and both sides signed in writing. That is why a clear written assignment of rights in your contract matters so much. This is general information, not legal advice.
One change is coming. ICANN's board adopted a revised Transfer Policy in June 2026. Registrar blogs say it drops the 60-day lock after a registrant change. It will roll out over many months. Until your registrar adopts it, the current rules apply.
Set up your next site so this never happens again
The fix is simple. Every account sits in your name, and the builder gets their own login on top.
- ☐ The domain is registered to your company, with your email as the contact.
- ☐ Hosting is billed to your card and opened under your email.
- ☐ Your builder has a separate user login that you can remove.
- ☐ The contract assigns copyright in the design and code to you on final payment.
- ☐ You get a full backup on launch day and a copy of every password.
- ☐ Google Business Profile, Analytics and Search Console list you as owner.
- ☐ Domain auto-renew is on, with a backup card on file.
Put the ownership terms in writing before work starts. Our free web design proposal template has a section for ownership and handover you can edit.
Common mistakes
- Changing DNS before saving the old records. This is how working email breaks for days.
- Threatening before asking. One clear written request solves many cases, and it is your best proof later.
- Letting the domain expire to "get it back". An expired domain can be lost to someone else entirely.
- Paying a new builder who repeats the setup. Insist on accounts in your name from day 1.
FAQ
Can a web developer legally keep my domain?
If the developer is the listed registrant, the registrar treats them as the holder until that changes. Whether they must hand it to you depends on your agreement and what you paid for. A lawyer's letter is usually the next step.
How long does a domain transfer take?
Your registrar must give you the transfer code within 5 calendar days of your request. How long the move takes after that depends on the new registrar. Locks after a recent registration, transfer or registrant change can delay it.
Do I own the website if I paid for it?
You own your domain if it is in your name, and you own the text and photos you supplied. The design and code depend on your contract. Without a signed assignment, the creator may still hold the copyright.
Will I lose my business email if I move the domain?
Not if you copy your DNS records first. Your email runs through MX records, so the new DNS host needs the same values. Test that mail arrives after each change.
Should I keep paying the developer while this is sorted?
Pay what you clearly owe under the contract, and keep proof. An unpaid balance weakens your position with the developer. ICANN rules also bar a registrar from using transfers to collect a payment it says you owe.
Own every login from day one
Getting a site back is slow and stressful, even when the rules are on your side. The cheaper path is a build where the domain, hosting and code sit in your name before launch day. Ready to start clean? See how our business website in 7 days plan hands you every login.