Subdomains

Get a list of subdomains for the eth domain, including their Domain type (ENSv1Domain vs ENSv2Domain) — a single query spanning both protocol versions. See Connect for setup.

SQL

What is an `ensindexer_0`?

It is the name of an ENSDb Writer Schema, which is a database schema within an ENSDb instance, used to store indexed ENS data from a given ENSDb Writer instance. We use ensindexer_0 as the ENSDb Writer Schema Name in examples on this page, but your ENSDb Writer instance may be configured to use a different schema name. Make sure to replace ensindexer_0 with the actual schema name used by your ENSDb Writer instance when querying the ENSDb instance directly. For example, ENSIndexer allows configuring its own ENSDb Writer Schema Name with the ENSINDEXER_SCHEMA_NAME environment variable.

SQL

WITH parent AS (
  SELECT subregistry_id
  FROM "ensindexer_0".domains
  WHERE canonical_name = 'ens.eth'
  AND canonical = true
)
SELECT
  d.type,
  d.canonical_name,
  d.canonical_node,
  d.owner_id,
  d.id as domain_id
FROM "ensindexer_0".domains d
JOIN parent p ON d.registry_id = p.subregistry_id
WHERE d.canonical = true
ORDER BY d.__canonical_name_prefix ASC
LIMIT 10;

Output

#	type	canonical_name	canonical_node	owner_id	domain_id
1	ENSv1Domain	app.ens.eth	0x50a74dcf107973068dfc00db69ecf98b49d52f5361cb4db5feb740fc9f4f74d1	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x50a74dcf107973068dfc00db69ecf98b49d52f5361cb4db5feb740fc9f4f74d1
2	ENSv1Domain	attestations.ens.eth	0x9e5c7a2f2ab8b565c6d2c4851a73decb53d1f6a23c97a2b5b66f21d8ace1bbd5	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x9e5c7a2f2ab8b565c6d2c4851a73decb53d1f6a23c97a2b5b66f21d8ace1bbd5
3	ENSv1Domain	coldwallet.ens.eth	0xc867d2bd24b8a88c7d5d416dfab28fec6858b5a86f3a1c94faeab450c34023f6	0x690f0581ececcf8389c223170778cd9d029606f2	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0xc867d2bd24b8a88c7d5d416dfab28fec6858b5a86f3a1c94faeab450c34023f6
4	ENSv1Domain	controller.ens.eth	0xceecb75ad42a60ea38b777bf842c14af3303219e2722a192ddeac19faa7fbb1c	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0xceecb75ad42a60ea38b777bf842c14af3303219e2722a192ddeac19faa7fbb1c
5	ENSv1Domain	design.ens.eth	0xe55e79685b24c7b16542f3c613a8899986ace5e2e08b3c9444ce70d81d49bcd2	0x690f0581ececcf8389c223170778cd9d029606f2	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0xe55e79685b24c7b16542f3c613a8899986ace5e2e08b3c9444ce70d81d49bcd2
6	ENSv1Domain	dnsname.ens.eth	0x250712f87e86832e8bed775a563920aed01b926d9d21950e363a042af40ad2b5	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x250712f87e86832e8bed775a563920aed01b926d9d21950e363a042af40ad2b5
7	ENSv1Domain	dnsregistrar.ens.eth	0x3124e45545d17d9fda8e24a7a09f111a0802ea26ce6b1f14c75c832442deb65d	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x3124e45545d17d9fda8e24a7a09f111a0802ea26ce6b1f14c75c832442deb65d
8	ENSv1Domain	dnssec.ens.eth	0x287e74fe5b4463a7e8b8d4c4cccae51a8ab397df053bc829c6a4e26963c7ce2b	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x287e74fe5b4463a7e8b8d4c4cccae51a8ab397df053bc829c6a4e26963c7ce2b
9	ENSv1Domain	docs.ens.eth	0x08625bbdd59ae52e6a0e3f8f2bd6213e60ad35276510c83d117c7a2a68bc65c0	0xee9eeaab0bb7d9b969d701f6f8212609edea252e	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x08625bbdd59ae52e6a0e3f8f2bd6213e60ad35276510c83d117c7a2a68bc65c0
10	ENSv1Domain	ecosystem.ens.eth	0x44ea949951a1e21fe141e9979ef9af0cef3df0ac50004c19309df97fef6c9023	0x690f0581ececcf8389c223170778cd9d029606f2	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x44ea949951a1e21fe141e9979ef9af0cef3df0ac50004c19309df97fef6c9023

Output matches a point in time snapshot of ENSDb result from our Alpha Hosted ENSNode instance. Live output depends on the configuration of your ENSNode instance and also changes that may have happened in ENS since this point in time snapshot example response was captured.

ensdb-sdk (TypeScript)

Connect with ensdb-sdk

See how to connect to ENSDb and get access to the ensDb query builder and ensIndexerSchema schema definition in the Connect example if you haven't already.

TypeScript

import { and, eq, inArray, asc } from "drizzle-orm";

const name = "ens.eth";
const limit = 10;

// Two-step:
// 1) find parent domains
// 2) query children by each parent domain's subregistryId.
const parentDomains = await ensDb
  .select({ subregistryId: ensIndexerSchema.domain.subregistryId })
  .from(ensIndexerSchema.domain)
  .where(
    and(
      eq(ensIndexerSchema.domain.canonicalName, name),
      eq(ensIndexerSchema.domain.canonical, true),
    ),
  );

if (parentDomains.length > 0) {
  const subdomains = await ensDb
    .select({
      type: ensIndexerSchema.domain.type,
      canonicalName: ensIndexerSchema.domain.canonicalName,
      canonicalNode: ensIndexerSchema.domain.canonicalNode,
      ownerId: ensIndexerSchema.domain.ownerId,
      domainId: ensIndexerSchema.domain.id,
    })
    .from(ensIndexerSchema.domain)
    .where(
      and(
        inArray(
          ensIndexerSchema.domain.registryId,
          parentDomains.map((d) => d.subregistryId),
        ),
        eq(ensIndexerSchema.domain.canonical, true),
      ),
    )
    .orderBy(asc(ensIndexerSchema.domain.__canonicalNamePrefix))
    .limit(limit);

  console.log(subdomains);
}

Output

#	type	canonicalName	canonicalNode	ownerId	domainId
1	ENSv1Domain	app.ens.eth	0x50a74dcf107973068dfc00db69ecf98b49d52f5361cb4db5feb740fc9f4f74d1	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x50a74dcf107973068dfc00db69ecf98b49d52f5361cb4db5feb740fc9f4f74d1
2	ENSv1Domain	attestations.ens.eth	0x9e5c7a2f2ab8b565c6d2c4851a73decb53d1f6a23c97a2b5b66f21d8ace1bbd5	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x9e5c7a2f2ab8b565c6d2c4851a73decb53d1f6a23c97a2b5b66f21d8ace1bbd5
3	ENSv1Domain	coldwallet.ens.eth	0xc867d2bd24b8a88c7d5d416dfab28fec6858b5a86f3a1c94faeab450c34023f6	0x690f0581ececcf8389c223170778cd9d029606f2	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0xc867d2bd24b8a88c7d5d416dfab28fec6858b5a86f3a1c94faeab450c34023f6
4	ENSv1Domain	controller.ens.eth	0xceecb75ad42a60ea38b777bf842c14af3303219e2722a192ddeac19faa7fbb1c	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0xceecb75ad42a60ea38b777bf842c14af3303219e2722a192ddeac19faa7fbb1c
5	ENSv1Domain	design.ens.eth	0xe55e79685b24c7b16542f3c613a8899986ace5e2e08b3c9444ce70d81d49bcd2	0x690f0581ececcf8389c223170778cd9d029606f2	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0xe55e79685b24c7b16542f3c613a8899986ace5e2e08b3c9444ce70d81d49bcd2
6	ENSv1Domain	dnsname.ens.eth	0x250712f87e86832e8bed775a563920aed01b926d9d21950e363a042af40ad2b5	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x250712f87e86832e8bed775a563920aed01b926d9d21950e363a042af40ad2b5
7	ENSv1Domain	dnsregistrar.ens.eth	0x3124e45545d17d9fda8e24a7a09f111a0802ea26ce6b1f14c75c832442deb65d	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x3124e45545d17d9fda8e24a7a09f111a0802ea26ce6b1f14c75c832442deb65d
8	ENSv1Domain	dnssec.ens.eth	0x287e74fe5b4463a7e8b8d4c4cccae51a8ab397df053bc829c6a4e26963c7ce2b	0xb6e040c9ecaae172a89bd561c5f73e1c48d28cd9	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x287e74fe5b4463a7e8b8d4c4cccae51a8ab397df053bc829c6a4e26963c7ce2b
9	ENSv1Domain	docs.ens.eth	0x08625bbdd59ae52e6a0e3f8f2bd6213e60ad35276510c83d117c7a2a68bc65c0	0xee9eeaab0bb7d9b969d701f6f8212609edea252e	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x08625bbdd59ae52e6a0e3f8f2bd6213e60ad35276510c83d117c7a2a68bc65c0
10	ENSv1Domain	ecosystem.ens.eth	0x44ea949951a1e21fe141e9979ef9af0cef3df0ac50004c19309df97fef6c9023	0x690f0581ececcf8389c223170778cd9d029606f2	1-0x00000000000c2e074ec69a0dfb2997ba6c7d2e1e-0x44ea949951a1e21fe141e9979ef9af0cef3df0ac50004c19309df97fef6c9023

Output matches a point in time snapshot of ENSDb result from our Alpha Hosted ENSNode instance. Live output depends on the configuration of your ENSNode instance and also changes that may have happened in ENS since this point in time snapshot example response was captured.