Dual-root resolution
Resolve each hostname through both HNS and ICANN, then apply an explicit selection when the two roots differ.
ICANN + Handshake
Explore the webyour way.
Browse ICANN and Handshake sites with authoritative DNSSEC and DANE
verification. For HNS sites that publish proof-anchored
hnsdns=1 authoritative DoH, Shakescape can bypass intercepted
port 53 without trusting a public resolver.
No account. No ads. No tracking by Shakescape. Native wallet actions stay outside web content.
01Resolve both ICANN and HNS naming roots
02Verify authoritative DNSSEC & DANE
03Choose your path
Dual-root resolution
One hostname.
Two naming roots.
For every DNS hostname, Shakescape builds independent HNS and ICANN resolution plans, validates their evidence, and reports the namespace and transport it selected.
DNSSEC and DANE
Validate DNSSEC, TLSA, and DANE evidence locally. Bogus or incomplete security evidence fails closed instead of being treated as trusted.
Local browser and wallet state
Keep history, settings, verified HNS state, and the encrypted wallet on the device. Websites cannot request or approve native wallet actions.
Resolution sequence
From hostname to verified connection.
Shakescape compares HNS and ICANN answers, validates the applicable DNSSEC and TLS policy, and records the selected root, transport, and connection result.
Download Shakescape →
YOU TYPE
A WEB ADDRESS
ROOT AHNS
ROOT BICANN
SHAKESCAPE CHECKS
PROOF · DNSSEC · DANE
SELECTED PLANROOT · TRANSPORT · TLS POLICY
Mobile apps
Shakescape for iOS and Android.
Available for iPhone, iPad, and Android.
MOBILE
iPhone & iPad
Dual-root browser for iPhone and iPad.
- Resolve ICANN and HNS names
- Validate DNSSEC, TLSA, and DANE
- Use native HNS wallet reads and approved actions
- Inspect the selected resolution path
MOBILE
Android
Dual-root browser for Android.
- Resolve ICANN and HNS names
- Validate DNSSEC, TLSA, and DANE
- Use native HNS wallet reads and approved actions
- Inspect the selected resolution path
Local data
No Shakescape account or analytics.
Shakescape has no ads, analytics, accounts, or browsing-history service. Sites receive connection requests, and a selected DNS, relay, or recovery service can observe requested names and timing. The privacy policy documents each network path.
Product details
Resolution, privacy, and source.
Is Shakescape only for Handshake names?
No. Shakescape resolves each hostname through both Handshake and the ICANN naming root, then reports which result it selected.
Does Shakescape send my history to a service?
No. Shakescape has no browsing-history, analytics, or telemetry service. DNS providers and the sites you visit still see the information needed to connect.
Can websites access the Shakescape wallet?
No. Wallet lifecycle, synchronization, send review, name actions, and closed offer exchange remain in native app screens. Shakescape does not expose a website wallet provider.
Is the source available?
Yes. Shakescape's code, releases, and issue trackers are public in the handshake-rs GitHub organization.