No Registrar, No Rules: Americans Are Hosting Websites That Nobody Can Shut Down

Let's say you build something. A community resource, a political archive, a whistleblower drop site. You pay for your domain, you pay for your hosting, you follow the rules. And then one day — maybe because someone powerful complained, maybe because an algorithm flagged you, maybe because your registrar just decided your content was inconvenient — it's gone. Domain suspended. Hosting terminated. Years of work, vanished.

This isn't a hypothetical. It happens. And a growing number of Americans have decided they're done playing by rules designed to make that easy.

They're building what some are calling the sovereign web: websites that don't depend on ICANN-approved domain registrars, centralized hosting providers, or any single point of failure that a corporation or government agency can quietly press a button to kill.

The Problem With the Web You're Used To

Most people don't think about what it actually means to "own" a domain name. You don't own it — you rent it. From a registrar. Who operates under rules set by ICANN, a nonprofit that's cozy with governments, law enforcement agencies, and major platform interests. Your registrar can suspend your domain. Your hosting provider can terminate your account. Your CDN can drop you. Cloudflare has done it. GoDaddy has done it. Even GitHub Pages has yanked sites.

The traditional web is built on a stack of rented permissions, and most users never notice until the permissions get revoked.

"People think they have a website," says one developer active in the Handshake community who asked to be identified only by their handle, Tessera. "They have a lease. There's a difference."

Handshake: Owning Your Name for Real

Handshake (HNS) is a decentralized naming protocol that operates completely outside the ICANN system. Instead of registering a domain through a company that can take it away, you own a top-level domain recorded on a blockchain. Nobody can revoke it. Nobody can transfer it without your cryptographic keys.

It sounds niche. It kind of is, still. But the infrastructure around it is maturing fast. Resolvers like NextDNS and certain community-run DNS servers now support Handshake lookups. Browsers like Brave have experimented with native HNS support. And a growing number of technically inclined users are setting up their systems to resolve Handshake domains natively.

The catch? Your average person visiting from Chrome isn't going to find your .free or .forever Handshake domain without some configuration. That's a real friction point. But advocates argue it's a friction worth leaning into — the point isn't to immediately replace the mainstream web, it's to build parallel infrastructure that exists outside its control.

IPFS: Hosting Without a Host

If Handshake solves the naming problem, IPFS — the InterPlanetary File System — attacks the hosting problem from a completely different angle.

Traditional hosting means your files live on a server somewhere, and if that server goes down (or gets pulled), your site goes with it. IPFS flips the model. Instead of addressing content by location ("this file is at this IP address"), it addresses content by what it actually is — a cryptographic hash of the data itself. Anyone who has a copy of your content can serve it. The more people who pin your files, the more resilient your site becomes.

Publish something on IPFS, get a few people to pin it, and it becomes genuinely difficult to disappear. There's no single server to seize. No hosting account to terminate. The content just... persists, distributed across whoever chose to keep a copy.

Projects like Fleek have made IPFS deployment feel closer to a normal web workflow — push your static site, get a content hash, done. And tools like ENS (Ethereum Name Service) let you attach a human-readable name to that content hash, so yoursite.eth resolves to your IPFS-hosted content for anyone using a compatible wallet or browser extension.

"It's not magic," admits Priya, a web developer based in Austin who's been running her personal site on IPFS for over a year. "There's still a learning curve. But once it clicked for me, I realized I'd been operating in this totally unnecessary state of dependence. I was paying someone for the privilege of letting them delete my stuff."

Mesh Networks: Going Even Deeper

For the most committed members of this movement, even decentralized hosting on the public internet isn't enough. The internet itself — the physical infrastructure of cables, routers, and ISPs — is another layer of centralized control.

Mesh networking projects like Meshtastic, NYC Mesh, and various community-run initiatives are quietly building alternative connectivity layers. These networks route traffic peer-to-peer, often over radio frequencies or community-maintained hardware, bypassing traditional ISPs entirely for local communication.

In a mesh context, hosting a "website" might mean running a small server that's accessible to anyone connected to the local mesh — no ISP required, no cloud provider required, no domain registrar required. It's hyper-local, sure. But in contexts where local resilience matters — think disaster preparedness, or communities where ISP access is unreliable or monitored — it's not a toy. It's infrastructure.

Activists in several US cities have been quietly stitching together mesh nodes for years. The goal isn't always to replace the internet. Sometimes it's just to have a fallback that nobody can cut off.

Who's Actually Doing This?

The sovereign web isn't a monolith. The people building it come from pretty different places.

Some are libertarian-leaning technologists who distrust government overreach and want infrastructure that's mathematically immune to takedown orders. Some are progressive activists who've watched platforms deplatform movements they care about and want infrastructure that doesn't depend on Silicon Valley's approval. Some are just privacy nerds who find the whole project intellectually satisfying.

What they share is a bone-deep skepticism of permission-based infrastructure — the idea that your ability to publish, communicate, and exist online should require ongoing approval from a corporate intermediary.

"The whole point of the internet was supposed to be that it routes around damage," says Marcus, a network engineer in Portland who contributes to several open-source mesh projects. "Somehow we built a version of it where one company can nuke your presence with a support ticket. That's not a feature. That's a bug."

The Honest Limitations

Look, we're not going to pretend this is all seamless. It isn't.

IPFS sites can be slow if nobody's actively pinning your content. Handshake domains require end-user configuration to resolve. Mesh networks are genuinely local and limited in range. None of these tools are ready to replace the experience of typing a URL into Chrome and having a page load in 200 milliseconds.

And there are harder questions too. Decentralized infrastructure is harder to moderate. Content that should be removable — CSAM, targeted harassment, dangerous disinformation — becomes more difficult to address when there's no central authority to pressure. The same properties that protect a political dissident protect bad actors. That tension is real, and anyone building in this space needs to think seriously about it.

Why It Still Matters

Despite the rough edges, the sovereign web project is worth paying attention to — not because it's going to replace the mainstream internet tomorrow, but because it's building the vocabulary and the tooling for a different kind of online existence.

Every time a platform bans a community, every time a registrar suspends a domain under political pressure, every time a hosting provider caves to a DMCA demand of dubious legitimacy, a few more people go looking for alternatives. And increasingly, those alternatives exist.

Handshake. IPFS. ENS. Mesh protocols. Tor hidden services. These aren't just nerd toys. They're the early infrastructure of a web that doesn't ask for your permission slip.

Free your stack. Own your future. That's not just a slogan — for a growing number of Americans, it's a technical roadmap.