What about .sol names?

SNS (**Solana Name Service**) is the Solana equivalent, run by Bonfida. A `.sol` name is an SPL account whose data holds the owner pubkey. Resolving SNS without a wallet library is non-trivial because the name account address is a **PDA** derived from sha256 hashes. We call the public Bonfida resolver gateway to keep the implementation dependency-free.

What is .bnb and SpaceID?

**SpaceID** is a multi-chain naming protocol that runs the `.bnb` namespace on Binance Smart Chain. Its registry / resolver split is **ABI-compatible with ENS**, so the same namehash plus `resolver(node)` plus `addr(node)` call pattern works on BSC. You can also resolve `.arb` on Arbitrum the same way (not enabled in this tool yet).

What about .crypto, .x, .nft, .blockchain?

Those belong to **Unstoppable Domains**. Their resolver layout is different (a single `ProxyReader` contract with per-record keys like `crypto.ETH.address`) and the contracts live on Polygon for new registrations, Ethereum for legacy. Adding them is a straightforward extension - this build focuses on ENS, SNS, and SpaceID as the three biggest by usage.

How does name to address resolution actually work?

For ENS: we compute the **namehash** of the name (EIP-137: recursively keccak256 each label against its parent), then call `resolver(node)` on the **ENS Registry** contract to get the resolver address, then call `addr(node)` on that resolver to get the wallet address. Each step is a single `eth_call` to a public node.

What is reverse resolution?

**Forward** = name to address. **Reverse** = address to name. ENS stores the reverse record at ` .addr.reverse`. We look that up, fetch the `name()` text on its resolver, and show the result. A name is considered "verified" only if the forward resolution of the reverse name produces the same address you started with - otherwise anyone could set a misleading reverse.

Why do some names have an avatar and most do not?

Setting an avatar costs gas (it is a transaction on Ethereum to write a `text` record with key `"avatar"`), so people only do it for names they actively use as identity. The value can be an https URL, an `ipfs://` URI, a base64 data URI, or even an NFT reference like `eip155:1/erc721:0xCONTRACT/TOKEN_ID`. We render the first three directly; NFT references are shown as text since rendering them requires an off-chain NFT API.

What is content hash in ENS?

A **content hash** is how an ENS name points at a website that lives on IPFS, IPNS, or Swarm instead of a centralized server. It is a binary value encoded per **EIP-1577**: a 2-byte namespace prefix (e.g. `0xe301` for IPFS) followed by the multihash. Browsers like Brave or wallets like MetaMask can fetch `vitalik.eth` over IPFS if a content hash is set. Our tool decodes the value into `ipfs://CID` so you can open it in any gateway.

How is this different from regular DNS?

DNS is a hierarchy of **trusted servers** (roots, TLDs, authoritative). ENS lives **on-chain**: there is no DNS server, the mapping is whatever the smart contracts say, and only the wallet that owns the name can change it. The trade-off is **resolution speed** (DNS is sub-50 ms, ENS needs an RPC round-trip, often 200-1500 ms) and **cost** (DNS lookups are free, ENS updates cost gas).

Registry vs resolver - what is the difference?

The **registry** is one contract (`0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e` on mainnet) that records, for every name, who owns it and which resolver answers queries for it. The **resolver** is a separate contract chosen per name; that is where addr / text / contenthash actually live. This split lets ENS upgrade resolver capabilities (CCIP-Read, off-chain resolvers via L2) without changing the registry every name relies on.

YourDevToolsPro

ENS and blockchain domain resolver

Type vitalik.eth, name.sol or name.bnb and see the address, avatar, IPFS content hash, and text records (Twitter, GitHub, URL). No wallet, no sign-in.

LiveRuns in your browser

Type a name like vitalik.eth, name.sol or name.bnb. The server detects the TLD, calls a public JSON-RPC node (Cloudflare Ethereum, Solana mainnet, BSC), and shows the resolved address, content hash, avatar, and text records (Twitter, GitHub, URL, email).

What we do with this query

We do not store names, addresses, or your IP. We only keep a result cache in memory for 10 minutes to avoid hammering public RPC nodes. After that the cache is gone. No database, no logs.

You can query this endpoint up to 30 times per hour from a single IP. The same name is cached for 10 minutes and cached hits do not count against the limit.

What an ENS resolver is

An ENS resolver turns a human-friendly blockchain name like `vitalik.eth` into the wallet address it points to, the same way DNS turns `example.com` into an IP. You type a name, the server reads on-chain records, you get back the address plus avatar, IPFS site, and social links if the owner set them.

This tool supports three name systems out of the box: ENS on Ethereum (`.eth`), SNS on Solana (`.sol`), and SpaceID on BSC (`.bnb`). No wallet, no signature, no extension. The server calls public JSON-RPC nodes (Cloudflare Ethereum, Solana mainnet, BSC public RPC) and ships the parsed result.

How to use it

Type the full name with the TLD: `vitalik.eth`, `bonfida.sol`, `name.bnb`. The TLD picks the right chain automatically.
Click "Resolve" or hit Enter. The first call hits a public RPC, takes 200 to 1500 ms depending on the network.
Read the resolved address at the top, the avatar on the right, and the content hash plus social text records (twitter, github, url, email) below.
A reverse name under "Reverse (address to name)" means the owner set the .reverse record. If it matches the forward name the name is confirmed verified.
Cached results for the same name are returned for 10 minutes and do not count against the per-IP rate limit (30 lookups per hour).
Click any sample chip (`vitalik.eth`, `nick.eth`, `ens.eth`) to fill the input and resolve in one click.

When this is useful

Six practical scenarios where a name resolver beats opening MetaMask:

Verifying a payment recipient before you send anything. You paste `alice.eth`, see the address, compare to what your wallet would show, and you know nobody swapped a character.
Resolving an ENS site / IPFS site from the content hash. ENS lets owners point names at IPFS CIDs (browser support varies). The resolver returns the `ipfs://` URI you can open via a gateway.
Sanity-checking a Twitter or GitHub handle linked from an ENS profile, to confirm the wallet you're looking at really is the same person.
Cross-chain identity check: someone says they own `name.eth` and `name.bnb`. You resolve both and confirm the same address controls them.
Debugging dApp integration: your dApp shows a wrong address. You resolve the same name here against a known-good public RPC and isolate whether the bug is yours or the upstream's.
Auditing a treasury wallet that publishes its name (e.g. `treasury.dao.eth`) so contributors don't have to memorize a 42-character address.

Related tools: crypto address validator (verify the resolved address is well-formed), HD wallet derivation, BIP-39 mnemonic, DNS lookup.

Questions and answers

ENS (Ethereum Name Service) is a set of smart contracts on Ethereum that maps human-readable names like `vitalik.eth` to wallet addresses, content hashes, and text records. It is the closest thing crypto has to DNS. Anyone can register a name for an annual fee. The registry records who owns each name, and a separate resolver contract per name decides how to answer queries (addr, text, contenthash).

Related tools

Crypto address validator

Check whether a BTC, ETH, SOL, LTC or ADA address is valid before you send funds.

HD wallet derivation (BIP32/44)

Turn a 12 or 24-word seed phrase into the first BTC and ETH addresses of any HD wallet.

BIP39 seed phrase generator

Generate a valid 12 or 24-word recovery phrase for any crypto wallet.

DNS Lookup

Check a domain's DNS records (A, AAAA, MX, TXT, CNAME, NS, SOA, CAA), see propagation across 8 public resolvers and surface the server's ASN/ISP, no terminal required.

ENS and blockchain domain resolver

Type vitalik.eth, name.sol or name.bnb and see the address, avatar, IPFS content hash, and text records (Twitter, GitHub, URL). No wallet, no sign-in.

LiveRuns in your browser

ENS and blockchain domain resolver

What we do with this query

We do not store names, addresses, or your IP. We only keep a result cache in memory for 10 minutes to avoid hammering public RPC nodes. After that the cache is gone. No database, no logs.

You can query this endpoint up to 30 times per hour from a single IP. The same name is cached for 10 minutes and cached hits do not count against the limit.

What an ENS resolver is

How to use it

Type the full name with the TLD: `vitalik.eth`, `bonfida.sol`, `name.bnb`. The TLD picks the right chain automatically.
Click "Resolve" or hit Enter. The first call hits a public RPC, takes 200 to 1500 ms depending on the network.
Read the resolved address at the top, the avatar on the right, and the content hash plus social text records (twitter, github, url, email) below.
A reverse name under "Reverse (address to name)" means the owner set the .reverse record. If it matches the forward name the name is confirmed verified.
Cached results for the same name are returned for 10 minutes and do not count against the per-IP rate limit (30 lookups per hour).
Click any sample chip (`vitalik.eth`, `nick.eth`, `ens.eth`) to fill the input and resolve in one click.

When this is useful

Six practical scenarios where a name resolver beats opening MetaMask:

Verifying a payment recipient before you send anything. You paste `alice.eth`, see the address, compare to what your wallet would show, and you know nobody swapped a character.
Resolving an ENS site / IPFS site from the content hash. ENS lets owners point names at IPFS CIDs (browser support varies). The resolver returns the `ipfs://` URI you can open via a gateway.
Sanity-checking a Twitter or GitHub handle linked from an ENS profile, to confirm the wallet you're looking at really is the same person.
Cross-chain identity check: someone says they own `name.eth` and `name.bnb`. You resolve both and confirm the same address controls them.
Debugging dApp integration: your dApp shows a wrong address. You resolve the same name here against a known-good public RPC and isolate whether the bug is yours or the upstream's.
Auditing a treasury wallet that publishes its name (e.g. `treasury.dao.eth`) so contributors don't have to memorize a 42-character address.

Related tools: crypto address validator (verify the resolved address is well-formed), HD wallet derivation, BIP-39 mnemonic, DNS lookup.