I want to upload my PGP public key on a public server. Till the time PGP was an independent organization, I heard a lot about KeyServers, but after Symantec acquired PGP, what is the future of these servers?

Is there any other alternative way to keep my public keys online?


Yes, keyservers still exist:

People usually use SKS, since it consists of many servers which synchronize their databased continuously. Meanwhile, Global Directory is a single, commercially operated server which may go down at any time; the same goes for the new non-SKS keyservers.

However, SKS has the problem of accepting anything and storing it forever (much like a blockchain). This has caused problems for a long time, but started getting massively abused in 2018–2019. The new keyservers don't have synchronization partly because they want to figure out how to combine opposing goals.

The popular pgp.mit.edu has finally upgraded to SKS and is now part of the pool. There also exist a bunch of other keyservers not part of the SKS pool (listed in the same status page). The default keyserver for GnuPG, keys.gnupg.net, is now an alias to the SKS pool as well.

Another widely known server, subkeys.pgp.net, is not part of the SKS pool since (AFAIK) it still runs a very old version of PKS instead. (It also seems to be down, although the website is up.)

If your email address is at a domain name you manage (i.e. can have arbitrary DNS records created), it is also possible to publish your PGP key using DNS. The easiest method for that is PKA, which only requires the ability to create TXT records; see the article on publishing PGP Keys in the DNS.

PKA, as well as two other methods (CERT and IPGP CERT), are described in this guide in much more detail.

One downside of all three methods is that GnuPG must be manually configured to use them, and PGP.com doesn't even support using DNS. Meanwhile, practically all versions of PGP and GnuPG can use keyservers.

Note: GnuPG 2.1.3 has completely changed the PKA format (into a mix of CERT and old PKA).

Given that GnuPG did this in a minor release without any worry about backwards compatibility with the old format (in fact, the old format used to outright crash 2.1.x for a while afterwards), I'm no longer comfortable suggesting pubkey publication in DNS. It's a waste of time. Use keyservers.

  • When i publish a key( which contains private+public) , does it also publish a private ??? it must not.... – Royi Namir Dec 23 '12 at 11:33
  • 1
    @grawity I don't use PGP Global Directory anymore due to many of the links moving back to symantec and whois information doesn't return with any results which worries me very much. Also the SSL security for PGP Global Directory is pretty bad as well. – meguroyama Mar 13 '14 at 7:00
  • 2
    @meguroyama PGP uses its own "Web of trust" for verifying keys, so SSL support in keyservers is only useful for privacy reasons (to hide what keys you retrieve). Many SKS keyservers still lack SSL completely, and while they're slowly adding it, it's not a security problem. – grawity Mar 15 '14 at 9:23
  • 1
    As for the WHOIS information – you don't know who runs most SKS keyservers either; and this too doesn't matter. – grawity Mar 15 '14 at 9:25
  • 1
    @meguroyama: Right – the only problem is that the Global Directory is isolated; it does not exchange keys with anything else. On the other hand, all SKS keyservers sync to each other; if one goes down, two dozen others continue working. – grawity Mar 19 '14 at 11:30

UPDATE: in 2017 you might want to consider using Keybase, the Social Approach to Public Key Verification.

"Keybase is a free, open source security app. It's also a public directory of people.

The Keybase app helps you perform cryptographically-secure operations with people you know on the Internet: chatting, file sharing, even publishing public documents."


I was facing the same issue today and found that neither keyserver.pgp.com/ nor sks-keyservers.net/ would reply timely to me.

However, I found that keyserver.ubuntu.com worked.

  • 1
    You should use the high-availability subset of the pool: ha.pool.sks-keyservers.net -- adding more keyservers can decrease the reliability because less reliable servers get queried – Otto Allmendinger Apr 1 at 12:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.