Website entry recognition should be handled as a page and domain check. The user needs a stable entry, a clear download path, and a later device-screen match, not a long list of unrelated warnings.
Start with the visible domain
Read the domain and page context before clicking deeper. Keep the check focused on the entry being used, not on broad web browsing behavior.
Use the app-entry baseline
If the task is downloading Ledger Wallet, compare the page with Ledger Wallet Download and Installation Guide before moving to setup.
Check page purpose before installing
A download page, support page, and device setup page serve different tasks. Name which task the page is supposed to support before continuing.
Confirm later on the device screen
After installation, the app and device screen should align. If the device state is the question, use What Ledger Authenticity Checking Really Is as a route reference.
