Look-alike Domains
A practical approach to look-alike domains
The practical value of “Look-alike Domains” becomes clearer when it is placed inside the full Phishing & Scam Awareness workflow rather than treated as an isolated definition. Phishing often uses look-alike domains, fake support, false airdrops, urgent notices or copied interfaces to trigger connections, signatures or disclosure of secret material. The source, domain, request details and on-chain target matter more than visual resemblance.
On this page, the broader goal is to recognize look-alike domains, fake support, false airdrops, malicious signatures, remote control and urgency tactics. “Look-alike Domains” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Stop when a page applies urgency, requests remote control or asks for an unfamiliar approval. Never send a seed phrase, private key or verification code to another person, and do not treat knowledge of a public address as proof of identity.
If a critical detail cannot be independently confirmed, stopping to gather more information is usually safer than repeatedly submitting the same action. In Phishing & Scam Awareness, apply this principle together with the checks described under Look-alike Domains.
Fake Airdrops
A practical approach to fake airdrops
The practical value of “Fake Airdrops” becomes clearer when it is placed inside the full Phishing & Scam Awareness workflow rather than treated as an isolated definition. Phishing often uses look-alike domains, fake support, false airdrops, urgent notices or copied interfaces to trigger connections, signatures or disclosure of secret material. The source, domain, request details and on-chain target matter more than visual resemblance.
On this page, the broader goal is to recognize look-alike domains, fake support, false airdrops, malicious signatures, remote control and urgency tactics. “Fake Airdrops” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Stop when a page applies urgency, requests remote control or asks for an unfamiliar approval. Never send a seed phrase, private key or verification code to another person, and do not treat knowledge of a public address as proof of identity.
Over time, these checks can become a personal routine that is repeated before important transfers, signatures and approvals. In Phishing & Scam Awareness, apply this principle together with the checks described under Fake Airdrops.
- Confirm the current network, intended target and purpose
- Never enter or send a seed phrase, private key or verification code
- Verify the result with an independent record after submission
Malicious Signature Requests
A practical approach to malicious signature requests
“Malicious Signature Requests” deserves its own check because it can change the object, network, permission or final state involved in Phishing & Scam Awareness. A signature is cryptographic confirmation of a message, structured payload or transaction. The consequences vary by request type: some signatures prove address control, while others can authorize a transaction or permission change, so “sign” should never be treated as a generic login button.
On this page, the broader goal is to recognize look-alike domains, fake support, false airdrops, malicious signatures, remote control and urgency tactics. “Malicious Signature Requests” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Review the domain, network, destination, amount, contract method and permission scope before signing. If the request is unrelated to the task or is not understandable, reject it and return through a trusted entry point rather than clicking through repeated prompts.
Over time, these checks can become a personal routine that is repeated before important transfers, signatures and approvals. In Phishing & Scam Awareness, apply this principle together with the checks described under Malicious Signature Requests.
Remote-control Risks
A practical approach to remote-control risks
Within a real Phishing & Scam Awareness workflow, “Remote-control Risks” is a decision point where interface familiarity should not replace independent verification. Wallet security depends on the device as well as the blockchain. Public computers, unnecessary browser extensions, remote-control software, clipboard substitution and unpatched systems can change what a user sees or submits.
On this page, the broader goal is to recognize look-alike domains, fake support, false airdrops, malicious signatures, remote control and urgency tactics. “Remote-control Risks” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Before a sensitive action, confirm that the device is under your control, review installed extensions and re-check any pasted address. Avoid handling seed phrases, private keys, important signatures or significant transfers on public or remotely controlled devices.
If a critical detail cannot be independently confirmed, stopping to gather more information is usually safer than repeatedly submitting the same action. In Phishing & Scam Awareness, apply this principle together with the checks described under Remote-control Risks.
- Confirm the current network, intended target and purpose
- Never enter or send a seed phrase, private key or verification code
- Verify the result with an independent record after submission
When Something Looks Wrong
A practical approach to when something looks wrong
Start “When Something Looks Wrong” with three questions: what object is involved, which network or environment applies, and what state or permission can change? This topic should be understood in the context of how to recognize look-alike domains, fake support, false airdrops, malicious signatures, remote control and urgency tactics, with the object, network and evidence source verified before the next action.
On this page, the broader goal is to recognize look-alike domains, fake support, false airdrops, malicious signatures, remote control and urgency tactics. “When Something Looks Wrong” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Use public, verifiable information first and compare the wallet view with on-chain records. Secret credentials, unexplained signatures and expanded permissions are not suitable areas for trial-and-error clicking.
The objective is not maximum speed; it is being able to explain the action, understand its effect and verify the outcome afterward. In Phishing & Scam Awareness, apply this principle together with the checks described under When Something Looks Wrong.