This is sks.spodhuis.org
, a mostly private keyserver providing HKP access to keys
on ports 11371, 80 and 443. Note that while port 11371 does not require a Host:
HTTP header, ports 80 and
443 do, and port 443 requires TLS SNI
to serve the correct certificate.
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, such as keys.gnupg.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.
For administrative questions, contact any of the non-revoked email addresses in my PGP key.
(Use verbose index to see which are revoked.) Or use keyserver as the left-hand-side,
in the domain spodhuis.org.
Note that this host peers as sks-peer.spodhuis.org and SKS-protocol
peering requests are often accepted; I'm willing to set up email-based exchange for non-SKS speakers.