Who owns your website? Probably not you.

You Google "who owns my website domain" because you just found out the answer isn't you.

Maybe the site went down and the hosting company won't talk to you. Maybe you're trying to switch email providers and nobody knows the DNS login. Maybe the freelancer who built your site years ago registered everything under his personal Gmail, moved, changed numbers — and now your business's front door is legally in the hands of someone you can't reach.

The pattern is common everywhere, and we see it regularly around DFW: a domain renewing on a credit card belonging to someone the owner hasn't spoken to in years; a business discovering mid-crisis that the "website guy" is the only person who can receive its password-reset emails. It's common, it's usually fixable, and it's completely preventable going forward.

The five accounts that make up "your website"

Your website isn't one thing. It's at least five separate accounts, and you can own some without owning others:

• The domain (your address). Registered at a registrar — GoDaddy, Namecheap, Cloudflare, Squarespace Domains. Whoever controls the registrar account controls the domain. This is the single most important one: lose the site files and you rebuild; lose the domain and you lose the address every customer, review, and search ranking points to.
• DNS (your traffic directions). Often at the registrar, sometimes separate — Cloudflare is common. DNS decides where your web traffic and email actually go. Whoever controls DNS can point your domain anywhere, including nowhere.
• Hosting (where the site lives). WP Engine, SiteGround, Vercel, or a reseller account your developer runs. This holds your actual site files and database.
• Business email. Google Workspace or Microsoft 365, usually tied to your domain. If DNS breaks, email breaks. If email breaks, so do the password resets for everything else.
• Analytics and listings. Google Analytics, Search Console, Google Business Profile, ad accounts. Less catastrophic to lose, painful to rebuild — years of data and reviews live here.

The failure pattern is almost always the same: the developer registered the first three under his own accounts because it was faster, and nobody ever moved them.

The 20-minute ownership audit

Do this today. You need a browser and a notepad.

• Step 1 — Look up your domain. Go to lookup.icann.org and search your domain. Most results are privacy-masked now, so the key data points are which registrar holds it and the expiration date. Write both down.
• Step 2 — Try to log in. Go to that registrar and attempt a password reset with your business email. If the reset email arrives in your inbox, you likely control the domain — change the password, add two-factor auth, and confirm the payment card on file is yours. If the reset goes to an email you don't recognize, you've found your problem.
• Step 3 — Check DNS. Run your domain through a nameserver checker (dnschecker.org works). If the nameservers point at Cloudflare or another DNS service, that's a sixth login to track down.
• Step 4 — Identify your host. Your monthly or annual invoice usually says. If you're not paying anyone for hosting, someone else is — and their card expiring takes your site down.
• Step 5 — Inventory the rest. Google Analytics, Search Console, Google Business Profile: check whether your email is an owner — not just a "user" or "manager" — on each. Ownership levels matter; a manager can't remove a rogue owner.

Score yourself: five accounts, all with your business email as owner, payment methods in your name, two-factor on. Anything less is homework.

Recovery: when the person holding the keys is gone

If the audit turned up accounts you can't access, work this order:

First, try the human route. Email, text, LinkedIn, mutual contacts. Most disappeared web guys aren't hostile — they're just busy or out of the business. A polite "I need the domain transferred to my own account, happy to pay for an hour of your time" resolves the majority of these. Offer money. An hour of transfer work is cheap compared to what comes next.

If they're unreachable, go to the registrar directly. Every ICANN-accredited registrar has a dispute and account-recovery process. You'll typically need to prove you're the business the domain represents: formation documents, a trademark if you have one, invoices showing you paid for the site. GoDaddy, Namecheap, and Squarespace all publish documented ownership-dispute procedures — expect document uploads and days-to-weeks of back and forth, not an instant fix. Registrars also have specific processes for domains registered to defunct companies or deceased owners; estate documents or proof of business succession apply.

If someone is actively holding your domain hostage — refusing to transfer, demanding an unreasonable payout — you have two formal paths: a UDRP complaint through an ICANN-approved provider like WIPO (built for trademark-based disputes, typically $1,500+ in filing fees), or an attorney letter, which often resolves things faster because most freelancers fold when the situation gets formal. A registered trademark on your business name makes your position dramatically stronger.

Worst case: you can't recover it. Watch the expiration date from your ICANN lookup — unrenewed domains eventually drop and can be re-registered, though redemption windows and drop-catching services complicate it. Sometimes the pragmatic answer is a new domain and a clean rebuild. Painful, but survivable, and better than years in limbo.

Whatever happens with the domain, get copies of your site files and database now, while the site is still up. A full backup can be taken from the live site even without hosting access.

The handoff terms to demand from any vendor

Going forward, put these in writing before anyone builds anything:

• The domain is registered under an account you own — your business email, your card. The vendor gets delegated access; registrars support this natively. They never get to be the owner.
• Hosting is in your name or contractually yours. If the vendor hosts as part of a care plan, the contract must state the site, files, and database are your property and will be handed over within a set window — seven days is reasonable — at no additional charge on termination.
• You are an owner, not a user, on Analytics, Search Console, and Google Business Profile.
• Credentials live in a shared record you control, not in one person's head.
• A "hit by a bus" clause: if the vendor becomes unreachable for 30 days, you're contractually authorized to take full control of everything.

A legitimate professional won't blink at any of this. Hesitation on the ownership question is the single most reliable red flag in vendor selection.

How West Fork approaches this

Every project we take on starts with the ownership audit above — including sites we didn't build. Domains sit in registrar accounts our clients own; we work through delegated access. Handoff terms are written into every agreement, and if a client leaves us, they leave with everything: files, database, DNS records, credentials, documentation. We'd rather earn the renewal than hold the keys.