0trust.name is the public naming face for 0Trust: private mesh TLDs, DNS-over-HTTPS for split resolution, RDAP lookup, and registrar tooling — without inventing a second root for the Internet.
Apps need private product namespaces and full-system resolution for the public Internet — one resolver, clear horizons.
Register non-ICANN extension zones for product and mesh names — .mesh, .social, .tunnel, and open private labels.
Private suffixes answer on the 0Trust plane. Everything else falls through to normal public recursion.
ICANN domain 0trust.name for DoH, RDAP, and NS branding. Not a claim on the global root.
Registry, authoritative answers, and client-friendly endpoints in one stack.
Hierarchical ownership, product zones, and operator tools on the control plane.
Optional cryptographic lineage for zone mutations via SDF grants.
RFC 8484 DoH for browsers and OS secure DNS. One URL for private + public.
Lookup ownership and registration data on the branded RDAP face.
ns.0trust.cloud / services / social mesh for delegated zones and private labels.
Identity, PKI, and naming share 0trust.cloud — one operator model.
Point secure DNS at a 0Trust DoH URL for full-system resolution.
https://dns.0trust.name/dns-query\nhttps://0trust.name/dns-query
https://dns.0trust.cloud/dns-query\nhttps://0trust.cloud/dns-query
RDAP https://rdap.0trust.name\nNS ns.0trust.cloud\n ns.0trust.services