# Check an ENS recipient before sending Ethereum

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/check-an-ethereum-name-before-sending/)

Rehearse an ETH transfer to a .eth name and compare the resolved address with the recipient shown in KeySigner before you approve.

## Before you start

**KeySigner computer tools, KeySigner on iPhone and a local Ethereum test network**

- Pair the computer tools with the phone. Fund a test account and set up a plain-ASCII .eth name on a local chain with an ENSv1 registry and a direct Ethereum address record.

## Data and access

- **Shared or checked**. The resolver maps the name to a recipient address. KeySigner shows that resolved address in the approval for review.
- **Check separately**. A dry run only previews the request. Resolve again if the record changes and check execution separately if you send.

## 1. Confirm the expected address

Use your own test record or ask the recipient which address should receive the test transfer. Confirm the full address independently and use the same test network for every check.

**Check.** Your independent record includes the full address and the test network for the recipient.

## 2. Start a dry run

Replace pilot-keysigner.eth with the name you set up on your local chain. If you have several accounts paired, add --from followed by the funded test account's address. The terminal prints the resolved address and asks for approval.

~~~
keysigner-eth send --rpc http://127.0.0.1:8545 \
  --to pilot-keysigner.eth --value 0.001eth --dry-run
~~~

**Check.** The terminal prints a resolved address. Compare all characters with the independently confirmed address before opening the approval.

## 3. Compare the address on your phone

In KeySigner, check the full recipient address against the address you confirmed. Review the test amount, network and fee. This is the address shown by the terminal in the local example. Decline if any field differs. Approving the dry run prints a signed transaction. Keep that output local and discard it after the rehearsal.

~~~
pilot-keysigner.eth resolves to 0x70997970C51812dc3A010C7d01b50e0d17dc79C8
~~~

**Check.** After the dry run the local balance is unchanged. Keep the signed output private and discard it.

## 4. Check the name again when you send

To send on the test chain, start a fresh request without --dry-run. KeySigner resolves the name again after approval, immediately before broadcasting. If the address changed, stop and confirm the recipient again before starting a new request.

**Check.** If the address is unchanged and you send, the receipt’s recipient matches the original record. If resolution changes while you approve, check for the stopped send before retrying.

## Check your result

The terminal and KeySigner show the same verified recipient address. The dry run leaves the recipient's balance unchanged. A send without --dry-run stops if the address changes during approval.

[How to verify your setup](https://keysigner.io/integrations/verify-a-setup/)

## If you get stuck

### The name does not resolve

Check that the selected network has the ENSv1 registry and the exact plain-ASCII .eth name has a direct Ethereum address record. A name that relies on ENSv2, wildcard resolution or an offchain lookup needs a different lookup method. If you can verify the recipient's address independently, enter that address directly.

## Tools in this guide

- [Ethereum](https://keysigner.io/integrations/ethereum/)
  - [Review transaction fields, signatures and fees](https://ethereum.org/developers/docs/transactions/)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#ethereum)

## Setup instructions

- [ENSv1 registry and resolver records](https://docs.ens.domains/registry/ens/)
- [ENS deployments by network](https://docs.ens.domains/learn/deployments/)

[More guides for this task](https://keysigner.io/integrations/tasks/check-key-approval/)
