PGP (Pretty Good Privacy) is a method of encrypting and signing data (for example an email) in a secure “end to end” way. This means, the message is encrypted on your computer, using the recipient’s public key, in a way that the e-mail server has no knowledge of the content of the message. The recipient of the message then decrypts the message on their own computer using their private key.
OpenPGP software uses a combination of strong public-key and symmetric cryptography to provide security services for electronic communications and data storage. These services include confidentiality, key management, authentication, and digital signatures. This document specifies the message formats used in OpenPGP.
This server is a member of sks-keyserver.net pgp keyserver pools. The main hkp pool which you should configure your pgp software to use is pool.sks-keyservers.net, or perhaps subset.pool.sks-keyservers.net.
The available pools this server is a memeber of are listed below:
More information may be found on the SKS Keyservers Pools Overview Page.
This service may be withdrawn at any time and without notice to end-users. (Peers will be notified). End-users should use a pool definition above, such as pool.sks-keyservers.net which will alias into an operational pool.
Note: This service is provided free, to the public, in the hopes that it might prove useful. No warranty is provided, nor any offer of continuing service or access.
By using this service, you MUST understand that presence of data in the keyserver (pools) in no way connotes trust. Anyone can generate a key, with any name or email address, and upload it. All security and trust comes from evaluating security at the “object level”, via PGP Web-Of-Trust signatures. This keyserver makes it possible to retrieve keys, looking them up via various indices, but the collection of keys in this public pool is KNOWN to contain malicious and fraudulent keys. It is the common expectation of server operators that users understand this and use software which, like all known common OpenPGP implementations, evaluates trust accordingly. This expectation is so common that it is not normally explicitly stated.
The server will return a list of keys matching the search text. The page will have links for every KeyID, and every bracket-delimited identifier (i.e. <email@example.com>). Clicking on the hypertext link will display an ASCII-armored version of the public key.
The search engine is not the same as that used by the pgp program. It will return information for all keys which contain all the words in the search string. A “word” in this context is a string of consecutive alphabetic characters. For example, in the string firstname.lastname@example.org, the words are user, example, and com.
This means that some keys you might not expect will be returned. If there was a key in the database for Marc Edu <mit.foo.com>, this would be returned for by the above query. If you do not want to see all these extra matches, you can select "Only return exact matches", and only keys containing the specified search string will be returned.
This algorithm does not match partial words in any case. So, if you are used to specifying only part of a long name, this will no longer work.
Currently, hypertext links are only generated for the KeyID and for text found between matching brackets. (It is a common convention to put your e-mail address inside brackets somewhere in the key ID string.)
Submitting a public key allows other people to find and download the public key.
That's it! The keyserver will process your request immediately. If you like, you can check that your key exists using the extract procedure.
Enter ASCII-armored PGP key here:
Notice: When you submit a key to this server, either via the web interface or via HKP, that key will be propagated throughout the pool to various servers. That key will then be stored on each of those servers in addition to this server. Due to the transferring of keys between servers not managed by a central hosts, deleting a key is not possible at this time. If a key were deleted from this server, other servers in the pool will restore the key in order to maintain a complete collection. This is the servers intended behavior.
Below you will find my list of help files and guides for using PGP on your client and building new key servers.
This site is maintained by Jonah Aragon (0xDB49BB255B868219). If you would like to report any problems or bugs, please send an email to the email address listed in my public key.
If you are thankful for this service, please consider donating some funds to the cause. My bitcoin address is
You may also see my profile on keybase.io/jonaharagon.
My Default RSA Key:
pub rsa4096 2018-06-19 [SC] [expires: 2022-06-19] 9BD822880E2784EE5C929CD6DB49BB255B868219 uid [ultimate] Jonah Aragon (Master Key) <email@example.com> uid [ultimate] Jonah Aragon <firstname.lastname@example.org> uid [ultimate] Jonah Aragon <email@example.com> uid [ultimate] Jonah Aragon <firstname.lastname@example.org> uid [ultimate] Jonah Aragon <email@example.com> sub rsa4096 2018-06-19 [E] [expires: 2022-06-19] sub rsa4096 2018-06-20 [S] [expires: 2019-06-20] sub rsa4096 2018-06-20 [A]
A signed copy of this information may be found here. You may validate the file by running the command below:
curl -s https://a.sks.jda.mn/contact.txt |gpg --keyserver-options auto-key-retrieve --auto-key-locate pka --verify