An account's device list can contain more entries than the number of devices you own. A phone, a browser and an app may appear as separate sessions, and an old device name may not be immediately recognizable. The task is to understand access well enough to keep expected sessions and respond appropriately to unexplained ones.
Start from the provider's official account-security page using a route you trust. Do not follow an unexpected message's sign-in link merely because it claims that an unfamiliar device has been detected.
Establish which account you are reviewing
Check the account identifier before opening the device list. If you use personal and work accounts, it is easy to inspect the wrong one in a browser with several active identities. A correct list for the wrong account does not answer your question.
Google's device guidance explains that the page can show devices where you are or were signed in recently, and that a session can belong to a browser, app or service. Multiple entries therefore do not automatically establish unauthorized access.
Make a short private list of devices you expect: current phone, home computer, work-managed device if authorized and any recently replaced equipment. Include recent travel or a browser reinstall as context, without assuming those explanations account for every unfamiliar event.
Inspect details before acting on the name
Open an entry and compare the information the provider exposes, such as device type, approximate location, session activity and timing. Names can be generic, and network-based locations can be approximate. Treat each field as a clue rather than a definitive physical identification.
An entry showing recent activity may reflect background synchronization rather than a person actively clicking at that moment. Read the provider's explanation of its timestamps. Do not turn an unfamiliar time into a confident accusation about another person.
If you can identify an old device you no longer use, record that conclusion. If an entry remains unexplained, keep the relevant details and use the provider's suspicious-activity process. The purpose of inspection is to distinguish an ordinary cleanup from a possible security incident.
Sign out only the access you intend to remove
Use the official sign-out control for the identified session or device. Read its scope: the action may affect one session, several sessions or a whole device. Avoid a broad “sign out everywhere” operation as a casual experiment when it could interrupt essential access.
Before removing your only convenient session, make sure you understand the supported sign-in and recovery route. Do not disable the device that currently receives a necessary second factor without arranging the provider-approved alternative. This is particularly important during a phone replacement.
For employer-managed accounts, follow the organization's security process. An unfamiliar session may need investigation by the administrator, and you may not have all the context or controls. Report what you observe rather than trying to bypass management restrictions.
Treat unexplained access as more than a list-cleaning task
If you believe the account may be compromised, use the provider's full account-security guidance. Signing out one visible session may not resolve a changed password, altered recovery information, connected application or other unauthorized setting.
Check recovery details through the official controls and review the specific security steps recommended for the incident. Do not share verification codes or grant remote access to someone who contacts you claiming to fix the problem. Seek support through independently established channels.
Preserve the facts you need for a report, while keeping them private. A screenshot containing account identifiers or location history should not be posted publicly as a casual troubleshooting image. Give the legitimate support team only the information needed through an appropriate channel.
Verify the intended result
Return to the device page and confirm the targeted session's new state according to the provider's interface. Record what was removed and why. Then confirm that your normal devices still have the expected access and recovery arrangements.
Do not repeatedly remove entries solely because they reappear under an unfamiliar label; investigate whether your own browser or app is recreating the session. A clear understanding is more useful than an empty-looking list that fills again immediately.
The completed review leaves you with recognizable expected access, a documented response to anything unexplained and a working route back into the account. That is the result to seek, rather than reducing the device count to an arbitrary number.
Sources
- Google Account: See devices with account access
Account device pages show sessions and recent access; sign-out and suspicious-activity review are supported.
- Google Account: Set up a recovery phone or email
Recovery information can be updated through account settings; previous recovery details may remain available temporarily.