How to Transfer an Unstoppable Web3 Domain

Transfer an Unstoppable Web3 domain by choosing the correct handover route, confirming the recipient and reviewing the records that may remain attached. A domain transfer changes control of an asset. It is separate from changing the cryptocurrency addresses that the name resolves to.

Identify the route before entering a destination

Unstoppable’s October 2026 Web3 account-push guide uses a recipient wallet address obtained from Account Settings. Its DNS account-push procedure uses a different identifier. A DNS registrar transfer with an authorization code is another product workflow.

Use the instructions for the exact asset and holding arrangement shown in the account. Do not enter a DNS Account ID into a Web3 wallet-address field. If a name is being sold through the marketplace, follow that sale’s handover process instead of sending a separate transfer in response to a buyer’s message.

Prepare the recipient and current records

Ask the intended recipient to obtain the destination through their own official account settings and confirm it through an established communication channel. Compare the full value at the review step. An address copied from an unsolicited offer does not establish recipient identity.

Inspect cryptocurrency destinations, public profile information and website settings before the handover. Decide which should be removed and which the recipient will deliberately replace. Save only the maintenance information needed to verify the transfer.

Unstoppable’s data-retention guidance says marketplace routes remove specified records, while certain direct transfers retain them unless cleared. Its older direct-transfer screen labels differ from the current account-push instructions. Verify actual resulting state rather than treating every route as identical.

Follow the documented Web3 account push

1. Confirm the recipient’s intended wallet address from their Account Settings.
2. In the sending account, open Account Settings, then Advanced.
3. Choose Move Domains Between Wallets, then Push Web3 Domains.
4. Select the current wallet holding the intended names.
5. Select only the domains being handed over and choose Push Domains.
6. Enter and review the complete recipient wallet address.
7. Check every listed name, read the confirmation checkboxes and review the proposed transfer.
8. Use Transfer Domain only when the details match the agreed handover.

The provider says processed names appear in the recipient’s Unstoppable account. These are documentation-based instructions; no domain or wallet was transferred while preparing this guide.

Distinguish the ownership check from the record check

Technical reverse-resolution documentation says reverse information is wiped when ownership changes. That does not prove that every forward address, profile field or website record was cleared. Inspect the relevant records independently.

Have the recipient verify the intended use

The recipient should review the receiving-record checklist, replace destinations as needed and inspect the result in the intended app. Record the token and network context beside the full destination.

A wallet’s NFT display, a receiving lookup and a profile display are different observations. If the asset arrives but a lookup differs, use the troubleshooting guide to find the failing layer. Do not assume that the transfer itself failed simply because an old display is cached.

For sales and organizational handovers

When selling, reconcile the asset transfer with the actual sale status and settlement route. Our selling guide covers listing eligibility, fees and Sales Balance. Sending an asset outside the agreed marketplace process can disconnect delivery from payment.

For a team handover, record who now manages settings, which apps rely on the name and which public materials need updating. Update the maintenance record after both parties verify the result, rather than leaving future operators to infer control from an old screenshot.

For an unresolved transfer, preserve the exact name, destination, route, time and relevant public reference. Use official support without sharing private keys or a recovery phrase. Do not repeat a transfer merely because a notification is delayed.