Ledger authenticity checking is a sequence of observable steps. It is not limited to the outside of the box, and it is not completed by a page title alone. A useful review moves from the entry source to the package, then to Ledger Wallet, then to the Ledger device screen, and finally to a local record that can be checked later.
Authenticity checking is a sequence, not one signal
The first part of the sequence is the path that starts the check. A fixed source keeps the review from drifting between browser pages, message links, and app prompts. The second part is the physical arrival state, including box condition, accessory list, and whether the device appears to follow a normal first-use flow. The third part is the app and device-state check.
If you are checking a newly received device, the Ledger unboxing inspection flow helps keep the physical review separate from the app review. That separation makes each observation easier to explain later.
Where Genuine Check fits in the sequence
Genuine Check belongs inside Ledger Wallet after the app is opened from a fixed source and the device is connected in the expected way. It should be treated as one step in the full authenticity process, not as a replacement for source review or device-screen reading. The app can report the check state, while the device screen keeps sensitive confirmation visible to the user.
For the app-side detail, continue with how the official firmware Genuine Check works. Use it after you have already confirmed which device, app, cable, and platform you are using.
How packaging and device state should be read together
Packaging can provide useful arrival context, but it should be read together with device state. A clean package is not the whole review, and a packaging concern should not be turned into a broad conclusion without checking the app and device path. Keep the questions concrete: what did the box show, what did Ledger Wallet show, and what did the device screen show?
Finish with a record that is useful later
The final record should include the source path, device model, package observation, app state, device-screen state, and next step. It should not include recovery words, PIN details, or private backup images. If you need a broader technical frame for why device-side confirmation matters, read the Secure Element technology overview. Then keep the authenticity note short enough that it can be compared during a later support or after-sales conversation.
