Similar domains and mirrored pages should be handled as entry-path checks. The useful question is not whether a page looks familiar, but whether the source path, Ledger Wallet state, and device screen describe the same task. That keeps the article neutral and operational.
Similar domains should be compared as paths
Record the page path exactly as shown and compare it with the known entry path. A small wording or layout difference is not enough to decide the next step. The next step should come from a known Ledger Wallet entry, not from a page that was reached by memory or a forwarded link.
The Ledger Wallet download guide gives the stable app-entry reference for platform and version checks.
Mirrored pages need app-state confirmation
If a page copies familiar colors, menus, or support wording, compare it with Ledger Wallet state. The app should show the task context before the user moves toward a device-side action. If app state and page wording diverge, pause and write a record.
- Copy the visible path into a private note for comparison.
- Use Ledger Wallet state as the app-side reference.
- Do not place recovery phrase or PIN content into page forms.
Device-screen tasks should remain separate
A mirrored page can describe a task, but the device screen confirms what the hardware is being asked to do. The entry verification checklist helps separate source path, app state, device state, and record.
Keep the method stable when page design changes
The public value is the method: path, app state, device screen, record. The article should not claim to describe every later page design; it should give readers a stable comparison process.
