.gao names, resolved
Type a .gao name and Gao Browser asks Gao ID's public site resolver where it lives. Only a validated https destination is opened; every other answer is shown as a clear card, never a blank page.
Gao Browser is the front door to Gao's products on your phone. .gao names resolve through Gao ID, the ecosystem is one tap away, and Web3 sites connect to the wallet you already use — with no wallet built into the browser. Native on iOS and Android, with the security defaults a browser should have had all along.
.gao names, resolvedType a .gao name and Gao Browser asks Gao ID's public site resolver where it lives. Only a validated https destination is opened; every other answer is shown as a clear card, never a blank page.
The new-tab screen lists Gao's products exactly as the Product catalog publishes them — Gao Domains, Gao Social, GaoKey, Meshii and more. The browser draws the list; it never decides what is on it.
A site sees a standard EIP-1193 provider only after you allow it, per site. Connections run over WalletConnect to the wallet you choose. Gao Browser holds no keys and signs nothing.
It is a browser first. Tabs, history, bookmarks, downloads, uploads and dialogs behave the way a native app should — on both platforms, from the same rules.
Tabs (up to ten), back / forward / reload, history and bookmarks — all restored when you relaunch.
Files are saved, never opened automatically, with safe names; cancelling leaves nothing behind.
Web forms open the system file picker — single or multiple files on Android, the native picker on iOS.
Alerts, confirms and prompts are shown by the browser with the site's origin as the title, so a page cannot impersonate the app.
Offline, DNS, timeout, TLS and unsupported addresses each get their own in-tab surface with Try again, Go back and Home.
A certificate that does not validate is not loaded. There is no “continue anyway”.
Camera, microphone, location and wallet access are asked per site, and only on secure origins.
.gao.eth, .sol, .bnb and .arb names open through public gateways; search goes to DuckDuckGo.
browser.gao.global is where the product lives on the web. It is not the identity service, not the resolver and not a wallet backend — those are Gao ID and the wallet you connect.
.gao name, a tap./wc/icon.png/.well-known/apple-app-site-association/.well-known/assetlinks.json
GET /v2/resolve/site/:nameGET /v2/explorer/sites
Names. .gao resolution is a public read: no account, no wallet, no token. Only an EXTERNAL_HTTPS answer becomes a page; sovereign and default modes are shown as cards.
Catalog. The ecosystem list is remote → cached → compiled fallback and never delays a tab. Catalog entries suggest destinations; the browser decides navigation.
Lanes. A build talks to exactly one lane by name — development or product — compiled in. A release that names no lane is refused, so a Product build cannot drift to a test host.
| iOS | Android |
|---|---|
| Swift · WKWebView · SwiftUI chrome · iOS 15.1 and later | Kotlin · Android WebView · Jetpack Compose chrome · Android 7.0 and later |
| Downloads to the app container, exported through Files | Downloads to the system Downloads collection, no storage permission |
| Native file picker | System document picker, multiple files |
Universal links: browser.gao.global/wc | App links: browser.gao.global/wc |
Same navigation rules, same download policy, same dialog behaviour, same permission model — defined once in shared fixtures and asserted by the iOS, Android and JavaScript test suites.
Gao Browser is currently distributed through internal testing tracks on TestFlight and Google Play. It is not yet a public store release; public availability will be announced here, at browser.gao.global.
The product is built for reliable native browsing today and is prepared for continued hardening and evolution — wallet-session persistence on iOS and removal of the dormant legacy runtime are the next tranches.
Secure, cross-platform access to .gao names, the Gao ecosystem and the wallet you already use.