Skip to main content

What's Your Hosting Company's Average Subpoena Response Time?

4 min read
TL;DR: Your hosting company's willingness (or unwillingness) to comply with Subpoenas may soon be seen as a competitive feature.

Subpoena

Bluehost, the web hosting service which powers more than 1.9 million sites globally, making it one of the top 20 largest hosting companies in the world and approximately 2% of the internet’s traffic (link removed), recently came under fire for its decision to depart from well-established internet standards and reveal the identity of one of its subscribers, over what later proved to be an unfounded suit.

From a technical standpoint, Bluehost is one of the good guys. I’ve hosted sites with them since 2005 and looking back at the past six months, I’ve enjoyed a 99.79% uptime, with an average response time just under a second. But that’s half the equation. Web hosting is not simply a cost-benefit analysis of price to uptime and responsiveness. There’s a third factor there: trust.

Why does a hosting company require trust? In December, a fake news release was published on a Bluehost powered site by an anonymous satirical group, stating that after “a recent internal and thorough company review,” Koch Industries, an oil processing company, would be “restructuring its support of climate change research and advocacy initiatives.”

The problem occurred, however, when Bluehost was over eager to comply with Koch’s subpoena demanding the identity of the anonymous poster, arguing, “[w]e are not in the business of harboring, you know, felons and crooks. We are not about that. This isn’t WikiLeaks… [w]e comply with the law here.”

Bluehost knew that the customer wanted to be anonymous (they had opted into Bluehost’s domain protection program), however, the law here depends on Bluehost providing their client with knowledge of the subpoena, so that a timely objection can be heard by the issuing judge. In the words of the site’s own counsel:

The judge ruled that [Bluehost’s customer,] Youth for Climate Truth had a First Amendment right to issue a satirical press release and site – in which the group impersonated Koch and announced that the company had reversed its position on climate change – in an effort to call attention to Koch’s notorious bankrolling of efforts to deny climate change.

The U.S. District Court for the District of Utah rejected all of Koch’s legal claims, which alleged trademark infringement, unfair competition, cybersquatting, computer hacking and breach of the company website’s terms of use. The judge also issued an order barring Koch from using any identifying information it had already obtained about our clients via subpoena.

The problem here arises not from Koch trying to use its legal muscle to silence political satire, but from Bluehost’s over willingness to comply with a request to identify the anonymous satirist.

In Bluehost’s defense, the suit came at the height of the Wikileaks debacle, a time when the industry’s top names were identifying otherwise anonymous customers, but at the same time, as political interactions move increasingly online, our marketplace of ideas relies increasingly on hosting companies and internet services providers to remain good political citizens (not simply corporate ones).

While technology may lend voice to otherwise marginalized political groups, it does not come without risk. In a shared hosting environment like Bluehost, “your” site, is not necessarily “your” site. Will we begin to see subpoena response times along the list of benchmarks and features when evaluating hosting companies? Probably not. But if you are planning on leveraging shared servers — be they Bluehost, Twitter, or YouTube — to blog about anything more than say, DC Summer Interns, perhaps you should take a look at your hosting company’s legal record before you click submit.

Originally published May 10, 2011 View revision history
Share

More to explore

Everyone Contributes

3 min read

Code is just one way to contribute to open source. Projects thrive when they create clear paths for non-technical contributors to participate.

Removing a feature is a feature

8 min read

Features aren't free. Every time you remove one that doesn't serve your core use case, you're adding an implicit feature that does.

How not to prioritize a feature

7 min read

The hardest part of software development is not coming up with features to build, but instead, deciding what features will have the biggest impact.

The top 10 posts of the past 10 years

2 min read

Celebrating 10 years and nearly 200,000 words of blogging with a countdown of the most viewed posts, from open source licensing to communicating at GitHub.

Securing the Status Quo

30 min read

Federal agencies spend billions on IT security, yet rigid compliance frameworks create false safety while stifling innovation against real threats.

Why WordPress

11 min read

The case for WordPress as the world's most versatile publishing platform, from its proven track record and ease of use to its community-driven ecosystem.

Ben Balter

I'm Ben Balter — I write here about engineering leadership, open source, and showing your work. I wrote Open & Async, the playbook for remote and distributed teams. My open source projects have hundreds of millions of downloads. I was the Director of Hubber Enablement at GitHub, where I helped thousands of GitHubbers do their best remote work. Before this role: Chief of Staff for Security, enterprise PM, and GitHub's first Government Evangelist. Before GitHub: attorney, Presidential Innovation Fellow, and member of the White House's first agile development team. More about the author →

Follow along: Bluesky LinkedIn

This page is open source Help improve this article on GitHub