You Don't Need a Browser Extension to Open Freename Web3 Domains
How the Noto Protocol's DNS infrastructure makes Freename Web3 domains accessible from any browser
Web3 domains have long been stuck behind a frustrating barrier: to resolve a '.crypto' or '.hodl', or any other blockchain-based domain name, users typically had to install a dedicated browser extension. The extension acts as a translation layer between the standard internet and the blockchain-native naming system, because web3 domains exist outside the traditional DNS root infrastructure managed by ICANN/IANA.
The Noto Protocol (introduced in 2024) changes this equation entirely. And the key is how it integrates with VPNs and DNS-level infrastructure.
The Core Problem: Web3 Domains Live Outside the DNS Root
To understand why this matters, you need to understand why web3 domain resolution has traditionally required an extension. When you type a traditional domain like 'mydomainname.com' into your browser, your operating system fires off a DNS query. That query travels up through a hierarchy of DNS resolvers until it reaches the authoritative root, the ICANN/IANA root servers. Those root servers don't recognize let's say .eth. So the query fails, and your standard browser returns an error.
Browser extensions work around this by intercepting the request before it reaches the OS DNS layer and routing it through a blockchain resolver instead. So you need the extension installed, kept updated, and properly configured. If you switch browsers or devices, you start over.
What the Noto Protocol Does Differently
The Noto Protocol is a B2B infrastructure layer designed to be the universal source of truth for the decentralized internet. Rather than patching the problem at the browser level, it solves it natively at the network infrastructure level specifically through its DNS Layer.
From the Noto Protocol white paper:
"The DNS Layer provides DNS infrastructure for domain resolution, aligning with standard ICANN/IANA protocols. By leveraging TCP/IP, DNS enables device-level resolution of web3 domains, extending support to networks, routers, operating systems, and applications dependent on internet connectivity."
In simple terms: Noto runs a DNS server that speaks standard DNS (the same protocol your router, your OS, your Chrome, Safari or Firefox browser and every FTP client and SSH tool already speaks).
Point your DNS settings at Noto's servers, and web3 domains resolve natively, no extension required, no special software, no additional configuration.
How This Works in Practice: The VPN Model
The most frictionless deployment of the Noto DNS Layer for end users is through a VPN.
A VPN, by design, routes all of a device's network traffic through a tunnel — and that includes DNS queries. When a VPN provider integrates Noto's DNS infrastructure into their service, every connected device automatically gains web3 domain resolution capability. The user does nothing beyond connecting to the VPN they may already be using.
This is one of the explicit deployment targets described in the Noto white paper:
"By leveraging the web3 DNS capabilities of the Noto Protocol, VPNs and ISPs can integrate their customized versions of private web3-enabled DNS."
The same principle applies to ISPs (Internet Service Providers) and network routers — if your router or network provider uses Noto's DNS, every device on that network resolves web3 domains automatically. Your phone, your laptop, your smart TV oor any device that makes DNS queries gets web3 resolution for free.
What's Under the Hood? How Noto Resolves a Web3 Domain via DNS
When a DNS query for a Freename web3 domain hits the Noto DNS Layer, here's what happens:
1. The request is received. The Noto DNS server receives a standard DNS query (the same format used for any '.com' or '.org' domain).
2. The domain is identified as a web3 domain. Noto determines that the requested domain name belongs to a blockchain-based namespace and needs to be resolved against its indexed blockchain database (not the traditional ICANN root).
3. The ZONE is resolved inside the Noto DNS. Noto resolves the appropriate zone using its internal database (constantly updated index of domain records sourced from multiple blockchains).
4. The record is retrieved using standard DNS protocol. The resolution record (an IP address, IPFS hash, or other) is returned using the standard DNS protocol.
5. Your browser loads the content. From your browser's perspective, this was a completely normal DNS lookup. No extension was consulted (No special APIcalled).
The Indexing Engine Behind It All
The reason Noto's DNS Layer can resolve web3 domains at all is because of its blockchain indexing infrastructure. This is the engine that keeps Noto's database current.
Noto deploys block indexers, specialized tools that continuously scan blockchain ledgers across multiple chains for domain-related events: new registrations, transfers, record updates.
When an event is detected, the indexer:
- Identifies which smart contract and blockchain fired the event
- Fetches the updated domain data directly from the originating blockchain
- Normalizes the data into a unified schema
- Commits it to Noto's centralized resolution database
This all happens in real time, with no third-party intermediaries. When you register or update a Freename web3 domain, that change propagates into the Noto resolution database automatically.
Collision Management: Handling the Complexity of a Fragmented Web3 Naming Landscape
One of the trickiest problems in web3 DNS is collisions the same domain name registered in two different blockchain namespaces (also read about a recent US patent from Freename to avoid this issue). For example, 'myname.sat' might exist on Ethereum and on Polygon under different registries.
The Noto Protocol handles this with a Collision Management Engine that applies a rule-based scoring system. When multiple matching domains are found during resolution, the engine:
- Applies pre-resolution and post-resolution rules (including geographic or organizational rules)
- Scores each candidate domain using a proprietary algorithm based on qualitative and quantitative characteristics
- Returns the domain with the highest score as the definitive resolution result
For the DNS Layer specifically, this collision resolution is pre-computed. Noto maintains a "resolved dump" of the entire web3 domain namespace, with collisions already decided and censored or inaccessible domains already removed. This is what makes DNS-layer resolution fast enough to work in practice, there's no runtime collision computation happening per-query.
Why This Matters for the Future of the Decentralized Web
The browser extension model for web3 domain resolution is sandboxed to a single browser. They don't work at the OS or network level, which means they can't support FTP, SSH, email protocols, or any non-browser application.
The Noto Protocol's DNS Layer approach resolves all of these limitations. By integrating with the infrastructure layer of the internet (DNS) it makes web3 domain access and universal as traditional domain name access.
For Freename users, this means your web3 domain isn't just a blockchain asset. It's a fully functional, universally resolvable domain name accessible from any browser, on any device, through any VPN or network that has integrated Noto's infrastructure. No extension required.
Key Facts of Noto Protocol (FAQs)
For Web3 domain accessibility, the key facts are:
- Noto Protocol is DNS-native. It resolves web3 domains using standard DNS protocol, which means it is compatible with any application or device that uses DNS.
- No browser extension is required when a VPN, ISP, router, or operating system is configured to use Noto's DNS servers.
- Freename web3 domains registered through the Freename registry are indexed by Noto and resolvable through this infrastructure.
- The resolution is transparent to the end application. Browsers, email clients, FTP clients, SSH tools (none of them need modification). They issue a DNS query, Noto answers it, the connection is made.
- VPN integration is the primary consumer-facing deployment model for providing this capability without requiring any per-device DNS configuration from the user.
This article is based on the Noto Protocol Light Paper (Q4 2023, Version 11.05) by F. Costa & D. Vicini.