OWN YOUR DOMAINS. CONTROL YOUR ROUTING. HOST WITHOUT DNS.
RUSH gives Handshake owners true independence: TXT-level redirects, IPFS hosting, and blockchain-backed identity without any centralized DNS provider.
WHAT'S NEW IN v2.1.1
Features that reduce traditional DNS dependencies for Handshake domains
RUSH Redirect for HNS
Set RUSH= in TXT records on your Handshake domains for instant TXT-driven redirects. No separate ICANN DNS hosting is required for the HNS source domain.
IPFS from TXT Records
Add IPFS=<CID> to blockchain‑backed TXT records for your Handshake names. Rush fetches content via the IPFS gateway, giving you a full site instead of a parking page and near‑instant updates when you change the CID.
Faster HNS Resolution
Optimized DNS-over-HTTPS resolution with a prioritized list of HNS resolvers, timeouts, and a 5‑minute in‑browser DNS cache significantly reduces HNS load times in practice.
CORE FEATURES
Decentralized naming with enhanced security and performance
DANE Certificate Verification
Cryptographic validation of TLS certificates using TLSA records fetched over DNS-over-HTTPS, with real-time visual indicators for domains that publish DANE.
Multi-Protocol Support
Native Handshake (HNS) and Ethereum Name Service (ENS) handling, alongside traditional DNS for ICANN domains — including hns:// and ens:// schemes and automatic handling of .eth via gateways.
Privacy First
No built-in telemetry, analytics, or profiling from the browser itself, with HNS and DANE lookups sent over encrypted DNS-over-HTTPS to reduce metadata leakage.
HOW RUSH REDIRECT WORKS
Set up Handshake TXT-based redirection in 3 simple steps
Update Your TXT Record
Add TXT records to your Handshake (HNS) domain:
RUSH=yourdomain.com
Or redirect to any HNS label:
RUSH=you
RUSH=you.guidance
Use IPFS for direct content hosting from blockchain-backed TXT on your HNS name:
IPFS=QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco
RUSH and IPFS TXT records are currently supported for HNS domains; ENS domains are resolved via gateways and ignore these keys.
Browser Resolves via HNS DoH
Rush Browser sends DNS-over-HTTPS queries for TXT, NS, and A records through a prioritized list of Handshake resolvers, with timeouts and caching to keep lookups fast and reliable.
Special thanks to Nathan Woodburn from Australia for building HNSDoh - without his work, the gateway would not be possible.
- ap.hnsdoh.com (primary)
- as.hnsdoh.com (fallback)
- au.hnsdoh.com (fallback)
Results are cached in-browser for 5 minutes to avoid redundant DNS queries.
Instant HTML Redirect
When a matching RUSH= TXT record is found, Rush serves a tiny HTML page that immediately forwards the user to the normalized target URL.
yourhns/ → target.com
In testing, HNS sites typically load in 2–4 seconds versus 10–15 seconds with slower legacy resolver paths, once TXT changes have propagated to the queried HNS resolvers.
Supported TXT Keys
| Key | Usage | Example | Status |
|---|---|---|---|
RUSH= |
Instant redirects for HNS domains | RUSH=example.com |
Active |
IPFS= |
Load content from IPFS CID | IPFS=QmXoypiz... |
Active |
TLSA= |
DANE certificate validation | Auto-handled | Active |
Currently supported for HNS domains. ENS domains are resolved via gateways.
Security & Resolution Architecture
Technical Implementation
Parallel TXT/NS Lookup
TXT and NS DNS-over-HTTPS queries for HNS domains execute in parallel via Promise.all() to minimize latency before redirect and IPFS checks run.
Smart Caching
DNS responses are cached in-memory with a 5-minute TTL to prevent redundant queries and speed up repeat visits.
Prioritized Resolvers
Rush uses an ordered list of HNS DNS-over-HTTPS resolvers with per-resolver timeouts and graceful fallback if one endpoint is slow or unavailable.
Fallback Chain
Resolution flow: HNS DoH → direct HTTPS-to-IP → gateway (hns.to) → human-friendly error pages when all methods fail.
THE RUSH BROWSER REVOLUTION
Rush Browser v2.1.1 pushes decentralized browsing forward with native Handshake (HNS) resolution, TXT‑powered redirects, and IPFS integration designed for real‑world use.
This upgrade lets HNS owners control redirects and IPFS content using TXT records on their Handshake domains, reducing reliance on traditional Web2 DNS hosting.
Why v2.1.1 is a Game Changer
Unlike traditional setups, v2.1.1 can route traffic and content for HNS names directly from blockchain‑backed TXT data in Handshake DNS, so you do not need to run separate ICANN DNS hosting just to make your Handshake domain useful.
This architecture makes Rush Browser v2.1.1 a powerful option for decentralized browsing, combining TXT‑driven HNS behavior, IPFS content delivery, and robust TLS/DANE checks.
Rush Browser is developed and maintained by Rush Team, with a singular vision: to make accessing the decentralized web as secure, intelligent, and low‑dependency as modern technology allows.
WHY RUSH IS DIFFERENT
True decentralization without traditional DNS dependencies
No ICANN Dependency
Handshake domains operate outside traditional DNS authorities
Blockchain-Powered Routing
TXT records on the blockchain control redirects and content
No DNS Hosting Needed
Redirects work without separate ICANN DNS providers
Built-in DANE Verification
Cryptographic certificate validation beyond traditional CAs
Native HNS + ENS Support
Direct resolution of decentralized naming systems
Decentralized-First Architecture
Resolution designed for blockchain domains from the ground up
REAL-WORLD PERFORMANCE
Benchmarks from actual usage testing
Note: Performance varies based on network conditions, resolver latency, and cache state. HNS sites typically load 85% faster than traditional resolution paths.
FEATURE COMPARISON
See how Rush Browser compares on decentralized features
| Feature |
Rush
|
Brave
|
Chrome
|
|---|---|---|---|
| HNS Native Support | |||
| ENS Native Support | |||
| DANE Verification | |||
| TXT-Based Redirect for HNS | |||
| IPFS via Blockchain TXT | |||
| Zero Built-in Telemetry | |||
| DANE / TLSA Integration |
DANE Verification: DNS-based Authentication of Named Entities validates SSL certificates using TLSA records, adding cryptographic checks alongside traditional Certificate Authorities.
TECHNICAL SPECIFICATIONS
Built on modern technologies for performance and security
Framework
Electron / Chromium
DNS Resolution
DNS-over-HTTPS (ap.hnsdoh.com, as.hnsdoh.com, au.hnsdoh.com, and others)
Security
DANE/TLSA validation, CSP handling, HTTPS-only navigation for most flows
Performance
Parallel TXT/NS queries, 5-minute DNS cache, connection timeouts
Protocols
hns://, ens://, http://, https://
Storage
IPFS loading via gateway using IPFS CIDs from blockchain-backed TXT records
Redirect System
TXT-based redirects for HNS domains using RUSH= keys
Handshake Root
Native Handshake DNS resolution via multiple DoH endpoints
DOWNLOAD RUSH BROWSER v2.1.1
Experience decentralized browsing with Handshake TXT redirects and IPFS integration
All downloads are direct from GitHub — no login required. Try the v2.1.1 release today.
Open Web3 for Everyone
Rush Browser is committed to making decentralized web access simple, secure, and available to everyone. By reducing reliance on traditional DNS for Handshake domains and moving redirects into blockchain‑backed TXT records, we're paving the way for a more open and decentralized internet.