Lost access

Web Developer Disappeared? Secure the Domain, Hosting and Code Before the Next Renewal Date Finds You

The last email was friendly. The next three went unanswered, the voicemail box is full, and the invoice for your website says paid in full. The developer is gone. The site is still up, which feels like good news and is mostly a countdown nobody can see.

November 20, 2026 · 11 min read

acmetileandstone.com · account inventory
Who holds each key, after the developer stopped answering
The domain renews in 19 days, in the developer's name
  • FailDomain registrantdeveloper
  • FailDomain renewal notices go todeveloper only
  • PassHosting billed to the company card
  • WarnSearch Console verified owneradd ours
  • FailCode repository accessnone
  • PassAnalytics admin
  • PassFull backup taken today
Illustrative: a sample account inventory for a fictional tile showroom whose developer went quiet

The short answer

When a web developer disappears, the site rarely breaks the same day, so the first hour is an inventory, not a fight. List every account the business runs on: domain registrar, DNS, hosting, code repository, Search Console, analytics, email and any app store. Note whose name each sits under, which email receives its notices and when it renews. Secure the domain first, because the registrant controls it.

On this page
  1. Nothing is broken yet, and that is the trap
  2. One hour, one spreadsheet, zero angry emails
  3. The key ring: every account, who should hold it, and the way back
  4. Everything hangs from the domain, so secure it first
  5. Ways owners accidentally hand a vanished developer the upper hand
  6. If the same person also built your app or your software
  7. What we take over, what it costs, and when you can skip us

Nothing is broken yet, and that is the trap

A missing developer is a strange emergency. The site loads. The forms work. Customers notice nothing. What changed is that the only person who knows where everything lives has stopped answering, and the accounts that keep your site alive are still sending their reminders to that person's inbox. The domain renews on a card that may have expired. The hosting bill goes to an address nobody reads. The first you hear of it may be a dark website on a Monday.

Sort the situation honestly before you act. A developer who is slow is a management problem. A developer who is ill or has closed the business is a handover problem, usually solvable with patience and paperwork. A developer who refuses to hand over what you paid for is a contract problem, and that one belongs with your attorney. This page is about the first hour in all three cases: what to gather, what to protect, and which mistakes weaken the position you already hold.

None of this is legal advice. Domain ownership, contracts and who owns the code a contractor wrote depend on your agreement and on your state's laws, which differ. Talk to your own attorney before you send anything that reads like a demand.

One hour, one spreadsheet, zero angry emails

  1. 1

    Minute 0: open a sheet with six columns

    Account, login address, the name it is registered under, the email that receives its notices, the renewal date, and who pays. Every row you fill in turns a vague fear into a specific task.

  2. 2

    Minutes 5 to 15: find your domain's registrar and expiry date

    ICANN points owners to a WHOIS search to find a domain's registrar, and a public lookup usually shows the expiry date too. If the date is weeks away, breathe. If it is days away or past, the domain jumps to the top of the list.

  3. 3

    Minutes 15 to 25: search your own inbox for receipts

    Search for the registrar, the host, renewal, invoice and receipt. Whoever pays an account often controls it. A receipt in the company's name is evidence you will want later.

  4. 4

    Minutes 25 to 40: try every login that is yours

    Use password resets only on accounts registered to an email address the business controls. In Search Console and analytics, open the users settings and check whether you are an owner or only a user.

  5. 5

    Minutes 40 to 50: list what you cannot reach

    The code repository, the hosting control panel, the DNS provider, any cloud account, any app store account. Note what each would cost you if it went dark tomorrow.

  6. 6

    Minutes 50 to 60: send one calm, written request

    List the accounts and files you need, ask for them to be transferred to the business by a specific date, and keep a copy. Polite and specific beats angry and vague, and it reads better later if a lawyer has to read it.

Chalkboard drawing of many keys hanging on a ring around a locked keyhole, with chalk arrows pointing away
Losing a developer is mostly a question of who holds which key, so the first job is a list.

The key ring: every account, who should hold it, and the way back

Most small business websites hang from the same eight or nine accounts. Here is each one, why it matters in a handover, and the official route to control as the provider documents it. Where we found no documented route, the table says so.

Accounts to recover after a developer leaves, and the documented route for each
AccountWhat it controlsWho should own itRoute back, as documented
Domain registrarThe name itself, and where it pointsThe business, as registrantTransfer rules under ICANN's Transfer Policy; see the next section
DNS providerWhere the site and email are foundThe businessOften the registrar or a service such as Cloudflare; same account question
HostingThe server and files the site runs onThe business, billed to its cardThe host's own ownership process; ask the host directly
Code repositoryThe source code and its historyThe business, with the developer as a memberA transfer by the current owner; no shortcut exists
Search ConsoleHow Google sees and reports the siteThe business, as verified ownerVerify with your own token, then remove old tokens
Cloud accountServers, databases, storageThe business, on a shared company addressAWS advises a root email managed by the business
Apple developer accountYour iOS app and its certificatesThe business, as Account HolderOnly the Account Holder can renew the membership
Google Play ConsoleYour Android appThe businessA US$25 one-time registration fee to open your own, as of November 2026

Search Console is the easiest win. Google's Search Console permissions page explains that a verified owner proved ownership using a token, and a new person verifies by starting the flow, posting their own token and clicking Verify. If you can edit the site's code or DNS, you can usually verify yourself without the developer. Then remove the old owner the way Google describes: by deleting their verification token. Google warns that if you leave the token in place, the removed owner can re-verify whenever they like.

Everything hangs from the domain, so secure it first

If you lose the hosting, you can rebuild the site. If you lose the domain, you lose the address on your trucks, your cards, your Google listing and every email your customers have saved. ICANN's Transfer Policy, updated in February 2024, says registrars must give the Registered Name Holder the unique AuthInfo code, and without self-service tools must do so within five calendar days of the holder's request, as of November 2026. The registrar may not refuse solely over a payment dispute.

The same policy lets a registrar deny a transfer within 60 days of a domain's creation, and requires a 60-day lock on moving registrars after a change of registrant, as of November 2026, unless the registrar offered an opt-out and the holder took it beforehand. So the order matters: get the registrant changed to the business, then decide whether to move registrars, knowing the lock may apply. If a registrar denies a transfer and you think the denial was improper, ICANN's registrant FAQ says you can file a Transfer Complaint.

Expiry is the other danger. ICANN's Expired Registration Recovery Policy requires notices about a month and about a week before expiration, sent to the registrant, who may be the developer. After expiry, the registrar must interrupt DNS for at least the last eight days the name can still be renewed. Our reasoning from that: when the domain's DNS goes, the website and email that depend on it stop resolving. A deleted name then enters a 30-day Redemption Grace Period, as of November 2026, and ICANN's renewal FAQ says restoring it may carry a redemption fee. The domain expired fix and the domain and DNS emergency page cover that situation.

Ways owners accidentally hand a vanished developer the upper hand

  • Removing the developer's access before you have your own owner-level login. You may lock out the only working key and still not have one of your own.
  • Letting a renewal lapse while you wait for a reply. Pay it yourself if you can reach the account; argue about the money later.
  • Hiring someone to rebuild the site from scratch in week one, before you know what you own. Half the time the code and content are recoverable.
  • Posting angry public reviews while you still need files from the developer. It feels fair. It rarely speeds a handover.
  • Leaving recovery emails and phone numbers on the developer's addresses after you regain control. Change them the same day.
  • Paying an unknown recovery service that offers to get your domain back for a fee. Use the registrar's own process and your attorney.
The developer leaving is the event. The renewal email going to their inbox is the emergency.

The fix that prevents the next one is dull and free. AWS, in its root user guidance, advises an email address managed by your business that forwards to a group, which reduces delays even if individuals are on vacation, out sick, or have left the business. The same logic applies to every account on your sheet: business-owned addresses, two-step verification, and a second person who knows where the list lives.

If the same person also built your app or your software

App store accounts raise the stakes, because renewal is tied to a role, not a payment. Apple's membership renewal page says renewal must be done by the Account Holder. If the membership expires, your apps are no longer available for download and you cannot submit updates or reach certificates, though apps already installed keep working. Apple's certificates overview adds that only the Account Holder or Admin role can create distribution certificates. If the developer is the Account Holder, a routine update can become impossible.

If that describes you, read expired Apple certificates and app removed from the App Store. For custom software that only the departed developer understood, legacy software rescue covers stabilizing it first and deciding later. When the problem is bigger than one project, and nobody in the business can judge technical work at all, a fractional CTO takes on that ownership, and our note for non-technical founders explains how that works.

What we take over, what it costs, and when you can skip us

We respond the same business day, during the hours on our contact page. We start with your spreadsheet, fill in the gaps we can find from the outside, take a full backup of everything we can reach, and work through each provider's official process to put accounts in the business's name. Then we document the lot so this never depends on one person again. If the site is also broken, we fix that first; our fixing broken websites service covers the repair.

If the site is WordPress and it is down, that repair is a fixed-price Fix it now job: site down or white screen $249, paid online, starting within one business day of payment, with a full refund if we can't fix it, via WordPress repair. A takeover of any other platform, custom code or an app is from $575, depending on complexity, with a written estimate before work starts. The emergency website repair page lists the access we ask for, and emergency pricing explains what moves a quote. Afterward, hosting and maintenance from $55 a month keeps the accounts and backups in one place.

Call us if

  • The domain expires within weeks and you cannot reach the account
  • The site is down and nobody has hosting access
  • You have the logins but no idea what you are looking at
  • An app or custom system depends on the missing developer

Save your money if

  • The developer is slow but still answering: set a date and wait
  • Every account is already in your name with your email
  • The site is on a builder you log into yourself
  • The real dispute is the contract, which is your attorney's job

DataCram is a web studio in San Antonio, Texas, building for the web since 1999, working with businesses across the US by phone, video and a shared project page. See our work, the rest of the emergency repair section, or call (210) 346-0848. If the site went dark while you were reading, go to website down: what to do first.

Questions owners ask in an emergency

List every account the site depends on, then send one written, specific request for each to be transferred to the business by a set date. Secure what you can reach yourself, starting with the domain and Search Console. If the developer refuses, involve your attorney, because ownership depends on your contract and state law, which differ.

Sometimes, but it is the hardest case, because the registrant controls transfers. ICANN advises against listing a designer or host as registrant and recommends legal advice when a third party holds that role. Keep proof the business paid for the domain and talk to your attorney before contacting the registrar.

Under ICANN's Transfer Policy, a registrar without self-service tools must give the registered name holder the AuthInfo code within five calendar days of the request, as of November 2026, and may not refuse solely over a payment dispute. That right belongs to the registrant, which is why the name on the registration matters so much.

Not immediately, in most cases. It goes down when something the developer was handling lapses: a domain renewal, a hosting bill, an expired card or a certificate. That is why the first hour is an inventory of renewal dates and who receives each notice.

Usually. Google lets a new person verify ownership with their own personal token, posted the way the chosen verification method requires. Once you are a verified owner, remove the old owner by deleting their verification token. Google warns that if the token stays, the removed owner can re-verify.

A WordPress site that is down is a fixed-price Fix it now repair at $249, with a full refund if we can't fix it. A takeover of any other platform, custom code or an app is from $575, depending on complexity, with a written estimate before work starts. We respond the same business day.

Keep reading

Free · No obligation

Get your accounts back in your name

Tell us what the developer built, what logins you still have and when the domain renews. We reply the same business day with what we would secure first and a written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote