If the domain or hosting account is in someone else’s name, then yes — technically they can, and buyers report it happening during disputes. The exposure isn’t legal permission; it’s simply who holds the login. Which is also why the fix is administrative rather than adversarial.
Complaint records include this plainly. One buyer wrote that after giving critical feedback, the vendor blocked their website. Another reported the site being stopped even though the renewal had been paid.
The moment it happens
Can a developer take your live website down over a payment dispute? You find out when a customer mentions the site isn’t loading, or your business email stops arriving — often on a weekend.
Then comes the calculation nobody wants to do: how much is a week of being offline worth, compared with the amount being demanded.
First, work out what’s actually wrong
Being offline has several possible causes, and only some involve a person.
| Symptom | Likely cause | Quick check |
|---|---|---|
| Site and email both dead | Domain expired or was moved | WHOIS lookup: check expiry and registrant |
| Site down, email works | Hosting expired or suspended | Ask the host; check hosting invoice |
| “Suspended” page | Hosting account suspended for non-payment | Whose account is it? |
| Site loads but shows something else | DNS pointed elsewhere | WHOIS + DNS records |
| Blank or error page | Technical fault, not necessarily deliberate | Ask before accusing |
Do the WHOIS check before sending anything. An expired domain and a deliberate shutdown look identical from your side and need very different responses.
The first 48 hours
- Send one calm, factual message. “The site is offline as of [date/time]. Please restore it. Separately, let’s resolve the payment question.” Keep the two issues apart — mixing them turns a technical request into a negotiation.
- Ask for the specifics you’ll need regardless: registrar name, hosting provider name, domain authorisation code, hosting login.
- Contact the hosting provider or registrar directly. If the account is in your name — check, some are — you can restore access without the developer at all.
- If the outage is costing you customers, consider paying first and moving afterwards. Winning the argument this week is rarely worth a week of downtime. Pay, restore, then transfer everything into your own accounts and end the exposure permanently.
- Keep a record of the outage, the messages and any demand. If this becomes a consumer complaint, the downtime is part of your case.
Getting control back for good
The permanent fix is boring: the domain in your registrar account, hosting in your account, a backup you hold.
Request it as routine admin — “please share the EPP/authorisation code and unlock the domain for transfer; also add me as owner on hosting” — not as an accusation. If the vendor refuses outright and the domain is legitimately yours by name, trademark or business registration, registrars have ownership-claim processes, and evidence that you paid and the name is your business carries weight.
If nothing works and the name is not recoverable in reasonable time, there is a harder decision: register a clean domain and rebuild. It costs traffic and reprinting, but it ends a dependency that will otherwise recur every renewal.
Reducing the risk before it happens again
- Domain registered in your name, your email, your registrar account.
- Hosting in your name; add the developer as a user rather than the owner.
- A backup you can access — a downloaded copy is enough for most small sites.
- Expiry dates in your own calendar, with a month’s warning.
- One line in any future quote: domain and hosting registered in the client’s account.
What to do this week
- Run a WHOIS check now, even if your site is working. Note registrant and expiry.
- Confirm whether the hosting account is in your name or the vendor’s.
- Ask for the domain authorisation code and hosting owner access as a routine request.
- Download a copy of the site if you can, or ask for the files.
- Diarise both expiry dates yourself.
If you want it done the certain way
If your site is currently offline or the accounts sit elsewhere, send us the domain and whatever access you have — we’ll tell you honestly whether it’s recoverable, worth paying to restore, or better rebuilt on a clean name. On our builds the domain and logins are yours from day one, so an unpaid invoice can only ever be a billing conversation, not an outage. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Whose name is your domain registered in?
- Website rescue: recovering your domain, hosting and site
- Year-two renewal shock
- The website handover checklist
FAQ
Is it legal for a web developer to take my website offline?
The question is usually control rather than legality: whoever holds the domain and hosting accounts can technically switch it off. Buyers have reported it during disputes. Holding those accounts yourself removes the possibility.
My site went down after I paid the renewal. What now?
Check the WHOIS expiry date and the hosting status first — a paid invoice doesn’t always mean the renewal was actually processed. If both look current, ask the provider directly rather than only the developer.
Should I pay a disputed amount to get my site back?
If downtime is costing you more than the amount, paying and then moving everything into your own accounts is usually the pragmatic sequence. Resolve the exposure permanently rather than winning the argument.
