Dreamhost, after working with DoJ for several months, opposes DoJ request for info on owners and visitors of anti-Trump site, including 1.3M IP addresses
I used to have DreamHost as a webhost. We parted ways, but I always admired and appreciated that they reliably stood up for their customers …
Context & Ripple Effects
DreamHost's refusal caps months in which it had been working with the Justice Department on a warrant targeting a politically critical website — until the scope ballooned to include identifying data on owners and visitors, among them 1.3M IP addresses. The company chose open litigation over quiet compliance, making it the test case for how far a hosting provider will go to shield customer and visitor records from a federal dragnet.
The standoff landed in a week when infrastructure firms' user-data stances were already under scrutiny: Cloudflare had just dropped its DDoS protection for Daily Stormer weeks earlier, showing the opposite instinct — a provider unilaterally deciding whose speech it serves. DreamHost's fight was about whether providers get any say at all when the government comes for visitor logs.
First-order effects
- The DoJ's own follow-up shows the pressure worked: days later it conceded the warrant was overbroad and disclaimed interest in the 1.3M visitor IP addresses (DoJ calls its own warrant too broad), while a judge ordered handover of user data with limits and court vetting of what the agency actually uses (judge imposes limits on the handover).
Second-order effects
- The court's continued involvement hardened into precedent for process: by October the judge required DreamHost to redact identifying information and demanded the DoJ justify why it needs each element (redaction order forces DoJ to justify the data) — raising the cost to prosecutors of sweeping warrants against any host.
Third-order effects
- If the pattern holds, bulk visitor-log demands become subject to judicial narrowing rather than rubber-stamp approval, pushing law enforcement toward narrower, targeted requests — and positioning hosting providers as de facto privacy litigants whose willingness to fight shapes what warrants agencies bother drafting.
The trend: Web infrastructure providers are being pulled into constitutional litigation over government access to user and visitor data, with courts — not company policies like Cloudflare's — emerging as the real constraint on mass collection.