Gab is back online; its domain has migrated to Seattle-area-based registrar Epik, and Cloudflare is shielding who actually hosts the site
AFTER IT WAS revealed that the suspect in the shootings at a Pittsburgh synagogue had threatened on the social media network Gab to kill Jews …
Context & Ripple Effects
A week after GoDaddy gave Gab 24 hours to move its domain, knocking the site offline entirely, the network has found a new home: Seattle-area registrar Epik took over the domain registration, and Cloudflare is now fronting the site so the actual hosting provider stays hidden. The restoration follows coverage of how Gab became a platform of choice for neo-Nazis and extremists after the Pittsburgh shooting suspect posted threats there (New York Times reporting).
The episode matters because Gab survived its first full-stack deplatforming attempt — and did so without changing anything about its content or moderation posture. Its continued viability is underwritten by small-dollar crowdfunding under the Jobs Act of 2012, which has kept roughly $2M flowing through broker StartEngine even as mainstream infrastructure firms refuse it service.
First-order effects
- Gab is back online within days of going dark, with Epik replacing GoDaddy as registrar of record and Cloudflare absorbing traffic so the underlying host is no longer publicly identifiable.
- Cloudflare is now in the position of shielding a site that one major registrar already expelled, making it the visible gatekeeper for whether Gab stays reachable.
Second-order effects
- Other registrars and CDN operators face a forced choice: follow GoDaddy's precedent and refuse extremist-adjacent domains, or accept the business Epik is now collecting — effectively splitting the infrastructure market into refusing and accepting tiers.
- Because Cloudflare hides the host, pressure campaigns can no longer easily target Gab's hosting provider directly, shifting activist and advertiser attention back up the stack to Cloudflare itself.
Third-order effects
- If the pattern holds, moderation migrates from the application layer to the infrastructure layer: a site's survival depends less on its own policies than on which registrar, CDN, and host will carry it, creating a parallel stack of tolerant providers.
- Regulators and payment/advertising networks may respond to this arbitrage by treating infrastructure access as the choke point for platform accountability, since domain-level expulsion proved reversible in days.
The trend: Content moderation is moving down the stack from social platforms to domain registrars and CDNs, where a single willing provider can undo an entire industry's refusal.