// AI SUMMARY

Quick answer: you are not really fighting over a website. You are fighting over five or six separate accounts, and they have an order. The domain record decides almost everything, so start there. Hosting, CMS admin, DNS and the files come after. Sometimes the fastest way out is to take the domain and rebuild rather than win the argument.

Why do people search this with “reddit” in it?

Because a normal search returns agencies selling the same monthly arrangement that caused the problem. Adding “reddit” is how you ask people with no invoice attached.

One note on sourcing: this page does not paraphrase other people’s threads back at you. It gives you the order of operations plus the domain rules that actually apply, which is the part most guides skip.

What are you actually trying to get back?

“My website” is usually six things, and people often fight over the wrong one first:

  • The domain registration record. Who is listed as the registered name holder, not who “set it up”.
  • The auth code, also called the EPP or transfer code. Without it the domain does not move.
  • The hosting account, which is not the same thing as the site files.
  • CMS admin, not a user account with the admin buttons hidden.
  • DNS control, which is often the real leverage point.
  • Backups and the actual files, including images, copy and anything custom.

Rank them by leverage. Whoever controls the domain and DNS can point your web address and your email anywhere, including at nothing.

Start with the domain

The domain is the whole argument, because it is the one thing that cannot be recreated. Everything else can be rebuilt.

Find out which registrar the name is actually registered at. A public WHOIS or RDAP lookup will usually tell you the registrar even when the contact details themselves are redacted, which they now are for most domains by default. The registrant contact email is the field that matters, and if it is not an email you control, that is the first thing to fix.

Then ask the registrar, not your designer, for the transfer code. This is the part people get wrong: they spend weeks emailing the web company when the registrar is the party with the obligation. ICANN’s Transfer Policy requires the registrar of record to provide the authorization code to the registered name holder on request, within five calendar days. Registrars take identity verification seriously here, so expect to prove who you are with business records rather than a single email.

Two things to expect along the way. Changing the registrant contact can trigger a 60-day lock that blocks a transfer to another registrar, so if you are going to move the domain, plan the order of those two steps rather than doing the easy one first. And if the registrar simply will not act, ICANN runs a contractual compliance complaint process for exactly this, including transfer failures. It is slow, and it is free, and it exists.

The pattern we see most often is not malice, it is inertia: a domain registered years ago inside a former developer’s account, nobody thinking about it until the day it matters, then a scramble because the renewal notice goes to an inbox nobody reads. Going around the middle party, straight to the registrar with proof of who you are, is what breaks the stalemate.

Hosting, CMS admin and DNS

Hosting is two things: the account, and the files inside it. A zip of your files is not the account, and the account is not much use without the files. Ask for both, in writing, as separate items.

CMS admin has the same trap. An “editor” role, or a custom “client” role, looks like access and then quietly refuses to install, export or add users. Test one thing: can your login create another administrator? If not, you have a user account, not admin.

Withheld hosting access is a lock-in tactic more often than an oversight. The tell is when every small change has to go back through the agency and comes back with a line on an invoice. If you have never been given hosting or file access, that was a decision someone made, not an accident. The reassuring part is that plenty of firms hand it over the moment they are asked directly and in writing, because the awkwardness of refusing outweighs the retainer.

DNS is last on the list and first in leverage. Whoever holds it can move your website and your email in minutes, so get DNS onto an account you control early.

What to do if they say no

  1. One written request with a deadline. List each item: registrant correction or transfer, auth code, hosting login, an admin user, DNS access, files and backups. Give a date, stay factual, keep the email.
  2. Go direct to the registrar and the host. They are the parties who can act, and going around a stalling middle party is what usually works.
  3. File an ICANN compliance complaint if the registrar will not release the auth code or correct the record.
  4. Price the rebuild as a real option rather than a defeat.

When a rebuild beats a fight

If they hold the files but you hold the domain, a new site can be live long before a dispute resolves. Copy and photos you supplied are usually sitting on your own devices, and the Wayback Machine often holds enough of the old pages to rebuild the structure. A small site done properly can cost less than a few weeks of argument, and you finish owning everything. If it is a WordPress build stacked with plugins you never chose, our WordPress versus custom comparison covers what is worth carrying across.

Some of this is not a technical problem. Who owns the design files, what your contract says about termination and ownership, and whether unpaid invoices can be used as leverage are legal questions whose answers depend on your paperwork and your state. We build websites, we are not a law firm, and we will not guess on your behalf. For smaller sums, small claims court is often proportionate and does not need an attorney. For anything larger, or where the contract language is genuinely ambiguous, get advice before you send anything you cannot take back.

How to stop it happening again

The arrangement makes this possible, not the individual. Two rules cover most of it: the domain is registered to your business with an email you control as the registrant contact, and you hold logins to hosting, DNS and the CMS from day one. Ask any supplier both questions before you pay a deposit.

For transparency: Web Blend builds hand-coded sites on Astro, hosted on Cloudflare, with no proprietary builder and no lock-in term. The client holds the domain, the site is theirs, and if they move on they take it with them, as set out on our websites service page. We are not neutral, we sell the opposite arrangement. For more of what the forums say about dealing with agencies, see our contractor marketing roundup.