---
title: Launching a new keyserver! 🚀
---

From a community effort by [Enigmail](https://enigmail.net), [OpenKeychain](https://openkeychain.org), and [Sequoia PGP](https://sequoia-pgp.org), we are pleased to announce the launch of the new public OpenPGP keyserver {{ brand() }}! Hurray! 🎉

#### Give me the short story!

*   Fast and reliable. No wait times, no downtimes, no inconsistencies.
*   Precise. Searches return only a single key, which allows for easy key discovery.
*   Validating. Identities are only published with consent, while non-identity information is freely distributed.
*   Deletable. Users can delete personal information with a simple email confirmation.
*   Built on Rust, powered by [Sequoia PGP](https://sequoia-pgp.org) - free and open source, running AGPLv3.

Get started right now by [uploading your key](/upload)!

#### Why a new keyserver?

We created {{ brand() }} to provide an alternative to the SKS Keyserver pool, which is the default in many applications today. This distributed network of keyservers has been struggling with [abuse](https://medium.com/@mdrahony/are-sks-keyservers-safe-do-we-need-them-7056b495101c), [performance](https://en.wikipedia.org/wiki/Key_server_\(cryptographic\)#Problems_with_keyservers), as well as [privacy issues](http://www.openwall.com/lists/oss-security/2017/12/10/1), and more recently also [GDPR](http://nongnu.13855.n7.nabble.com/SKS-apocalypse-mitigation-td228252.html) compliance questions. Kristian Fiskerstrand has done a stellar job maintaining the pool for [more than ten years](https://blog.sumptuouscapital.com/2016/12/10-year-anniversary-for-sks-keyservers-net/), but at this point development activity seems to have [mostly ceased](https://bitbucket.org/skskeyserver/sks-keyserver/pull-requests/60/clean-build-with-405).

We thought it time to consider a fresh approach to solve these problems.

#### Identity and non-identity information

The {{ brand() }} keyserver splits up identity and non-identity information in keys. You can find more details on our [about page](@/_index.md): The gist is that non-identity information (keys, revocations, and so on) is freely distributed, while identity information is only distributed with consent that can also be revoked at any time.

If a new key is verified for some email address, it will replace the previous one. This way, every email address is only associated with a single key at most. It can also be removed from the listing at any time by the owner of the address. This is very useful for key discovery: if a search by email address returns a key, it means this is the single key that is currently valid for the searched email address.

#### Support in Enigmail and OpenKeychain

The {{ brand() }} keysever will receive first-party support in upcoming releases of [Enigmail](https://enigmail.net) for Thunderbird, as well as [OpenKeychain](https://play.google.com/store/apps/details?id=org.sufficientlysecure.keychain&hl=en) on Android. This means users of those implementations will benefit from the faster response times, and improved key discovery by email address. We hope that this will also give us some momentum to build this project into a bigger community effort.

#### Current challenges

Privacy-preserving techniques in keyservers are still new, and sadly there are still a few compatibility issues caused by splitting out identity information.

In particular, when GnuPG (as of this writing, version 2.2.16) encounters an OpenPGP key without identities, it throws an error "no user ID" and does not process new non-identity information (like revocation certificates) even if it is cryptographically valid. We are actively engaged in providing fixes for these issues.

#### The future

Privacy-preserving techniques in keyservers are still new, and we have more ideas for reducing the metadata. But for now, our plan is only to keep {{ brand() }} reliable and fast 🐇, fix any upcoming bugs 🐞, and [listen to feedback](/about#community) from the community. 👂

For more info, head on over to our [about page](@/_index.md) and [FAQ](@/faq.md) pages. You can get started right away by [uploading your your key](/upload)! Beyond that there is more cool stuff to discover, like our [API](@/api.md), and an [Onion Service](@/faq.md#tor)!

Cheers! 🍻
