---
title: "ENSv2 public beta"
description: "Switch safely between Ethereum mainnet ENSv1 and the Sepolia ENSv2 beta."
canonical: "https://ens.tools/docs/ensv2-public-beta"
section: "Reference"
stability: "beta"
version: "ENSv2 public beta · Sepolia"
verifiedAt: "2026-08-14"
owner: "ENS.Tools Protocol Integration"
---

# ENSv2 public beta

Switch safely between Ethereum mainnet ENSv1 and the Sepolia ENSv2 beta.

## Overview

ENS.Tools can inspect the public ENSv2 beta on Sepolia without changing the default Ethereum mainnet experience. The selected protocol and network are explicit, use separate deployment addresses, and must never be inferred from a name alone.

## What this covers

- Ethereum mainnet ENSv1 remains the default production network.
- The header network control exposes the Sepolia ENSv2 beta as an explicit opt-in.
- Domain detail identifies protocol version, registry, registrar, resolver, ownership chain, and migration state.
- Hierarchical registry and resolver diagnostics show the root-to-leaf chain instead of flattening ENSv2 into one object.
- Mainnet and beta caches, clients, contract addresses, and transaction preparation stay network-scoped.

## Before you run this workflow

### Networks

- Ethereum mainnet ENSv1
- Sepolia ENSv2 public beta

### Prerequisites

- An explicit network selection
- Sepolia test ETH only for beta transactions

### Wallet permissions

- None for reads
- A separately reviewed Sepolia signature for beta state changes

### Expected result

- Network-scoped registry, registrar, resolver, ownership, and migration evidence

### Errors and recovery

- Confirm the protocol badge
- Clear stale network selection by switching explicitly
- Never reuse a beta contract target on mainnet

## How to use it

1. **Choose the beta deliberately.** Use the network control and confirm Sepolia ENSv2 beta is visible before interpreting a result or preparing an action.
2. **Read the protocol badge.** Confirm the page reports the intended chain and protocol version; the same label can have unrelated state across deployments.
3. **Inspect the resolution chain.** Check every parent, registry, resolver, and leaf result. A missing link should remain explicit rather than being replaced by mainnet data.
4. **Switch back for production.** Return to Ethereum mainnet before managing production .eth names or reviewing mainnet marketplace and portfolio evidence.

## Beta assets and state are not mainnet ENS

> Sepolia names, addresses, balances, and transactions have no production ownership or market meaning. Always verify the wallet network and contract target.

## Related guides

- [ENS lookup and domain details](https://ens.tools/docs/lookup-domain-details)
- [Transfers and subnames](https://ens.tools/docs/transfers-and-subnames)
- [Troubleshooting](https://ens.tools/docs/troubleshooting)