My Web Designer Disappeared: Getting Your Website Back

Three emails, two texts and a voicemail, and nothing back for six weeks. You do not know where the site is hosted, you are not sure whose name the domain is in, and the renewal for something arrives on a card you think might be theirs. The fear underneath all of it is that the whole thing will vanish one morning, the site, the email addresses, the years of it, and you will be starting over. Here is the fact to hold onto before anything else: a designer's silence changes nothing. The domain, the DNS, the hosting and the site are all exactly where they were the day the emails stopped. The site is almost certainly still running, and there is time to find out what you control before you replace anything.

Open the site right now on your phone, off the office Wi-Fi. If it loads, it is still being served by whatever host was always serving it, and the domain is still pointing there. That is the position for the overwhelming majority of people who type this search. What has actually failed is a relationship, and the operational problem is that you cannot tell whether the domain, the hosting, the site's admin login, the email, the analytics or the billing are yours to get into.

The first job is to preserve the current state and touch nothing. Screenshot every page, the contact form, the checkout or booking flow, and the footer. Save the dates and content of every unanswered message. Do not change DNS, cancel anything, delete a user or publish a replacement while you are doing this. Everything you save now is evidence for an account recovery, and everything you change now is a variable somebody will have to untangle later.

The domain is the one asset that can genuinely be lost if it lapses, so it comes first. ICANN's free Registration Data Lookup shows the registrar of record, the domain's status, the expiry date and the nameservers, drawn live from the registry. Since 28 January 2025, the lookup runs on RDAP rather than the old WHOIS, and ICANN's registration data policy lets personal contact fields be redacted, which means a blank owner name is the normal result and says nothing about who owns the domain. What the lookup does reliably tell you is which company to contact, how long you have, and which company's servers are answering DNS, and the last of those is often a different company from the registrar.

Then the paper trail. Search your email for renewal notices and invoices, and your card and bank statements for registrar and hosting names. A card descriptor is a lead to follow to the merchant, and it is worth knowing that paying the bill does not by itself make you the registered name holder. ICANN's registrant page describes the registrant as the party with the contract with the registrar, and the registrant is who a registrar will talk to. Write down what you find: registrar, expiry, nameservers, the email the notices went to, whose card paid.

Owners say "my website" and mean one thing. A technician hears five, held by up to five different parties, recoverable separately.

Sort your situation into that table before asking anyone for help. A designer who set the domain up in their own account but gave you the site's admin login is a very different case from one who holds everything, and the recovery effort goes where the gap actually is.

With the evidence saved and the five things mapped, the recovery runs in a fixed order, and none of the steps involves a redesign.

• Try ordinary account recovery first, at each provider, using an email address and phone number the business controls. A surprising number of "lost" accounts come back this way.
• Assemble the identity packet: business formation records, government ID, invoices, renewal notices, and the signed scope or contract. Each provider runs its own identity review and decides what it needs.
• If you are the registered name holder and cannot get into the account, work with the registrar on recovery. Once you are in, ICANN's transfer FAQ says a registrar without self-service tools must provide the transfer authorisation code and remove the transfer lock within five calendar days of your request.
• Get a working copy before you move anything. Export from the platform, request a host backup if the account allows it, and save the media, form settings, DNS records and any code separately. A WordPress export, per its own documentation, is an XML file of posts, pages, comments, menus and custom fields. It is content, not the database, the plugin settings, the payment configuration or the server setup.
• Choose the least disruptive move the evidence supports. If the domain can stay, prepare a copy on new hosting, test it, then point DNS at it. That is the whole move.
• Escalate in the right lane. The registrar's own process for access. ICANN's transfer complaint only for a breach of its Transfer Policy. A lawyer for contract, copyright or ownership. Nobody for "make my designer answer", because no lane exists for that.

The step people skip is the copy. A site that is running today can be copied today, and a copy in your hands changes every later conversation from a rescue into a migration.

Expiry and a hasty move are the two ways a manageable problem becomes a real loss, and both are avoidable if you know the clocks.

The first is expiry. ICANN's expired-registration policy requires registrars to send two reminders before expiry, about a month and a week out, to the registrant email on file, which in this situation may be the designer's inbox. After expiry, a registrar may offer an auto-renew grace period of 1 to 45 days, and a 30-day redemption period follows deletion. ICANN says DNS can be disrupted for up to eight days before deletion and throughout redemption, and when DNS stops, the site and every email address on the domain stop with it. The expiry date in the lookup is the only deadline that matters, and the fix is to get to the registrar before it.

The second is the instinct to start fresh on a new domain. Google's guidance distinguishes two events. A hosting move with no URL change is prepare, test, change DNS, monitor, then switch off the old host, with nothing visible to search. A move to a new domain is a migration: map every old URL to its new equivalent, set 301 redirects, verify both sites in Search Console, submit a Change of Address, keep the redirects for at least 180 days and the old domain for at least a year, and expect a medium-size site to take weeks or more to settle. Google says correctly implemented 301 redirects do not lose ranking on their own, and that incorrect redirects, blocked crawlers and stale sitemaps are what cause the losses people fear. Rebuilding on a new address before checking whether the old one is recoverable is choosing the harder event for no reason.

The evidence and access work is yours, and doing it well is what makes the technical help fast. Save the public pages and media. Run the lookup. Search your own records. List every account and the email attached to it. Try password recovery everywhere with a business email. Once you are into the site, create a second administrator account immediately. Export the content and test the export somewhere harmless.

Stop before any irreversible or security-sensitive change to the live system. That means nameservers, mail records, DNSSEC, registrant contact details, transfer locks, payment settings, user roles, and deleting old hosting. Each of those has something depending on it that you cannot see, and each needs a written record of the current setting and a tested replacement before it changes. One trap worth naming: ICANN notes that changing the registrant's contact details can trigger a 60-day transfer lock in some circumstances, so an eager edit to put your own name on the domain can freeze the very move you were planning.

Get qualified technical or legal help when the registrant is disputed, the expiry is close, business email is down, the site holds customer or payment data, a transfer is locked or refused, somebody is demanding payment to release access, or the contract and copyright position is contested.

The costs with published figures are few and specific. The ICANN lookup is free. A WIPO UDRP complaint for one to five domains with a single panelist carries a $1,500 filing fee, and the UDRP is a trademark process: the complainant has to show the domain is confusingly similar to a mark they hold, that the registrant has no legitimate interest, and that it was registered and used in bad faith. A silent developer who registered your domain in good faith while building your site does not fit that shape, which is why the dispute route is usually the wrong lane. Tarrant County's Justice Court 6 publishes a $54 small-claims filing fee and a $20,000 cap, which is court information and not advice that a given dispute belongs there. Any redemption fee for a lapsed domain is whatever the actual registrar's current schedule says, and ICANN requires registrars to make those fees available.

Recovery labour, migration and a rebuild are priced job by job, because the platform, the number of pages and integrations, whether a backup exists and whether you are the registered name holder all move the figure. What the contract should have said is worth knowing for next time. The US Copyright Office says the person who pays a web designer can be a different party from the author and copyright owner, and its work-for-hire guidance describes narrow conditions that need a written agreement. The useful question was never "do I own the site". It was which assets are assigned or licensed, which accounts are in the business's name, which email receives renewal notices, and what is handed over at launch and at termination. This is general information, not legal advice, and a contested contract needs a lawyer.

No Arlington programme recovers websites, and no Texas statute transfers a domain because a developer stopped answering. The registrar's policies and ICANN's rules are the operational law for a generic domain, wherever the business sits.

What the city does offer is general business guidance. Its small-business resources page points to the Arlington Economic Development Corporation, the Greater Arlington Chamber, the Arlington Black Chamber and the US Pan Asian American Chamber, and names the Tarrant County Small Business Development Center and SCORE Fort Worth among its partners. Those are places to ask about contracts and vendors, not custodians of any account.

One Texas document is useful in a narrow way. An assumed-name certificate under Business and Commerce Code Chapter 71, per the Secretary of State, tells the public that an entity trades under a name other than its legal one, and it can support an identity review at a registrar. It does not create a right to the name or prove ownership of a domain.

The prevention is a control you can test. At least two people authorised by the business should be able to get into the registrar, the hosting, the site's admin, the email administration, the analytics, any code repository, the backup storage and every paid third-party service. One page records the legal registrant, the renewal date, the billing method, the recovery email, the DNS provider, the nameservers, and the date and location of the last backup that was actually restored somewhere. The page lives outside any contractor's inbox.

You know it works when you can sign in to each account yourself, recover access with a business email, see and renew the domain, request the transfer code, view the DNS records, create a second administrator, and restore a copy without touching the live site. Check it before every renewal notice, after any staff or vendor change, and after any big platform change. ICANN's two pre-expiry notices, a month and a week out, are a ready-made calendar for the check.

My web developer ghosted me. Is my site going to disappear?

Not because of the silence. The site keeps running on whatever host was always serving it until a domain or hosting renewal lapses. Find the expiry date in the ICANN lookup, and that is your actual deadline.

How do I find out who hosts my website?

The nameservers in the ICANN lookup point to whichever company answers DNS for the domain, which is often the host. Statements and invoices fill in the rest. The registrar in the same lookup is where the domain lives, and it can be a different company.

I cannot access my website. How do I get back in?

Try password recovery on the admin login with a business email first. If that fails, the host's account-recovery process, with your identity packet, is the route. A running site can also be copied before you have admin access, which is worth doing early.

Can I just move to a new domain and start over?

You can, and it is the harder of the two options. Google treats it as a migration with page-by-page redirects, Search Console verification and a year of holding the old name, and a medium site takes weeks or more to settle. Keeping the domain and moving the hosting has none of that.

Does paying for the website mean I own it?

Paying is evidence for an account recovery, and the registrant, not the payer, has the relationship with the registrar. The Copyright Office says the payer and the copyright owner can be different parties, so what you own depends on what the contract assigned.

Can ICANN make my designer hand over the domain?

No. ICANN accepts complaints about a registrar breaching its Transfer Policy, and it does not settle ownership disputes between private parties. The registrar's recovery process, a lawyer for the contract, and the UDRP only where a trademark is involved, are the three lanes.

The silence felt like the site disappearing, and it was a relationship disappearing while the site stayed exactly where it was. The lookup, the statements and a few password-recovery attempts usually answer most of what you were afraid of within an afternoon.

The two things to protect are the domain's expiry date and the domain itself. Get to the registrar before the first, and keep the second, because moving hosts under a domain you hold is a quiet afternoon and moving to a new domain is a year of redirects.

If the lookup has given you four facts and no idea what to do with them, Arlington Website Designer helps owners in Arlington, TX turn that into a recovery plan with the accounts in the right names at the end of it. Send the domain and what the lookup showed through the contact page, and you will hear back which of the five things you already control, which need recovering, and in what order.