If your web developer has disappeared, do two things today: look up your domain’s public record to see which registrar holds it and when it expires, and save a copy of your site’s public pages. The rest can be worked through step by step; an expired domain or a site that goes offline before you copy it is much harder to fix.
Step 1: Work out what you actually control
A website is several separate accounts, often held by different people. Before you contact anyone, list each one and note whether you have the login, so you know exactly what to ask for.
- Domain. Your web address, rented yearly from a company called a registrar (GoDaddy, Namecheap, Cloudflare and so on).
- Hosting.The server where the site’s files live and run.
- CMS admin. The content management system, the dashboard where pages are edited, such as WordPress.
- Code and files. The site itself, plus any database behind it.
- DNS. The settings that point your domain at the hosting and your email at your mail provider.
- Email. Your business mailboxes, which often run on the same domain.
Search your inbox for invoices and renewal notices from any of these companies. A receipt in your name, paid with your card, is useful evidence later.
Step 2: Check who the domain is registered to
Use ICANN’s free registration data lookup. It shows which registrar holds your domain, its creation and expiry dates, its status and its nameservers. The owner’s name and email are often hidden for privacy, but the registrar is always the next door to knock on.
ICANN’s own transfer FAQ points registrants to lookup.icann.org to find out who their registrar is. ICANN says its tool can “query, parse, and display registration data in a human-friendly format”, and that results containing personal data “may be redacted for privacy.” Porkbun’s guidelists what a typical record includes: the current registrar, the registration and expiration dates, and the current nameservers. A status of “transferProhibited” means the domain is locked against transfer, which is normal and can be switched off by whoever controls the account.
If the owner details are hidden, ICANN’s Registration Data Policysays a registrar that redacts them must publish “an email address or a link to a web form” for contacting the registrant. Write down the expiry date. If it is close, that is your deadline.
Step 3: Recover the domain account through the registrar
If the domain is in your name, the registrar can usually get you back into the account even without the old developer. Start with the normal password reset. If the account email belonged to the developer, use the registrar’s account recovery process, which normally asks for photo ID.
GoDaddy is a typical example. Its account recovery pagesays recovery is available if you lost access to the email on the account or if “You are listed as the domain registrant of a domain in the account.” It asks for a colour copy of a government-issued photo ID, and business documents if a company is listed on the account. Other registrars publish their own versions; search their help centre for “account recovery”.
If the lookup suggests the domain is registered to the developer, not you, recovery is a different process. Our guide on getting your website and domain back from a developer covers that case in detail.
Step 4: Get into the hosting account
Find the hosting company from the nameservers in your lookup, which often belong to the host, or from an invoice or card statement. If the account is in your name, the host can verify you and reset access. If it is in the developer’s name, expect to prove your claim.
Each host has its own process. Bluehost’s ownership request page, for example, lets you request ownership when the current primary contact “cannot or will not provide access”. It asks for a colour, government-issued photo ID plus a recent proof document, and if you are not in contact with the current owner it asks for a court order or legal documentation. Ask your own host what it needs.
Step 5: Get a copy of the site
Once you are in, take a full backup before you change anything. A site built on a CMS has two parts, the files and the database, and you need both. With no access at all, you can still save the public pages, which keeps your text and images safe.
WordPress’s backup documentationsays: “There are two parts to backing up your WordPress site: Database and Files.” It adds that most hosts provide software to back up your site. The WordPress export tool produces an XML file with your posts, pages, comments, custom fields, categories, tags and users. Images, the theme and plugins are not on that list, so the export is a useful extra, not a full backup.
With no logins at all, use the Internet Archive’s Save Page Now. Its help pagesays it saves the page you enter “including the images and CSS”, but that “this method only saves a single page, not the whole site.” Save each important page one at a time, and also save them in your browser and copy your text into a document.
Step 6: Secure what you recovered
As soon as you are back in an account, change its password, turn on two-factor login, point the account email to an address you control, and remove any user you do not recognise or no longer need. Do this for the registrar, the host, the CMS and email, in that order.
CISA, the US cybersecurity agency, says in its guidance for small businessesthat “Any form of MFA is better than no MFA” and to “Enable MFA for all system administrator accounts.” MFA (multifactor authentication) means a second check, such as a code from an app, on top of the password. Its password adviceis at least 16 characters, “a different strong password for each account”, and a password manager to keep them. In WordPress, check Users, then All Users, for old admin accounts.
Step 7: Decide whether to keep, move or rebuild
Only decide once you know what you own. If the site works and you have full access, keep it and put it on proper maintenance. If the hosting is in someone else’s name, move it. Rebuild only when the site is broken, outdated or impossible to recover.
- Keep when you have every login and a backup, and the site still does its job.
- Move when you have the files and the domain but the hosting belongs to the old developer.
- Rebuild when you have only the public pages, or the site is too old to update safely. Our website redesign page explains what a rebuild involves, and the website cost guide shows what each route costs.
Who usually holds each part, and how to get it back
| Asset | Who usually holds it | How to prove it is yours | If you cannot reach it |
|---|---|---|---|
| Domain | A registrar account, opened by you or the developer | Being the listed registrant, plus photo ID and invoices | Registrar account recovery; see our domain guide if you are not the registrant |
| Hosting | The developer’s account or yours | Account holder name, payment records, ID | Host’s ownership or recovery process; save public pages meanwhile |
| CMS admin | A user account inside the site | Access to the hosting or the admin email | Reset through the host’s database or file tools |
| Code and files | The server, and sometimes the developer’s computer | Your contract or invoices for the build | Host backup, or rebuild from the saved public pages |
| DNS | The registrar or a separate DNS provider | Control of the domain account | Recover the domain first; DNS follows it |
| A mail provider linked through DNS | The admin login for the mail service | Provider’s admin recovery; keep MX records unchanged meanwhile |
What to ask the developer for, in writing
Send one short, polite email so there is a dated record. Ask for specific things, and offer to settle any genuine unpaid invoice.
- The registrar name and account login, or a move of the domain into your own account.
- The hosting company and account login, or a full backup of files and database.
- An admin login for the CMS in your name.
- Any other services the site uses: DNS, email, forms, payments, analytics.
- A list of anything still billed to them that renews soon.
What not to do while you sort this out
Two mistakes cost the most. Do not let the domain expire while you wait for a reply, and do not pay for a new website before you know what you own. A rebuild does not help if the address it needs is still in someone else’s account.
On expiry, ICANN’s Expired Registration Recovery Policy requires reminders about a month and about a week before the date. After expiry the registrar must interrupt the domain’s normal DNS, so the site stops loading, and if the name is deleted most generic domains get a 30-day redemption period in which the registrant can still restore it. ICANN warns that a name not restored in time “may be made available for registration on a first-come-first-served basis.” Those reminders go to the email on the account, which may be the developer’s. Also avoid changing DNS records you do not understand: Google warns that “Your email might not work correctly if you keep old or incorrect MX records.”
Where Kodetra fits
We are a small software studio, registered in India, that works remotely with clients worldwide. Our hosting and maintenance service takes over hosting for sites other people built and lists this exact situation among the cases it is for. The steps it describes are moving the site onto managed hosting, then switching on monitoring, automated backups and security updates.
Care plans start at $89/mo and Growth at $229/mo, month to month. If the site needs replacing instead, see websites and landing pages. For ongoing costs, the website maintenance cost guide breaks down each part.
Frequently asked questions
Who owns my website if the developer built it?
The domain belongs to whoever is the registrant of record, and the hosting to whoever holds the account. Rights to the design and code depend on your contract. Check the lookup and your invoices first.
How long should I wait for a developer who is not responding?
Do not wait to start the safe steps. Look up the domain, save the public pages and check renewal dates today. Send a written request and give a clear, reasonable deadline for a reply.
Can I get back into WordPress without the admin password?
Yes, if you have hosting access. WordPress documents resets through phpMyAdmin, FTP and WP-CLI, all of which need access to the server or database. Without hosting access, start with the host.
How do I find out who hosts my website?
Start with the domain lookup: Namecheap notes that the record shows the nameservers the domain uses, which often belong to the host. Old invoices and card statements are the other quick check.
What if the domain is registered in the developer’s name?
Ask them in writing to move it to your account. If they will not, the options are narrower. See how to get your website and domain back.
Do I need to rebuild my website from scratch?
Usually not. If you recover the hosting or a backup, the site can be moved and kept. Rebuild only when nothing usable can be recovered or the site no longer does its job.
Next step
Write down your domain, its registrar and expiry date, and which logins you have. Send that through our contact page and we will tell you what can be recovered, what it will cost to host and look after, or that you can handle it yourself.
Sources checked: 21 November 2026.
Written by the Kodetra team with AI assistance and checked against the sources linked above.