Six Names, One URL: The Gentle Chaos of Co-Owned Domains

Every shared domain starts the same way: somebody says "I'll grab it," somebody else Venmos them twelve bucks, and just like that, six friends technically own a piece of the internet.

Nobody reads the registrar's terms. Nobody thinks about what happens in three years when one of them moves to Austin, one of them stops answering texts, and one of them decides the whole project was their idea anyway.

We spent the last few weeks asking friend-run projects how they actually manage a co-owned domain — and what they'd do differently.

The $2 Problem Nobody Solves

The registration fee is easy. Splitting $12 six ways is trivial. The real question is what happens at renewal, when the card on file expired, the person who bought it is on a flight, and the whole site goes dark for 36 hours.

"We lost a .com for four days once," one group project founder told us. "Somebody's bank flagged the charge as fraud because four other people had paid it before. We got it back, but I aged a decade."

The groups that survive tend to converge on the same fixes: one dedicated card, one "domain treasurer," and a renewal date on a shared calendar with three reminders. Not glamorous. Effective.

The Ghost Partner

Here's the scenario nobody plans for: one of the six just... stops responding. Not fighting. Not quitting. Just gone — new job, new baby, new obsession with sourdough. But their name is still on the domain, and now the group wants to rebrand.

The projects we spoke to handled this in one of three ways:

• The buyout. Everyone else chips in to cover the ghost's share, and the domain gets transferred to a single owner or an LLC.
• The grandfather clause. The quiet partner keeps a symbolic 5% and a permanent credit in the footer. No vote, no veto.
• The sunset rule. If you don't respond to two consecutive project votes within 30 days, your ownership converts to a "thanks for the memories" acknowledgment.

None of these were written down at the start. All of them were invented mid-crisis, usually at 11 p.m. in a group chat.

What Everyone Wishes They'd Put in Writing

Ask any group that's been through a domain breakup and you'll hear the same short list:

1. Who legally holds it. One name on the registrar account, clearly designated, ideally not the person most likely to disappear.
2. What happens to the domain if the project dies. Does it go to the group? The founder? Does it get sold and split?
3. A simple buyout price. Even "cost of registration plus $1 per year held" prevents a decade of resentment.
4. A decision threshold. Renewals need a simple majority. Selling needs everyone. Write it down.

One project we talked to did it right from the start. "We wrote a two-paragraph agreement in a shared Google Doc," they told us. "Everyone signed with an emoji. It's not legally binding. It doesn't need to be. It just means we all remember agreeing."

The Weird Benefit Nobody Mentions

For all the horror stories, almost every group we spoke to said the shared domain made the friendship stronger. There's something about jointly paying for a tiny piece of internet real estate — checking in every year, arguing about whether to renew the .io nobody uses — that keeps a group chat alive long after the project itself would have faded.

A domain is a small thing. But it's a small thing you hold together. And for a lot of internet friend groups, that annual renewal email is less of an invoice and more of a reunion.

If you're about to split a domain with friends: congratulations. Take ten minutes, open a doc, and write down who holds it, who pays, and what happens if someone ghosts. Your future selves — all six of them — will be glad you did.