
Yes. A Bluetooth Low Energy scanner can detect radio advertisements from a nearby AirTag when the tag is transmitting and your phone receives those packets. What a generic scan cannot do is turn every nearby Bluetooth result into reliable proof that the device is an AirTag, or that it is being used to track you.
Apple lists Bluetooth as part of AirTag connectivity for proximity finding. Bluetooth LE itself uses advertising for device discovery: nearby devices broadcast small packets, and a scanner listens for those packets when it is on the right channel at the right time.
{getToc} $title={What a Bluetooth scanner can tell you about an AirTag}
A scanner can see the radio layer
When a BLE device advertises, a scanner can receive information that the device chose to broadcast. Depending on the scanner and the advertisement, that can include a local name, manufacturer data, service data, service UUIDs, signal strength and other fields.
That is useful evidence. It tells you that a Bluetooth device was observable nearby during the scan. It does not automatically tell you the exact product model, the owner, or why the device is there.
| Scanner clue | What it can support | What it does not prove |
|---|---|---|
| Nearby BLE advertisement | A Bluetooth device was observable during the scan | That the device is an AirTag |
| Apple-related manufacturer data | The advertisement contains Apple-associated data | That every Apple-related broadcast is a tracker |
| Find My-family pattern | The broadcast more closely matches a Find My accessory pattern | That the exact device is an AirTag or that tracking is unwanted |
| RSSI | Relative signal comparison while you move | Exact distance or device identity |
An AirTag may not appear with a stable, obvious name
Do not expect every AirTag to show up as a neat row labeled "AirTag." Apple says AirTag and other Find My network accessories use Bluetooth identifiers that change frequently. A generic scanner can therefore show an identifier that later changes, and the visible name or other advertisement fields may be incomplete or absent.
This is one reason raw Bluetooth lists are easy to overinterpret. The Bluetooth scanning guide explains the difference between radio visibility and device identity.
Protocol-aware classification is stronger than guessing from a name
A better tracker-oriented scanner looks at advertisement structure instead of treating any Apple device name or company identifier as proof. Tracker Detector: Tag Finder checks Apple manufacturer data for a Find My offline-finding pattern, refines compatible Find My-family observations using the advertised status information, and can attempt an on-demand device-name read for compatible accessories that respond.
Those extra checks narrow the interpretation, but they still have limits. A Find My-family pattern can belong to an AirTag or another compatible Find My accessory, and not every accessory exposes a readable identity. A tracker-like result is radio evidence, not proof of ownership or intent.
RSSI can help you search, but it is not an AirTag detector by itself
Signal strength can be useful after you have chosen one nearby result to follow. If repeated readings generally get stronger as you move toward one area, that can help narrow the search.
RSSI is affected by walls, furniture, your body, antenna orientation and radio reflections. Use it as a trend, not a meter reading that claims an exact distance. The Bluetooth RSSI guide covers that process in more detail.
Operating-system tracker alerts answer a different question
A generic BLE scan asks what Bluetooth advertisements are nearby now. Android and Apple unwanted-tracker systems add context about separation from the owner and whether a compatible tracker appears to be moving with you over time.
That distinction matters. A Bluetooth scanner may see a nearby tracker that belongs to another traveler, a family member or someone sitting close to you. Google explicitly notes that a tracker found in a manual scan may simply be misplaced or temporarily separated from its owner.
For a safety concern, use the operating system's unknown-tracker tools as the primary safety layer. The Bluetooth tracker safety guide explains how those alerts differ from a raw scan, and the Bluetooth scanner and tracker guide covers the broader limits of manual BLE discovery.
A practical workflow
- Start with any native Android or Apple unwanted-tracker alert you already received.
- If you want an additional manual check, run a BLE scan and separate ordinary known devices from unexplained results.
- Prefer advertisement evidence and compatible identity refinement over device-name guessing.
- If one result remains relevant, compare repeated RSSI readings while moving slowly.
- If you physically find a tracker that may be associated with an unwanted-tracking alert, follow the platform's identification and disable instructions rather than relying on the scanner alone.
Sources and further reading
- Apple Support: AirTag technical specifications
- Apple Support: AirTag (2nd generation) technical specifications
- Apple Support: unwanted tracking alerts
- Android Help: Find unknown trackers
- Bluetooth SIG: Bluetooth LE advertising and device discovery
- Apple Developer: Core Bluetooth advertising data
- Google Play: Tracker Detector: Tag Finder