Hosted ENSNode Instances

Hosted Instances

NameHash Labs provides freely available hosted instances for ENS developers looking to get started quickly.

These instances are currently provided free of charge with no API key required, have no rate limiting, and are maintained and monitored by the NameHash Labs team.

Version compatibility with hosted instances

Our hosted ENSNode instances currently run ENSNode v1.13. If you are querying them from your own app, you must use enssdk@1.13.1 (and enskit@1.13.1 when using React). The latest published versions (1.14.0+) contain breaking changes in the Omnigraph API data model not yet deployed to our hosted infrastructure. Use these exact install commands:

npm install enssdk@1.13.1
# or, for React apps:
npm install enskit@1.13.1 enssdk@1.13.1

This notice will be removed once the hosted instances are upgraded.

ENS Namespaces

Each ENSNode hosted instance is configured for a specific ENS namespace and activated ENSNode plugins. The ENS namespace identifies which ENS protocol deployment will be indexed by ENSNode (ex: mainnet or sepolia). The activated plugins determine the specific indexed data model ENSIndexer will produce in ENSDb and therefore which APIs ENSApi will make available to query.

Each ENS namespace is associated with a particular ENS Root Registry deployment, which may or may not have completed the transition from ENSv1 to ENSv2. Currently, ENSNode supports the following ENS namespaces:

• mainnet (ENSv1)
• sepolia (ENSv1)
• sepolia-v2 (ENSv1+ENSv2 — An independent deployment of ENS to Sepolia that is already upgraded to ENSv2)
• ens-test-env (ENSv1+ENSv2 — A deployment of ENSv2 to a local Anvil chain for development and testing. For details see https://github.com/ensdomains/ens-test-env and https://github.com/ensdomains/contracts-v2)

More details about ENS namespaces can be found inside ENSNode’s datasources package.

ENSv2 Instances

These instances are associated with an ENS namespace that has upgraded to ENSv2 and demonstrate the latest ENSv2 support in ENSNode.

ENSNode ‘v2 Sepolia’

v2 Sepolia

The sepolia-v2 namespace is undergoing active development by the ENS Labs team who is continuing to release updated ENSv2 contracts. It should be considered experimental.

Hosted at	https://api.v2-sepolia.ensnode.io Connect with ENSAdmin
ENSNode Version	v1.13.1
ENS Namespace	sepolia-v2
ENS Deployments	(ENSv1+ENSv2)
Active Plugins	subgraph, unigraph, protocol-acceleration
APIs	ENS Omnigraph API Powered by a polymorphic GraphQL API with native support for both ENSv1 and ENSv2. When ENSv2 launches in Summer 2026, data from two protocol versions coexist — and the ENS Omnigraph API will keep your app working against both, at the same time, with no code changes. Domains from ENSv1 and ENSv2 are indexed concurrently and exposed through a unified schema. ENS Protocol Acceleration Radically accelerated resolution of most ENS queries. ENSNode’s architecture unlocks near-instant bulk resolution of live ENS records, including name resolution configurations that span across multiple chains. ENS Subgraph API API-level Subgraph Compatibility, where GraphQL APIs are equivalent but a superset of data is being queried and therefore the data returned for some queries may be different.

ENSv1 Instances

These instances are associated with an ENS namespace that has NOT upgraded to ENSv2 yet and are still operating under ENSv1. These demonstrate how the ENS Omnigraph API, enssdk, enskit, and the full stack of ENSNode services provide support to developers to become ENSv2 ready even before ENSv2 launches.

Alpha-style Deployments

These ENSNode instances focus on pushing the boundaries of what’s possible with ENSNode.

ENSNode ‘Alpha’

Hosted at	https://api.alpha.ensnode.io Connect with ENSAdmin
ENSNode Version	v1.13.1
ENS Namespace	mainnet
ENS Deployments	(ENSv1 only)
Active Plugins	subgraph, basenames, lineanames, threedns, unigraph, protocol-acceleration, registrars, tokenscope
APIs	ENS Omnigraph API Powered by a polymorphic GraphQL API with native support for both ENSv1 and ENSv2, though data is exclusively sourced from ENSv1. ENSNode can be used as a future-proof integration point for your app to smoothly transition to ENSv2 when you need. ENS Protocol Acceleration Radically accelerated resolution of most ENS queries. ENSNode’s architecture unlocks near-instant bulk resolution of live ENS records, including name resolution configurations that span across multiple chains. ENS Subgraph API API-level Subgraph Compatibility, where GraphQL APIs are equivalent but a superset of data is being queried and therefore the data returned for some queries may be different.

ENSNode ‘Alpha-Sepolia’

Hosted at	https://api.alpha-sepolia.ensnode.io Connect with ENSAdmin
ENSNode Version	v1.13.1
ENS Namespace	sepolia
ENS Deployments	(ENSv1 only)
Active Plugins	subgraph, basenames, lineanames, registrars, unigraph, protocol-acceleration
APIs	ENS Omnigraph API Powered by a polymorphic GraphQL API with native support for both ENSv1 and ENSv2, though data is exclusively sourced from ENSv1. ENSNode can be used as a future-proof integration point for your app to smoothly transition to ENSv2 when you need. ENS Protocol Acceleration Radically accelerated resolution of most ENS queries. ENSNode’s architecture unlocks near-instant bulk resolution of live ENS records, including name resolution configurations that span across multiple chains. ENS Subgraph API API-level Subgraph Compatibility, where GraphQL APIs are equivalent but a superset of data is being queried and therefore the data returned for some queries may be different.

Subgraph-style Deployments

These ENSNode instances focus on maximizing backwards compatibility with the ENS Subgraph.

ENSNode ‘Mainnet’

Hosted at	https://api.mainnet.ensnode.io Connect with ENSAdmin
ENSNode Version	v1.13.1
ENS Namespace	mainnet
ENS Deployments	(ENSv1 only)
Active Plugins	subgraph
APIs	ENS Omnigraph API Not activated due to this instance's focus on maximum compatibility with the ENS Subgraph. ENS Protocol Acceleration Not activated due to this instance's focus on maximum compatibility with the ENS Subgraph. ENS Subgraph API Full Subgraph Compatibility at both the API-level and the data-level. ENSNode can be used as a drop-in replacement for the ENS Subgraph, with guarantees that all data returned by ENSNode will be fully aligned with the ENS Subgraph.

ENSNode ‘Sepolia’

Hosted at	https://api.sepolia.ensnode.io Connect with ENSAdmin
ENSNode Version	v1.13.1
ENS Namespace	sepolia
ENS Deployments	(ENSv1 only)
Active Plugins	subgraph
APIs	ENS Omnigraph API Not activated due to this instance's focus on maximum compatibility with the ENS Subgraph. ENS Protocol Acceleration Not activated due to this instance's focus on maximum compatibility with the ENS Subgraph. ENS Subgraph API Full Subgraph Compatibility at both the API-level and the data-level. ENSNode can be used as a drop-in replacement for the ENS Subgraph, with guarantees that all data returned by ENSNode will be fully aligned with the ENS Subgraph.

Start building

Pick an instance above, then jump into the Quickstart for integration options to start making use of it.

ENSNode Quickstart Wire enskit, enssdk, or the ENS Omnigraph API up to a hosted instance in a few minutes.