Public part only
The keys are created by you. Only the public certificate belongs to the server, never your password or private key.
CH-J INFRASTRUCTURE / KEYS2Public keys.
Public keys.
Own infrastructure.
Find the right key. Share yours.
Open space for your OpenPGP certificates.
Connecting to server…
—of stored keys
TLSencrypted connection
DEVELOPMENTkeys2.ch-j.de · IPv4 + IPv6
YOUR KEYS, WITHIN REACH
The private key remains with you.Work with public keys
01 / SEARCH
Who do you want to write to?
Enter fingerprint, long Key ID or a verified email address.
Fingerprint: 40 or 64 hex characters Long Key ID: 16 hex characters
Fingerprint always compare with the data obtained from the owner in another way.
02 / PUBLISHING
Your public key belongs outside.
Upload a new certificate or update. Valid signatures, subkeys, and revocations are merged with the saved version.
You will receive a detailed import result via a private link to the address from the certificate. The link is valid for 2 hours.
03 / YOUR EMAIL IDENTITY
Decide what to post.
Request a one-time link to the address contained in the certificate. Both the link and access to the administration are valid for a maximum of 2 hours. Each address is managed separately.
Do you have a private import message identifier?
An administrative link provides access only to its address. Other unverified or hidden addresses are not displayed.
04 / FOR YOUR TOOLS
Open protocol. Easy connection.
Use CH-J Keys v GnuPG or custom application via HTTPS.
Download key via GnuPG
gpg --keyserver hkps://keys2.ch-j.de \
--recv-keys FINGERPRINTGET
/vks/v1/by-fingerprint/{fingerprint}Public keyGET
/vks/v1/by-keyid/{keyid}Long Key IDGET
/vks/v1/by-email/{email}Verified addressPOST
/vks/v1/uploadJSON: {"keytext": "..."}GET
/api/v1/keys/{fingerprint}/infoCertificate detailGET
/api/v1/keys/{fingerprint}/historyTechnical change historyGET
/api/v1/capabilitiesProfiles and AlgorithmsGET
/api/v1/federation/statusRevocation check and worker statusPOST
/api/v1/federation/searchExternal search with email consentGET
/api/v1/statsServer statisticsGET
/healthService statusHKP: /pks/lookup?op=get&search=0xFINGERPRINT · POST /pks/add
The server is accepting OpenPGP V4 a V6 i PQC algorithms by RFC 9980. PQC authentication backend is still experimental. Supports hybrid ML-DSA + Ed25519/Ed448, ML-KEM + X25519/X448 a SLH-DSA-SHAKE. ML-KEM-768 + X25519 can also be accepted as V4 encryption subkey.
LibrePGP V5 is turned on as a separate compatibility profile for RSA, DSA/ElGamal, Ed25519, ECDSA a ECDH. V5 p Ed448 or X448 is not validating this backend yet; support in V6/PQC is standalone. Historical V2/V3 are not accepted. Current server options →
Identity under control
Search by email requires address verification. A verified email does not confirm a person's identity.
A key that is being developed
Updates will preserve earlier revocations and add new valid signatures. Without forwarding to other keyservers.
This instance is created on its own infrastructure CH-J. Detailed messages and address management are protected by email links valid for 2 hours.
Service status