NameHash Labs provides hosted instances of ENSNode for developers building on ENS and 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.
Each ENSNode instance is configured for a specific ENS namespace. An ENS namespace identifies which ENS protocol deployment ENSNode will provide data for (ex: mainnet or sepolia).
Each ENS namespace is associated with a particular ENS Root Registry deployment, which may or may not have completed the transition from ENSv1 (only) to ENSv1 + ENSv2 (both v1 and v2 concurrently activated together).
ENSNode supports all of the following ENS namespaces:
mainnet (currently ENSv1 only and not also ENSv2 yet)
sepolia (currently ENSv1 only and not also ENSv2 yet)
sepolia-v2 (now ENSv1 + ENSv2 — An all new deployment of ENS to Sepolia that is already upgraded to ENSv1 + ENSv2 and is independent of the traditional sepolia ENS namespace listed above which currently remains ENSv1 only)
ens-test-env (now ENSv1 + ENSv2 — A deployment of ENSv1 + 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). Teams working on the core ENS protocol and infrastructure such as ENS Labs and NameHash Labs are using this ENSNode configuration to support ENSv2 development.
Each ENSNode instance is also configured for a specific set of activated ENSNode plugins.
The activated plugins determine the specific indexed data model and data records ENSIndexer will produce in ENSDb and therefore which APIs and data records ENSApi will make available to query.
These instances are associated with an ENS namespace that has upgraded to ENSv1 + ENSv2 and demonstrate the latest support in ENSNode for ENSv1 and ENSv2 being concurrently activated together.
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
Available. Accelerate most of your ENS protocol resolution requests while maintaining full compliance with all ENS protocol standards and best practices.
ENS Subgraph API
API-level Subgraph Compatibility. This ENSNode instance has a fully backwards compatible ENS Subgraph GraphQL API. However, additional plugins have been activated which index a superset of data into the subgraph data model in ENSDb (including Basenames, Lineanames, and 3DNS). This superset of indexed data means that the data returned for some ENS Subgraph API queries may be different. **NOTE:** As soon as ENSv2 launches the ENS Subgraph will no longer return correct data. Transition your apps now to the new ENS Omnigraph API to be ENSv2 ready.
These instances are associated with an ENS namespace that has NOT upgraded to support ENSv1 and ENSv2 concurrently yet and are still operating exclusively 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.
These ENSNode instances do not constrain themselves to exclusively activating the subgraph plugin. They activate additional plugins such as the unigraph plugin to demonstrate the latest capabilities of ENSNode including the new ENS Omnigraph API.
Activated. Demonstrates the ENS Omnigraph's ability to support ENSv1 only before ENSv2 launches and both ENSv1 and ENSv2 are concurrently active. Until ENSv2 launches on this namespace, only ENSv1 domains will be available. As soon as ENSv2 launches on this namespace both ENSv1 and ENSv2 domains will be available.
ENS Protocol Acceleration
Available. Accelerate most of your ENS protocol resolution requests while maintaining full compliance with all ENS protocol standards and best practices.
ENS Subgraph API
API-level Subgraph Compatibility. This ENSNode instance has a fully backwards compatible ENS Subgraph GraphQL API. However, additional plugins have been activated which index a superset of data into the subgraph data model in ENSDb (including Basenames, Lineanames, and 3DNS). This superset of indexed data means that the data returned for some ENS Subgraph API queries may be different. **NOTE:** As soon as ENSv2 launches the ENS Subgraph will no longer return correct data. Transition your apps now to the new ENS Omnigraph API to be ENSv2 ready.
Activated. Demonstrates the ENS Omnigraph's ability to support ENSv1 only before ENSv2 launches and both ENSv1 and ENSv2 are concurrently active. Until ENSv2 launches on this namespace, only ENSv1 domains will be available. As soon as ENSv2 launches on this namespace both ENSv1 and ENSv2 domains will be available.
ENS Protocol Acceleration
Available. Accelerate most of your ENS protocol resolution requests while maintaining full compliance with all ENS protocol standards and best practices.
ENS Subgraph API
API-level Subgraph Compatibility. This ENSNode instance has a fully backwards compatible ENS Subgraph GraphQL API. However, additional plugins have been activated which index a superset of data into the subgraph data model in ENSDb (including Basenames, Lineanames, and 3DNS). This superset of indexed data means that the data returned for some ENS Subgraph API queries may be different. **NOTE:** As soon as ENSv2 launches the ENS Subgraph will no longer return correct data. Transition your apps now to the new ENS Omnigraph API to be ENSv2 ready.
These ENSNode instances focus on maximizing backwards compatibility with the ENS Subgraph. Therefore they exclusively activate the subgraph plugin and no others.
Not activated. This ENSNode instance optimizes for maximum compatibility with the ENS Subgraph. Therefore it exclusively activates the subgraph plugin and does not activate the unigraph plugin that the ENS Omnigraph API requires.
ENS Protocol Acceleration
Unavailable. Your ENS protocol resolution requests will be serviced in full compliance with all ENS protocol standards and best practices. However, this ENSNode instance did not activate the protocol-acceleration plugin and therefore ENS resolution requests will be serviced accurately but without acceleration.
ENS Subgraph API
Full Subgraph Compatibility. This ENSNode instance has a fully backwards compatible ENS Subgraph GraphQL API at both the API-level and the data-level. We have exhaustively tested and verified that every data record returned by this ENSNode instance's ENS Subgraph API is byte-for-byte identical with The Graph's ENS Subgraph API. **NOTE:** As soon as ENSv2 launches the ENS Subgraph will no longer return correct data. Transition your apps now to the new ENS Omnigraph API to be ENSv2 ready.
Not activated. This ENSNode instance optimizes for maximum compatibility with the ENS Subgraph. Therefore it exclusively activates the subgraph plugin and does not activate the unigraph plugin that the ENS Omnigraph API requires.
ENS Protocol Acceleration
Unavailable. Your ENS protocol resolution requests will be serviced in full compliance with all ENS protocol standards and best practices. However, this ENSNode instance did not activate the protocol-acceleration plugin and therefore ENS resolution requests will be serviced accurately but without acceleration.
ENS Subgraph API
Full Subgraph Compatibility. This ENSNode instance has a fully backwards compatible ENS Subgraph GraphQL API at both the API-level and the data-level. We have exhaustively tested and verified that every data record returned by this ENSNode instance's ENS Subgraph API is byte-for-byte identical with The Graph's ENS Subgraph API. **NOTE:** As soon as ENSv2 launches the ENS Subgraph will no longer return correct data. Transition your apps now to the new ENS Omnigraph API to be ENSv2 ready.
