CryptDNS should be the convenient choice, not an unavoidable dependency.
Run as much or as little as you need. These are product directions, not a menu of live plans.
One internet.
More possibilities.
Open-source infrastructure connecting private DNS with decentralized naming, identity, and discovery.
Early-stage. The services described here are directions, not a live resolver.
You should not have to choose between convenience, privacy, and control.
The internet you know and the networks still arriving can share one way in.
CryptDNS is being built so encrypted, policy-aware DNS can sit beside ENS, Handshake, ArNS, and identity discovery. Adopt new capabilities without learning every protocol first. Existing services stay useful. New names get a path. Nobody has to pick a side of the internet and stay there.
Different names take different paths. What follows is one map, not one protocol.
A name is the start of a path, not the destination.
Watch the helix open into separate routes. Then pick an illustrative name type. Changing DNS alone does not make every decentralized name a normal HTTPS site.
Illustrative: example.com is resolved through DNS to an HTTPS endpoint.
Conventional domain
- DNS resolution finds the endpoint for a familiar domain.
- An HTTPS endpoint still needs its server and certificate.
ENS name
- ENS resolution reads the name and its records.
- The resource is interpreted.
- An appropriate content-access path follows. That is not always ordinary HTTPS.
Handshake name
- Handshake root resolution uses a different root.
- DNS delegation still applies.
- The endpoint has its own authentication requirements.
ArNS name
- Name-to-content resolution returns a content reference.
- A content gateway is the access path.
Identity and agent discovery
- A Nostr NIP-05 identifier or an agent/MCP discovery record is one possible document.
- What comes back is a public key or an advertised endpoint for a relevant client.
These are designed examples with simulated results. Nothing on this page queries a blockchain, a public resolver, or a third-party API.
Run it yourself
Self-hosted software with local caching, policies, and optional on-site statistics. A direction, not a ready-to-install claim.
Use CryptDNS-operated infrastructure
A managed path for people who want convenience. Availability has not been announced.
Get professional help
Deployment, management, and commercial support are possible later offerings for teams, MSPs, and ISPs.
Replaceable upstreams stay in the design. Convenience is optional. Control travels with you.
Specific commitments. Honest limits.
Principles for the work, not a certification, an audit, or a claim that every capability already exists.
Early-stage project. This site describes intended direction, not an available resolver.
- Open-source software. Inspect what is published. This repository currently hosts the public website.
- Privacy-preserving defaults. Filtering, when it exists, should be explicit and user-selectable.
- Replaceable upstreams. Provider choice stays visible. One gatekeeper should not become mandatory.
- Explained trust boundaries. What resolves a name, what serves content, and any narrow safeguards against exploitation or malicious abuse should be stated in the open.
Help build an internet with more choice and fewer gatekeepers.
This is the project overview. Status, source, documentation, and contribution paths live here. There is no waitlist and no resolver to join.
- Current status Early-stage public website and positioning. No production service, uptime figure, or audit is claimed.
- Source code View source on GitHub
- Documentation Not published yet. This page will link it when it exists.
- Contribute Open an issue Ask a question or suggest a path in. Business inquiries can use the same issues list until a dedicated channel exists.