Privacy & Social · September 21, 2026
What to Do When a Former Web Developer Controls Your Domain Name
A calm, practical plan for documenting domain control, requesting a proper handover, protecting website and email continuity, and escalating a genuine dispute.
Do not cancel hosting, change DNS records, or start a public fight. Identify the registrar and registered name holder, preserve the contract, invoices, messages, renewal details, and current DNS records, then request a documented handover to a company-controlled account. Use the registrar's recovery or transfer process when appropriate. If the developer disputes your right to the domain, get qualified legal advice because payment, branding, registration data, contracts, and local law can all matter.
The domain, hosting, email, DNS, analytics, and Search Console are separate assets. One vendor may control several, but moving one carelessly can interrupt the others. Keep the site, email, forms, and customer links working while authority is clarified.
ICANN describes a registrant, or registered name holder, as the person or entity that enters the registration agreement with the registrar. That record is important, but a business dispute may also involve contracts, agency relationships, trademarks, payments, and local law. An invoice by itself does not settle every ownership question.
Many cases are solved with a complete handover request rather than an accusation. A former developer may need the destination account, authorized contact, balance resolution, or safe cutover plan. Keep communication factual. Do not guess passwords, enter another person's account, or use a false complaint.
A practical step-by-step approach
01Preserve the current setup before changing it
Record the domain, website, email, registrar, reseller, host, nameservers, DNS, renewal date, certificate, analytics, Search Console, forms, and vendor contacts. Save screenshots and export settings where authorized. Keep renewals and essential services paid during the review. A rushed nameserver or account change can take the site and email offline.
02Identify the registrar and registered name holder
Use ICANN's Lookup tool to find the registrar and available public registration data. Review registrar receipts, renewal notices, account emails, and the registration agreement. Privacy services may hide contact data, so contact the registrar through its official website rather than a number or link in an unexpected message.
03Review the agreement and business evidence
Collect the proposal, contract, invoices, payment records, messages, brand records, and clauses about domains, credentials, termination, or transfer. Write a timeline showing who selected the name, who registered it, which account paid, and what the parties agreed. Keep legal conclusions separate from facts and ask counsel to interpret a dispute.
04Prepare a company-controlled destination
Create an account with a company email address, current recovery contact, unique password, and multifactor authentication. Use company billing and document at least two authorized administrators. Do not ask the developer to email passwords. Transfer the domain or account through the provider's supported process whenever possible.
05Send a precise handover request
Request the domain, registrar account or registrant change, authorization code when needed, DNS zone, nameservers, renewal details, website files, database, certificates, email setup, analytics, and Search Console access. State a deadline and technical contact without threats. Confirm what remains active until transfer and what access is removed afterward.
06Follow the registrar and ICANN process
A change of registrant and a transfer to a different registrar are different actions. ICANN says a transfer between registrars generally needs authorization from an eligible transfer contact and an Auth-Code. Certain locks or disputes can delay a transfer, and a change of registrant can trigger a transfer lock. Read the registrar's current instructions before deciding the order of operations.
07Escalate a refusal through the right channel
If the account holder cooperates but the registrar mishandles an eligible transfer, use the registrar's escalation route and ICANN complaint process when its requirements fit. If the developer claims the domain personally, the conflict may be contractual or legal rather than a registrar-service failure. Counsel can assess negotiation, demand letters, trademark procedures, court options, or other remedies without making unsupported claims.
08Complete and verify the handover
After access changes, confirm registrant details, renewal, payment, recovery, nameservers, DNS, website, email, forms, certificates, analytics, and search tools. Google advises removing former Search Console owners and unused verification tokens carefully because a valid token can restore access. Keep a signed inventory and add domain ownership to vendor offboarding.
Information to gather
A clear record makes it easier to choose the right channel, communicate accurately, and avoid unnecessary repetition. Start with:
- Domain, registrar, reseller, registered name holder, and renewal date
- Contract, proposal, invoices, payments, and project communications
- Nameservers, DNS zone, website backup, email, certificates, and forms
- Company-controlled account, billing, recovery contact, and multifactor authentication
- Written handover request, deadline, technical contact, and response log
- Registrant-change, Auth-Code, transfer-lock, and registrar instructions
- Analytics, Search Console, tag manager, advertising, and social access
- Final access inventory, vendor offboarding record, and next renewal review
What not to do
Pressure can lead to decisions that create a second reputation problem. Avoid:
- Changing nameservers or canceling hosting before website and email dependencies are mapped
- Guessing passwords, entering another person's account, or impersonating the registrant
- Assuming an invoice or trademark automatically forces a registrar transfer
- Publishing credentials, private registration data, or accusations about the developer
- Submitting false fraud, trademark, abuse, or transfer complaints
- Promising recovery, uninterrupted service, a legal result, or a transfer date
Frequently asked questions
Who owns a domain registered by a web developer?
The registrar recognizes the registered name holder under its registration agreement, but a dispute between the developer and business may also depend on contracts, authorization, payments, trademarks, agency rules, and local law. Do not assume one invoice or public lookup decides the legal issue. Preserve the records and ask qualified counsel about contested rights.
Will the registrar transfer the domain because it matches my business name?
Not automatically. Registrars follow their agreements, identity checks, authorization rules, transfer policies, dispute procedures, and applicable orders. A matching business or trademark name can be relevant evidence, but it does not replace the registrar's required process. Submit accurate documents and use legal advice when the current registrant objects.
Should I change DNS or cancel the old hosting immediately?
Usually not. DNS can direct the website, email, verification records, forms, and other services. First inventory and back up the current configuration, prepare the destination, and plan a controlled cutover with authorized technical help. Keep necessary services renewed until the website and email work from the company-controlled setup.
What if the domain name has expired?
Contact the current registrar immediately through its official support channel. ICANN explains that renewal and restoration options depend on the domain's status and timing, and an unrenewed name can eventually become available for someone else to register. Do not wait for a general ownership dispute to resolve before asking about the active recovery window.
Can a reputation company guarantee that the domain will be recovered?
No. A responsible provider can document the public setup, organize a handover inventory, coordinate continuity, improve company-controlled access, and work with technical and legal advisers. Outcomes depend on the registration agreement, registered name holder, contracts, evidence, registrar, registry, policies, domain status, laws, and other third parties.
Primary resources
Policies and features can change. Review the current source before submitting a request:
- ICANN: information for domain-name registrants
- ICANN: Lookup tool
- ICANN: change of registrant
- ICANN: Auth-Codes
- ICANN: domain-name transfers
- Google Search Console: manage owners and verification tokens