The /.well-known/ directory is defined in RFC 8615 as a reserved space for well-known URIs - paths that clients, tools, and protocols can rely on finding at a predictable location without prior negotiation. The full registry of registered well-known URIs is maintained by IANA.

/.well-known/security.txt RFC 9116

Machine-readable vulnerability disclosure policy. PGP clearsigned with the site's Ed25519 key - the signature can be verified by anyone with the public key. Instructs security researchers how to responsibly report issues and what to expect in return.

/.well-known/security-key.asc

PGP public key (ASCII-armored) for security@chrisbmn.com. Used to sign security.txt and to allow encrypted communication with the site's security contact. Also published to keys.openpgp.org for independent retrieval.

/.well-known/chris-key.asc

ASCII-armored OpenPGP public key for chris@chrisbmn.com - the Ed25519 identity and signing key used for Keyoxide identity proofs, commit signing, and encrypted communication. The security@chrisbmn.com key is at security-key.asc. Both keys are also discoverable automatically via WKD.

/.well-known/openpgpkey/ WKD

Web Key Directory - a standard that allows OpenPGP-capable email clients (Thunderbird, GPG, Proton Mail, Fastmail) to automatically discover and import the correct public key without any manual lookup. Two keys are served: the security contact key for security@chrisbmn.com, and the personal Ed25519 key for chris@chrisbmn.com used for Keyoxide identity proofs and commit signing.

/.well-known/chris-pub-smime.cer S/MIME

S/MIME public certificate for chris@chrisbmn.com, issued by Sectigo (Mailbox Validation Strict). A separate system from the OpenPGP key above - trust here comes from Sectigo's CA chain rather than the proofs on the identity page. Publishing it lets anyone send an encrypted email on the first try, without needing a previously-signed message to extract it from.

/robots.txt RFC 9309

Crawler directives for web robots and search engines. Specifies which paths may be indexed. Located at the site root rather than /.well-known/ - the Robots Exclusion Protocol predates the well-known standard by decades.

/humans.txt humanstxt.org

An informal companion to robots.txt - for the humans, not the bots. Documents the people behind the site, the tools used to build it, and credits where they're due. No spec, no enforcement, just a nice thing to have.

/.well-known/did.json W3C DID

W3C Decentralised Identifier document for did:web:chrisbmn.com. Lists verified service endpoints and linked accounts (GitHub, Bluesky, Keybase, Keyoxide, WKD) in a machine-readable format any W3C-compliant DID resolver can parse. Served with Content-Type: application/did+json per the DID Core spec.

/.well-known/keybase.txt

Keybase website proof - a cryptographically signed file generated by Keybase that confirms domain ownership and links this site to the Keybase identity at keybase.io/chrisbmn. Used by Keybase to verify the website claim on the identity profile.

Why does this page exist? Apache is configured with Options -Indexes, which means browsing to a directory without an index file returns a 403. This page is the index - a human-readable alternative to a raw file listing. If you were looking for a specific well-known URI and didn't find it here, check the IANA registry - chrisbmn.com only implements the ones it actually uses.