Services
Every service, and where to reach it.
Open the service links below, or use a native Handshake name where one is listed. A website, a mail client and a relay use different entry points. Access requirements and incomplete features are listed with each service.
Directory
Any Handshake sitelive
The gateway serves any delegated name's content to an ordinary browser, under a certificate that covers that hostname: <name>.hns.one. Natively it is hns://<name>. How the mirror works →
PXLSlive
The pixel-canvas game at hns://pxls, played in Wildroot or a compatible client. The public page explains how to open it. Handshake Apps →
Maillive
A mailbox at your name, with JMAP and IMAP and public-key publication over WKD. Open webmail. Not end-to-end encrypted by default. Mail setup →
Fediverse handlespartial
Optional ActivityPub accounts use handles at hns.one, with separate service setup. Native names are mapped to compatible usernames. Handle conventions →
Bluesky (atproto PDS)live
A Bluesky account whose handle is a Handshake name, hosted at pds.hns.one. Invite-gated. Run your own →
Nostr relaylive
A Handshake-aware relay at wss://social.hns.one, with a NIP-05 handle per name. Records →
Private searchpartial
Private metasearch for Handshake identity holders at hsearch.hns.one. Access requires a client and authorization; the root URL is not a public search page. Browser integration is partial.
Oblivious DNSexperimental
An ODoH target at odoh.hns.one, used through a relay run by someone else. Privacy depends on their independence. Setup and limits →
Panellive
The wallet-less control plane where you claim a name and manage its records: app.hns.one. Private identity keys stay on your device. Records →