Similar Ledger entry and download pages should be checked by comparing the domain, app path, page task, and device screen. The goal is not to judge by appearance alone, but to return to a route and task that can be identified before continuing.
Compare the domain and page task together
Look at the domain, page title, navigation path, and what the page is asking you to do. A page that only looks familiar is not enough context for a setup or download task.
Use a known Ledger Wallet app path
When the task is download or installation, restart from a known app path and compare the page with the Ledger Wallet download and installation guide.
Keep device screen confirmation separate
Download pages and app pages can prepare the task, but device-side confirmation still belongs on the hardware screen. The workflow boundary is explained in the Secure Element basics article.
Protect recovery phrase and PIN boundaries
If a page task asks for recovery phrase words or PIN details outside the device workflow, pause and return to the record boundary. The computer and phone entry boundary is covered in the recovery phrase entry boundary guide.
