Web3 Domain Scams: An ENS Safety Checklist
Spot Web3 domain scams with checks for fake renewals, lookalike names, wallet approvals, buyer messages and official support.
Web3 domain scams usually exploit a rushed wallet approval, a misleading name or a fake support request. A useful safety routine checks the site, exact identifier, intended action and full destination before any signature. The examples here focus on ENS, with checks you can also apply when using other naming services.
Open the service independently and keep a written description of the action you intend to perform.
- 01Verify the site and exact name
- 02Read the actual wallet request
- 03Confirm the resulting state independently
Match the message to an independently checked fact
| What arrives | What to check yourself |
|---|---|
| An urgent renewal warning | Open the official app independently and inspect the real expiry. |
| An upgrade or migration demand | Read the provider’s current announcement and status through its own site. |
| A request to verify your wallet | Identify the exact action; never enter a recovery phrase into a support page. |
| A buyer’s error screenshot | Open the marketplace yourself and inspect the real listing or offer. |
| An unfamiliar name or NFT | Do not treat an unsolicited asset as permission to interact with its links. |
ENS’s current safety guidance identifies fake renewals, upgrade messages, approval traps and phrase phishing. At our review, ENSv2 remained unavailable on Mainnet, with no confirmed launch date. A message claiming an urgent mandatory upgrade is not evidence that those conditions changed.
Check the complete name, not just its appearance
Different characters can look similar while representing different names and destinations. ENS’s lookalike guidance recommends typing the intended name independently in the official app and comparing the owner and receiving address with the information you expected.
For a suspicious string, character inspection can reveal mixed scripts or invisible characters. An unusual-character warning is a reason to inspect the identifier, rather than proof of fraud by itself. Legitimate names can use non-Latin writing and emoji. Verify the particular string and identity instead of relying on its visual familiarity.
For a name you plan to buy, use the naming checklist before checking out. For a payment instruction, confirm the full destination through a channel you already trust.
Read what the wallet is authorizing
Describe the expected action before opening the wallet: registration, record edit, ownership transfer or marketplace listing. Compare that description with the request. An unexpected asset transfer or broad approval needs investigation before you sign.
A connection prompt, a message signature and an onchain transaction have different purposes. Do not treat any of them as harmless simply because no payment amount is displayed. If a site says it is updating a profile but asks to move an asset, the mismatch is a reason to stop.
Know the fake-buyer pattern
OpenSea warns about supposed buyers who send error screenshots and ask sellers to pay to fix a sale. Its selling guidance says it will not ask you to send funds to enable selling or resolve a transaction failure. Verify any offer in the marketplace interface you opened independently.
A private conversation is not a completed order. A screenshot can describe a transaction that never happened. Our ENS selling guide separates listing, accepting an offer and confirmed proceeds.
A short example of a useful pause
A creator receives a direct message saying her name will disappear unless she completes an upgrade that day. She already has a calendar entry for renewal, but does not use the message’s link. She opens the official app, checks the actual expiry and compares the provider’s public release status.
Her review produces two concrete facts: the registration status and the current supported procedure. Neither depends on the sender’s urgency. She can then perform any legitimate maintenance through the independently opened site.
If you already interacted
Stop using the suspicious page and record the public transaction references and requests you approved. Distinguish a connected site, a granted approval and an exposed recovery phrase when seeking help. Those events call for different responses.
Use the provider’s official security instructions for the incident you actually observed. Never send credentials to someone offering recovery help. Do not let another urgent message decide the next action. There is no recovery promise in this checklist, and an onchain loss may not be reversible.
Keep a repeatable routine
- Use independently verified official entry points.
- Check the full name and destination.
- Compare each request with the action you intended.
- Record confirmed ownership or configuration afterward.
- Keep renewal reminders and public profile data deliberate.
For ongoing maintenance, link this routine with the renewal guide and transfer checklist. Checking a specific task is more useful than treating a familiar brand logo as a guarantee.
Finished when: you can explain the intended action, verify the exact resource and destination, and identify the resulting confirmed state without relying on an unsolicited message.
Sources and review
Official documentation reviewed 23 October 2026. Procedures and compatibility below are documentation-based; no purchase, wallet transaction or payout was performed.
ENS safety and common scams ↗ENS lookalike characters and names ↗ENSv2 announced changes, not live at review ↗OpenSea listings and accepting offers ↗