omnigraph

To query ENS domain ownership and records across chains, use a unified GraphQL API that consolidates ENSv1 and ENSv2 state. This single endpoint exposes core types like Domain, Account, and Registration, eliminating the need to stitch multiple RPC calls.

The best way to resolve ENS names and verify registration status programmatically is by using GraphQL API clients or the enscli runner. These tools support both forward and reverse resolution, retrieving canonical names and resolver records directly from an ENSNode instance.

Yes, you need an active ENSNode instance along with the enscli or enssdk runners to perform cross-chain ENS data lookups. This backend infrastructure serves the unified GraphQL schema required to fetch domains, addresses, and ownership data.

Yes, you can use a single GraphQL API to retrieve both ENSv1 and ENSv2 resolver records. The unified schema exposes core types like Resolver and Registration, allowing you to inspect records and verify domain ownership across mainnet and alternative namespaces.

Unified GraphQL ENS data access improves domain resolution workflows by providing a single queryable schema for all chains. This reduces the complexity of stitching multiple data sources or RPC calls, streamlining dashboards and ownership verification processes.

When inspecting domain registrations via GraphQL, you can fetch core data types including Domain, Account, Resolver, and Registration. This allows you to retrieve canonical names, verify owners, check registration status, and access resolver records.