This week a systems administrator who had spent twelve years as a Namecheap customer posted that a single email gave him 72 hours before the company disabled his domains. The thread on r/sysadmin drew 454 points and 215 comments on Hacker News, most of them variations on “switch registrars” — which is roughly the advice you’d give a man whose house burned down: try a different insurance agent.

The interesting fact is not that a registrar behaved harshly. Registrars behave harshly constantly, quietly, thousands of times a month. The interesting fact is that Namecheap had already published a rule against doing this.

Namecheap’s Own Abuse Policy Said Not to Do This

Buried in the company’s support documentation on filing abuse complaints is a distinction most customers never read. When Namecheap hosts the domain, it can investigate. When it merely registers the domain and the content sits on someone else’s servers, the company concedes that “some types of abuse may not be verified from our side.” Its stated conclusion: “we will not take restrictive action in order to avoid false-positive cases.” The categories that policy covers include copyright, spam, fraud, and malware.

So the 72-hour termination notice is not a gap in policy. It is a policy that lost an internal argument and did not tell anyone it had lost. The abuse page still says what it said; the enforcement did something else. That gap — between the published rule and the actual behavior — is the thing a twelve-year customer had no way to see, price, or appeal.

The same asymmetry shows up in the paperwork. In an earlier round of public complaints about the registrar, commenters pulled apart Namecheap’s counter-notice terms and found that submitting one requires registrants to waive legal claims against the company for acting on the original takedown. Whatever you think of that clause, it tells you which party the contract is written to protect, and it isn’t the one paying the renewal.

Takedown Is an Industry Now, With Vendors and Slide Decks

Netcraft published a piece this year titled, without apparent irony, “The Ultimate Guide to Domain Takedown Services in 2026.” It walks through the escalation ladder — hosting provider, CDN, registrar, registry, app store, code repository — and specifies the evidence package a complainant should assemble: full indicators, URLs, WHOIS data, DNS records, timestamped screenshots. The registrar is one line item in a workflow diagram.

That’s the part the thread misses. Nobody at the registrar has to dislike you. A brand-protection firm files a package; the registrar’s counsel prices the risk of ignoring it against the value of one customer’s annual renewal. One paralegal at a firm that files these packages, on her phone in the parking garage under her building after a filing deadline, described the logic without a flicker of embarrassment: “We don’t ask the registrar to adjudicate. We ask them to price the risk of not.”

That is what a functioning market in deplatforming looks like. Not a villain with a grudge — a vendor with a spreadsheet, and a counterparty whose per-domain margin wouldn’t cover a lawyer’s first six minutes.

The Appeal Everyone Wants Would Build a Speech Tribunal

The reflexive fix, already forming in the comments, is that ICANN should mandate notice, an appeal window, and an independent reviewer. Consider what that actually creates: a California nonprofit, advised by a Governmental Advisory Committee populated with representatives of governments that maintain their own lists of sites they’d like gone, installed as the world’s final arbiter of whether a domain stays up. You would trade a vendor’s caprice — which can at least be shamed, publicized, and abandoned — for an administrative procedure with a letterhead.

The deeper problem is that a domain name is not property. It is a chain of contracts of adhesion: you to the registrar, the registrar to the registry, the registry to an authority that operates by agreement rather than by sovereign grant. There is no title to quiet, no deed to record. That is why a company can repossess it on suspicion while a landlord who wants your building has to go see a judge.

Here is the uncomfortable part for readers on my side of the aisle. The property-rights and anti-delegation project of the last decade has been scrupulous about occupational licensing, administrative courts, and the regulatory state — and near-silent on domain names. Not by accident. Everyone, left and right, keeps a list of sites they’d like to see disappear, and cheering when a payment processor cuts off an adversary is conceding the whole principle. A domain is the same chokepoint, one layer lower, with less publicity and no press release.

Courts, Not Commissions

The reform that doesn’t require a new agency is a property interest recognized by courts: a registrant holds a leasehold in the name, enforceable against the registrar; suspension requires a transfer rather than a deletion, so the name survives its exile; suspension statistics get published, so patterns become visible; and a named technical contact gets notice that doesn’t arrive as a 72-hour countdown. All of it litigable. None of it requiring a working group.

Until then, the practical version: keep your zone files, split registrations across providers, and assume the name can vanish on a Tuesday. That is thin comfort for a man who lost twelve years to one email. But he was never the owner of anything — he was a customer in good standing, which is a different and much weaker thing. The 72-hour notice wasn’t a malfunction. It was the system working exactly as written, for someone who wasn’t him.

Sources