Why ENSNode?

ENSNode is the full-stack ENSv2 development platform — a single, unified API over both ENSv1 and ENSv2, with first-class multichain support and the integration surfaces (React, TypeScript, GraphQL, Postgres) you need to ship.

The Subgraph won’t survive ENSv2

ENSv2 is a fundamental change to ENS’s onchain data model. The legacy ENS Subgraph wasn’t designed for it, and it never will be — single-chain, no resolution, no understanding of the new ENSv2 Namegraph. Apps that stay on the Subgraph will be left behind the moment ENSv2 launches.

🚨 What’s at stake

Indexed ENS data is critical infrastructure for ENS — and the legacy ENS Subgraph is fundamentally unsuitable for ENSv2. When ENSv2 launches, that gap becomes breaking for many of ENS’s most important apps.

Keep ENS apps working 🚨 Much of the ENS ecosystem quietly relies on the Subgraph today, and risks going dark when ENSv2 launches.

Overcome critical limitations of the ENS Subgraph 🚨 Why the Subgraph falls short today, and breaks with ENSv2.

ENSNode is built for ENSv2

ENSNode is built around ENSv2 from the ground up. The same query works against an ENSv1 name today and an ENSv2 name the moment it goes live — with zero downtime or code changes in your app.

✅ Ready the moment ENSv2 launches

Adopt the ENS Omnigraph today and your app is ENSv2-ready before ENSv2 even ships — no rewrite, no scramble, no downtime.

ENSv2 Readiness What you need to do to prepare your app for ENSv2.

How ENSNode delivers

One unified API over ENSv1 + ENSv2 — The ENS Omnigraph is a single GraphQL API that returns a polymorphic, unified view of every ENS Domain — regardless of whether it lives in an ENSv1 Nametree, the ENSv2 Namegraph, on mainnet, or on an L2 subregistry such as base.eth subnames on Base. ENSv1 and ENSv2 coexist after the ENSv2 launch; your code asks for domain(by: { name: "vitalik.eth" }) and gets a typed result, regardless of which protocol version the underlying domain is on.

Multichain by default — ENSNode provides the world’s best indexing coverage for ENS, spanning every chain that matters:

• Mainnet — the canonical ENS root and .eth registrations
• Basenames (.base.eth) on Base
• Lineanames (.linea.eth) on Linea
• 3DNS names (.box, tokenized DNS) on Optimism and Base

No more wiring up a per-chain Subgraph, reconciling overlapping ENS Nametrees, or writing CCIP-Read logic in your app — ENSNode handles forward and reverse resolution, including offchain gateways, server-side.

Full-stack integration surfaces — whatever your stack looks like, there’s an ENSNode integration shaped for it: React, TypeScript, GraphQL, or direct Postgres access.

ENSNode integration options Explore the different ways to integrate with ENSNode based on your stack, runtime, and needs.

Join those already building on ENSNode

A growing set of companies and apps have already moved onto ENSNode and have future-proofed their ENS applications.

• ENS Labs — ENSv2 Explorer, ENSv2 App, ens-test-env.
• EthId Foundation — Grails, ENS Market Bot, Grails CLI.
• Blockful — Anticapture.
• Enscribe
• JustaName — ENSvolution, ENS MCP Service.
• ENS Tools
• ENS Vision
• Namespace — ENS MCP Service, Subpages.
• Lighthouse — ENS Metadata Manager.
• Ethereum Comments Protocol
• FusionENS — Fusion ENS Extension.
• Interface Social — likely reaching our hosted ENSNode indirectly through its Ethereum Comments Protocol integration (not yet fully confirmed).

Indie developers

• Atlas (ENS CLI) — by Steve Dylan.
• Ensemble (ENS CLI) — by estmcmxci.
• Basenames CLI — by estmcmxci.
• Dapp Rank — by Joel Thorstensson.
• Klyra
• pier

Next steps

Quickstart Ship your first Omnigraph query in minutes

ENSv2 Readiness Prepare your app for the ENSv2 launch

Integration Options Pick the integration surface that fits your stack