Updated October 2026: This post has been expanded from its original December 2013 version with a full account of why Lavabit closed, what the courts decided, how Hushmail handled a similar demand, and what happened to Lavabit afterward. It is a historical account; details describe the time it covers, not today.

On August 8, 2013, a small Texas email company called Lavabit went dark. Its owner, Ladar Levison, posted a short notice saying he would not become "complicit in crimes against the American people," and that he was legally barred from explaining what had happened over the previous six weeks. Lavabit had around 400,000 accounts, according to court records. Earlier reports said 350,000. Most users found out the service was gone when they tried to log in.
Weeks earlier, the world had learned that Edward Snowden, the former NSA contractor behind the leaks about U.S. surveillance programs, used a Lavabit address. The link was obvious, but nobody could confirm it officially for years. This post looks back at the Lavabit shutdown as a piece of history: what the government asked for, why Levison refused, what the courts said, and the practical lessons that still apply to anyone choosing a "secure" email service.
What Lavabit was
Lavabit started in 2004. A group of Texas programmers ran it first under the name Nerdshack LLC, and the company became Lavabit LLC the next year. It offered free and paid email accounts and promoted its security features. Messages were stored encrypted on its servers, so the stored mail could only be unlocked with each user's password.
That design mattered. Lavabit was not refusing all cooperation with police. Before 2013 it had complied with ordinary search warrants for individual accounts, including one in June 2013 tied to a child-abuse-imagery investigation. Levison's quarrel in the Snowden case was with the scope of the demand, not with the idea of lawful access to one person's data.
What the government asked for
The legal fight came in stages. On June 10, 2013, a court order under section 2703(d) of the Stored Communications Act sought metadata, meaning records about messages rather than their contents, for one unnamed customer. It was served the day after Snowden revealed his identity. A pen register and trap-and-trace order followed. That kind of order lets investigators collect addressing information about communications in real time.
The sticking point was encryption. Lavabit's connections were protected by TLS (often still called SSL). Its private SSL key was the secret that made the encryption work. Watching one user's traffic in real time meant breaking that protection, so in July 2013 investigators obtained a search warrant for the private key itself. Lavabit used one key for the whole service, so handing it over would expose every user's traffic, not just the target's.
Levison offered alternatives. According to the case history, he proposed providing the target's metadata, without message contents or passwords, for $2,000 in development costs plus $1,500 for collection. He also offered to write code that would capture only the target's data. The court rejected these offers. Lavabit was ordered to provide the key in a machine-readable format by noon on August 5, 2013, or pay a fine of $5,000 per day.
The 4-point font
Levison's first response became one of the case's best-known details. He gave the government the key printed on paper in a tiny 4-point font. An FBI motion called the printout "largely illegible." It noted that typing in 2,560 characters by hand would be prone to error. Three days after the deadline for a usable copy, Levison shut Lavabit down instead.
Shutting down did not undo the demand, but it changed what the key was worth. With the service closed, there was no live traffic left to watch. Lavabit was the first company known to close rather than compromise every customer to satisfy a surveillance order. In the same month, Silent Circle, another encrypted communications company, discontinued its email service and erased the keys that gave access to its stored and transmitted mail.
- 2004
Texas programmers start the service under Nerdshack LLC, renamed Lavabit LLC the following year. - June 10, 2013
A court order under 18 U.S.C. 2703(d) seeks metadata on one unnamed Lavabit customer. - July 2013
Investigators obtain a search warrant for Lavabit's private SSL keys, which protect every user's connection. - August 1, 2013
The district court order that the appeals court later says covered the encryption keys. - August 5, 2013
Deadline to hand over the keys in machine-readable form or face a $5,000-a-day fine. - August 8, 2013
Ladar Levison suspends Lavabit. Silent Circle shuts its own encrypted email service the same month. - October 2, 2013
The court unseals the case records, redacting the target's name. - April 16, 2014
The Fourth Circuit upholds the contempt finding against Lavabit and Levison. - Early 2016
An unredacted court filing shows the target address was Ed_Snowden@lavabit.com. - January 20, 2017
Lavabit relaunches on the DIME protocol and the open-source Magma mail server.
What the courts decided
Levison appealed. The case records were unsealed on October 2, 2013, with only the target's details blacked out. On April 16, 2014, a three-judge panel of the U.S. Court of Appeals for the Fourth Circuit upheld the contempt finding against Lavabit and Levison.
The ruling was narrower than many people expected. Writing for the panel, Judge G. Steven Agee said Lavabit had not properly raised its main arguments in the lower court. Its only earlier objection had been a vague complaint about harm to its business model. Because Lavabit admittedly did not comply, the appeals court found no error in the contempt finding. It did not rule on the bigger constitutional question of whether the government could demand a key that protected thousands of uninvolved users. Lavabit lost on procedure, and that big question was never answered.
The identity of the target stayed officially secret until a mistake in early 2016. When case documents were published, the target's email address, Ed_Snowden@lavabit.com, had been left visible on an appeal cover sheet. Levison had been barred from naming the target under threat of contempt. The error confirmed what most observers had assumed.
After Lavabit: what Hushmail's record showed
After the Lavabit shutdown, many readers asked whether other secure email providers, such as Canada's Hushmail, would hold out the same way. Hushmail's own history suggested a different approach.
In 2007, court documents in a U.S. prosecution of alleged steroid dealers showed that Hushmail had turned over 12 CDs of decrypted email from three targeted accounts. The orders came through a mutual legal assistance treaty between the U.S. and Canada and were filed in a Canadian court. Hushmail had added a server-side encryption option in 2006. Users who skipped its Java applet had their passphrase handled on the company's servers, which let the company decrypt their mail when ordered.
The company was open about its position. Its chief technology officer at the time said the service was not suitable for hiding illegal activity. He said it would respond only to orders aimed at named accounts, would refuse broad collection, and had never challenged an order in court. Wired went further and suggested that even the more secure Java mode could be defeated if the company were compelled to send a modified applet to a target.
Put side by side, the two cases show the real question for any encrypted email service. The key issue is not how strong the encryption is, but who holds the keys and what the provider will do when a court demands them.
| Design | Who can read stored mail | What a court order can reach |
|---|---|---|
| Lavabit (2013): mail encrypted on the server | The provider, once a user logs in with a password | Live traffic, if the provider's TLS key is surrendered |
| Hushmail (2007): server-side encryption option | The provider, while it handles the passphrase | Decrypted copies of a targeted account's mail |
| Hushmail (2007): Java applet mode | In principle only the user | A modified applet pushed to a targeted user, as Wired suggested |
| End-to-end design (DIME goal) | Only the sender and recipient | Mostly metadata, depending on the setup |
Simplified summary of designs described in the sources below. It is not a security rating of any current product.
What happened next
Levison spent the following years trying to build email that could not be handed over even by its operator. At the DEF CON 22 conference in August 2014, a year after the shutdown, he announced the Dark Internet Mail Environment (DIME). DIME was a specification for end-to-end encrypted email that also tried to limit the metadata a server could see. It was developed through a group called the Dark Mail Alliance. By mid-2016, other collaborators had reportedly left the project, and Levison was working on DIME largely alone.
On January 20, 2017, Lavabit relaunched using DIME and Magma, an open-source mail server. The stated goal was a design where, at the highest security settings, a subpoena could not force the provider to hand over readable mail. At first only former customers and early sign-ups were admitted, and new customers were accepted again later in 2017. Its availability for new users has varied since, so check its current status directly before relying on it.
The case reached well beyond one small company. It is still cited in debates about encryption and lawful access, because it showed in practice what a demand for a provider's master key means for users who are not under investigation.
Lessons that still apply
- Ask who holds the keys. If a provider can decrypt your stored mail, a court can order it to. End-to-end encryption, where only you and your recipient hold the keys, is the only design that takes the provider out of that position.
- Metadata is often not protected. Even with encrypted contents, records of who emailed whom and when may be visible to the provider. The first Lavabit order sought exactly that kind of information.
- Read the provider's threat model and transparency reports. Reputable services explain what they can and cannot hand over and publish how many legal requests they receive. Treat vague promises of "military-grade" security with caution.
- Plan for the service disappearing. Lavabit users lost access overnight and had only a short window later in 2013 to download their data. Keep backups of important mail and use a domain you control if continuity matters.
- Jurisdiction helps less than people think. Hushmail was based in Canada, yet U.S. investigators reached its data through a treaty request. Cross-border legal cooperation is routine.
Lavabit's story is not a case for or against Edward Snowden. It is a case about architecture. A service built so that one key unlocks everyone ends up holding everyone's privacy in a single place, and the 2013 shutdown showed how quickly that key can become the target.
Sources
- Wikipedia: Lavabit
- Threatpost: Federal court rejects Lavabit contempt appeal (2014)
- Al Jazeera: Encrypted US email service shuts down (2013)
- Techdirt: Redaction failure confirms target of Lavabit investigation (2016)
- The Register: Hushmail turns over emails under court order (2007)
Top image: "Empty server racks - IMG 3674" by Jemimus, CC BY 2.0, via Wikimedia Commons (resized). Charts by Thank You Robot.
0 Comments