Gateway Services DNSLink and HTTP Gateways Bridging Web2 Web3

The rapid development of Web3 naming systems such as Ethereum Name Service (ENS), Unstoppable Domains, and other decentralized identity protocols has enabled users to map human-readable names to blockchain addresses, content hashes, and metadata stored on decentralized storage systems like IPFS and Arweave. However, despite these innovations, most end users still access the internet through Web2 browsers that do not natively support blockchain-based protocols or decentralized resolution layers. To bridge this gap, gateway services—particularly DNSLink and HTTP gateways—have emerged as critical infrastructure that enables interoperability between the decentralized Web3 naming stack and the established Web2 ecosystem.

DNSLink is a technology developed by the IPFS community that allows domain owners to associate their DNS records with IPFS content hashes. It functions by inserting a special TXT record into the DNS zone file of a traditional domain, usually in the form _dnslink.example.com, with a value that specifies an IPFS content identifier (CID). This record points to content hosted on the InterPlanetary File System (IPFS), a distributed peer-to-peer file system designed to enable content-addressable storage. When a user visits the domain via an IPFS-aware gateway or browser extension, the gateway queries the DNS record, retrieves the associated CID, and loads the corresponding content from the IPFS network. In doing so, DNSLink enables traditional DNS domains to serve decentralized content while maintaining compatibility with existing Web2 infrastructure.

This bridging function is particularly useful for users or developers who wish to host decentralized websites or documents without requiring their audience to adopt new browser technologies. By using a conventional .com or .org domain with a DNSLink record, projects can publish content that is resilient to censorship and server failures while remaining accessible via any browser. For example, a decentralized application might host its front-end files on IPFS and configure a DNSLink on app.example.com so that users can access the dApp as a normal website. Behind the scenes, the content is fetched from IPFS, but the user interacts with it through a familiar Web2 domain and protocol.

HTTP gateways play a parallel role by providing a standard HTTP interface to access IPFS content. These gateways, such as ipfs.io, cloudflare-ipfs.com, and dweb.link, translate HTTP requests into IPFS node lookups, retrieve the content from the distributed network, and return it over the standard web. Users can access content on IPFS by visiting a URL like https://ipfs.io/ipfs/Qm…, where the CID uniquely identifies the desired file or website. In combination with DNSLink, HTTP gateways enable full Web2 compatibility for decentralized hosting, allowing content to be loaded in any browser without requiring the user to run an IPFS node or install a plugin.

In the context of Web3 naming, these gateway services are essential for content resolution. Many ENS domains, for example, associate a contenthash record with a domain like mydapp.eth, pointing to an IPFS or Arweave hash. However, Web2 browsers do not natively resolve .eth names or understand the contenthash field. Services like eth.link and eth.limo emerged as purpose-built HTTP gateways that resolve ENS names, fetch the associated contenthash from the Ethereum blockchain, and serve the corresponding content via IPFS gateways. When a user visits mydapp.eth.limo, the gateway acts as a resolver and proxy, delivering decentralized content using standard HTTP protocols. This model allows ENS names to function as practical website URLs even before full native browser support for Web3 naming systems is available.

These gateway services are not without challenges. They introduce a degree of centralization into otherwise decentralized systems, as users must trust the operator of the gateway not to censor, tamper with, or log access to content. While the underlying content remains cryptographically verifiable via its CID, the retrieval process is dependent on the reliability and integrity of the gateway operator. Moreover, high usage volumes can strain gateway infrastructure, and the use of centralized DNS and TLS certificates still exposes these services to legal and technical attacks.

To mitigate these concerns, decentralized gateway architectures are being explored. One approach is to distribute gateway services across a federation of nodes, each independently verifying and serving content, with load-balancing and failover mechanisms. Another strategy involves integrating gateway functionality directly into browsers and operating systems, removing the need for intermediaries entirely. Projects like Brave and Opera have taken early steps in this direction by offering native IPFS support, and the continued evolution of standards such as the Decentralized Web Node (DWN) protocol and the InterPlanetary Naming System (IPNS) may further reduce reliance on centralized points of resolution.

Additionally, cross-layer solutions are emerging that combine DNSLink, HTTP gateways, and smart contract-based naming records. For instance, a dApp may use an ENS name that links to an IPFS CID via the contenthash field while also setting up a DNSLink TXT record on a matching DNS domain and configuring HTTP gateway support to route both domains to the same decentralized content. This multi-path architecture ensures resilience, enhances discoverability, and provides fallbacks for users across varying levels of Web3 adoption.

In conclusion, DNSLink and HTTP gateways serve as indispensable bridges between the decentralized promise of Web3 naming and the practical realities of the current web. They enable seamless access to content stored on peer-to-peer networks, allow Web3 domains to function like traditional websites, and provide a foundation for mass adoption while full native support continues to mature. As browser vendors, infrastructure providers, and protocol developers converge on shared standards for naming and resolution, the integration of gateway services will remain a cornerstone of efforts to make Web3 accessible, secure, and usable for a global audience.

The rapid development of Web3 naming systems such as Ethereum Name Service (ENS), Unstoppable Domains, and other decentralized identity protocols has enabled users to map human-readable names to blockchain addresses, content hashes, and metadata stored on decentralized storage systems like IPFS and Arweave. However, despite these innovations, most end users still access the internet through…