---
title: "Unknown AirTag Alert: How to Find and Disable a Tracker"
author: "Kshitij Gupta"
author_url: "https://theinfosiast.com/about-us/"
author_linkedin: "https://www.linkedin.com/in/kshitij-gupta-855535134/"
publisher: "The Infosiast"
canonical_url: "https://theinfosiast.com/apples-airtags-lawsuit-a-potential-weapon-for-stalkers/"
pillar: "Cybersecurity"
date_published: "2024-03-16"
date_modified: "2026-11-08"
---

# Unknown AirTag Alert: How to Find and Disable a Tracker

> **Canonical Citation URL**: [https://theinfosiast.com/apples-airtags-lawsuit-a-potential-weapon-for-stalkers/](https://theinfosiast.com/apples-airtags-lawsuit-a-potential-weapon-for-stalkers/)  
> **Author**: [Kshitij Gupta](https://www.linkedin.com/in/kshitij-gupta-855535134/) | **Publication**: [The Infosiast](https://theinfosiast.com/)

**Reviewed on September 6, 2026.** This guide explains what an unwanted-tracker alert means and the practical steps Apple and Google provide for locating, documenting, and disabling an unknown AirTag or compatible Bluetooth tracker.

**If you feel unsafe now:** Move to a safe public place, contact a trusted person, and call local emergency services. Do not confront a suspected stalker or travel to a private place just to search for a tracker.

## What an unknown AirTag alert means

An alert means that a Bluetooth location tracker separated from its owner appears to have been moving with you over time. It does not prove malicious tracking. The device might be attached to borrowed keys, luggage, a vehicle, or another item traveling with you. Treat the alert seriously while you check the context.

Apple and Google support cross-platform unwanted-tracker alerts. Apple says compatible iPhones and iPads can warn about AirTags, certain AirPods, Find My accessories, and compatible Bluetooth trackers. Google says Android 6 and later can provide unknown-tracker alerts for compatible Find Hub tags, headphones, and Apple AirTags.

## First steps for any unwanted-tracker alert

- **Open the alert and review the map.** Note where the tracker was detected moving with you.

- **Take screenshots.** Save the alert, route, times, and any device details before they disappear.

- **Consider an innocent explanation.** Check borrowed belongings and ask trusted companions whether they own the item.

- **Play a sound when it is safe.** Both Apple and Google provide this option for supported trackers.

- **Search likely hiding places.** Check bags, coat pockets, mobility equipment, children’s belongings, and the accessible parts of a vehicle.

- **Preserve identifying information.** If you find an AirTag, use an NFC-capable phone to read available details and record its serial number.

## How to find an unknown tracker on iPhone or iPad

Tap the unwanted-tracking notification, choose **Continue**, and use **Play Sound**. On supported devices, **Find Nearby** may show distance and direction. Apple recommends keeping iOS or iPadOS updated and enabling Location Services, Bluetooth, Tracking Notifications, and the relevant system-location settings.

You can also open the Find My app, choose **Items**, and review recently detected unknown items. Options vary by tracker and device. Follow the instructions shown on your phone rather than relying on screenshots from an older article.

## How to find an unknown tracker on Android

Tap the notification to open its map, then use **Play sound** or the available nearby-finding option. Google also provides a manual scan:

- Open **Settings**.

- Choose **Safety & emergency**.

- Open **Unknown tracker alerts**.

- Choose **Scan now**.

Menu names can vary on older Android versions. Google states that turning off Bluetooth, Location Services, or Airplane Mode does not by itself stop the tracker's owner from receiving the tracker’s location. The tracker must be disabled using its manufacturer’s instructions.

## Before disabling a tracker, make a safety decision

Disabling an AirTag stops new location updates, but it may also reveal to an abusive person that the tracker was discovered. If you believe a partner, former partner, or another known person placed it, consider contacting law enforcement or a specialist support service before changing the device. Your immediate safety matters more than completing every technical step.

If you choose to disable the device, follow the instructions displayed in the alert. For an AirTag, Apple’s instructions normally involve pressing down on the metal battery cover, rotating it counterclockwise, and removing the battery. Check Apple’s current support page because device instructions can change.

## Evidence worth preserving

- Screenshots of the alert and detection map

- Date, time, and places where the alert appeared

- Photographs showing where the tracker was found

- The serial number or other identifier shown by the phone

- Messages, threats, or earlier incidents that explain the safety concern

Avoid modifying or discarding the tracker if police may need it. Apple says law enforcement may request available information associated with an AirTag investigation and may need the device and serial number.

## What the alert cannot tell you

The map shows where your phone detected the tracker traveling with you. It does not show every place the owner checked its location, prove who placed it, or establish criminal intent. Detection can also be delayed. Use the alert as a safety signal and evidence source, not as a complete investigation.

## About the AirTag lawsuit behind the original article

This page began as a short report about allegations that AirTags had been misused for stalking and about litigation concerning Apple’s responsibility. Allegations in a lawsuit are not findings that every claim has been proven. The continuing public value of this page is the practical response guidance above, which is based on current platform instructions.

## Related Online Safety guides

- [Online Safety: prevent scams, report fraud, and recover accounts](https://theinfosiast.com/online-safety-guide/)

- [Google Account safety and recovery guide](https://theinfosiast.com/google-account-center-guide/)

- [WhatsApp scams: warning signs and response steps](https://theinfosiast.com/whatsapp-scams-safety-guide/)

## Sources

- [Apple Support: What to do if an AirTag or compatible tracking device is with you](https://support.apple.com/en-us/119874)

- [Android Help: Find unknown trackers](https://support.google.com/android/answer/13658562?hl=en)

**Explore More in Practical Tech:** Learn about everyday computing, secure network protocols, and software productivity in our [Practical Technology & AI Resource Hub](https://theinfosiast.com/practical-technology-ai-digital-skills/).

## How Crowd-Sourced Bluetooth Tracking Actually Works

An AirTag has no GPS receiver and no cellular modem. It cannot know its own location. Everything it does is built on three primitives: short-range radio advertisements, public-key cryptography, and the fact that hundreds of millions of phones around the world are already listening for anonymous BLE beacons whether or not their owners realize it. Understanding those primitives is what separates a panic reaction ("there's a tracker on my car") from a correct forensic response ("this beacon was last seen 40 meters behind me, so it is probably not attached to anything I'm carrying").

Every two seconds or so, an AirTag wakes its Bluetooth radio and transmits a BLE advertisement frame — a small broadcast packet, typically under 100 bytes of payload, sent without any connection request. Any nearby phone can hear it. The tag never pairs, never asks for acknowledgment, and never learns who heard it. That asymmetry is the entire design: cheap, low-power, and deliberately one-directional.

### The Rotating P-224 Key: Anonymity With Verifiability

The heart of every advertisement is a rotating ephemeral public key. Apple uses an elliptic-curve key pair over the NIST P-224 curve (a 28-byte coordinate representation, shorter than the P-256 curve used in TLS). Roughly every 15 minutes, the tag derives a fresh 16-digit sequence from its current secret state, combines it with a new ephemeral P-224 public key, and broadcasts both. The result:

- **Static MAC tracking dies.** The tag also randomizes its Bluetooth MAC address on rotation, so neither the device address nor the advertised payload stays constant long enough to follow through a crowd, a parking garage, or a train station.

- **Only the owner can decode reports.** A passing stranger's phone that picks up the beacon cannot interpret it. The phone simply records "I saw this opaque blob at these coordinates, at this time" and uploads it to the Find My network — end-to-end encrypted under the owner's key pair held by the tag's paired iCloud/FMF account.

- **The owner's lookup is one-way.** The owner's device queries the network for the tag's last known rotating-key identifiers; only matching encrypted location reports decrypt successfully, because each report was sealed to the tag's per-rotation public key.

Google's Find My Device network (FMDN) and Tile's mesh use structurally similar designs: rotating broadcast identifiers, third-party devices relaying encrypted sightings, owner-side decryption. FMDN differs in scale ambition — it draws on the roughly three-billion-device Android install base (Android 6.0+ participates in the network layer), which cuts expected time-to-first-fix from hours toward minutes in dense areas. That same density raises the anti-stalking stakes, which is why the cross-platform detection work matters more than any single vendor's alerting.

### Offline Finding vs. Online Reporting

AirTag beacons support two sighting channels. In *online* finding, a phone with connectivity uploads an encrypted report to Apple/Google servers immediately. In *offline* finding — relevant when the finder has no data connection or the relayed phone is another AirTag-aware device — the sighting is cached and uploaded later. For a stalker scenario this latency is forensic gold: the detection algorithms care about spatial-temporal consistency across hours of sightings, not the freshness of any one report.

| Property | AirTag (Find My) | FMDN (Android network) | Tile (proprietary mesh) |
| --- | --- | --- | --- |
| Broadcast identifier | Rotating ECC P-224 ephemeral key + 16-digit sequence, ~15 min rotation | Rotating ephemeral keys per FMDN spec | Rotating Tile UUIDs |
| Adv interval (typical) | ~2 s burst frames; on-the-move acceleration shortens it further | Vendor-defined, typically 1–5 s | Vendor-defined (~2 s nominal) |
| Relay base | iPhones/Macs/iPads (hundreds of millions) | Android 6.0+ devices opted into the network | Tile app users only (smaller, opt-in) |
| Report crypto | E2EE to owner key pair; relays see opaque blobs | E2EE with owner-held decryption keys | Encrypted to Tile cloud account |
| Cross-platform alerting | Native on iOS; via Apple's Android "Tracker Detect" app | Native on Android 6.0+ (Unknown Tracker Alerts) | In-app only |

### The DULT Specification: Engineering Against Stalkers, Not Just for Convenience

For years each vendor shipped its own anti-stalking heuristic — Apple's iOS would alert an iPhone user about an AirTag traveling with them, but a non-Apple phone heard nothing at all. The fix is a joint industry specification drafted through the IETF under the working name *Detecting Unwanted Location Trackers* (the `draft-detecting-unwanted-location-trackers` Internet-Draft), co-developed by Apple and Google so that any compliant tracker broadcasts metadata that *any* compliant scanner OS can interpret. That shared grammar has three load-bearing pieces:

- **Detection mode.** The tag advertises which protocol it speaks (Find My, FMDN, Samsung SmartTag, Tile-compatible modes) so a single scanner app can identify heterogeneous tags in one pass.

- **Owner state bit ("not mine").** The tag signals whether it believes its owner is currently nearby. When an owner walks away, the flag flips, and a nearby stranger's phone gains permission to start counting dwell time against the tag.

- **Access control / "trigger sound" and key material.** The spec defines how a scanning device fetches the tag's public configuration (owner-shared metadata, serial-number-derived identifiers, audio-playback commands) without letting a random passerby maliciously force beeps on someone else's legitimately owned tag.

iOS 17.5+ and modern Android builds implement this cross-platform detection natively: one system-level service scans for all major tracker families, not just first-party hardware. This matters enormously if the tracker aimed at you was manufactured by a different ecosystem than your phone.

### Spatial-Temporal Clustering: Separating Commuters From Pursuers

The hardest engineering problem in unwanted-tracker alerting is false positives. In any urban environment your phone overhears dozens of anonymous BLE tags every minute — strangers' keys in the next car seat, luggage tags three rows back on a bus. Alerting on mere proximity would train users to dismiss alerts within a week, which is functionally equivalent to breaking the feature.

Compliant algorithms therefore evaluate persistence across a joint spatial-temporal window rather than raw RSSI alone:

- **Dwell time.** A "not mine" beacon must remain co-located with the victim long enough that coincidence becomes implausible. Typical consumer implementations require roughly 15 minutes or more of sustained presence after the owner leaves before an alert fires (exact thresholds vary by vendor and OS version).

- **Path correlation.** The sighting history is compared against the victim's own motion trace. A tag that appears near you in a coffee shop, then reappears 40 meters behind you as you walk home, then again at the station platform, has crossed paths repeatedly — but it also moves like your shadow. A commuter's AirTag left on a train rides away from you monotonically; its displacement-from-victim grows over successive sightings.

- **RSSI trajectory, not snapshot.** Signal strength integrated over multiple advertisement frames distinguishes "tag inside my bag" (consistently strong, variance low) from "tag in someone else's pocket passing through" (one or two strong bursts amid weak ones). Modern scanners also use the BLE direction-finding extensions where hardware supports them.

- **Sleep-state weighting.** Compliant tags can advertise sleep state (in-motion vs stationary). A stationary tag near a parked car for hours reads differently than one vibrating around on a keychain in transit.

For a modified tracker — battery intact but speaker deliberately disabled or removed — audio-based escalation fails silently. Detection therefore cannot rely on the sound being heard; it must still surface the alert visually, which is exactly why the DULT framework treats the audible tone as a secondary confirmation channel rather than the primary alarm.

### Precision Finding: UWB ToF/AoA vs RSSI-Only Scanning

Once an alert confirms an unwanted tag, localization becomes the task. Two physical regimes are available:

**RSSI trilateration by feel.** Received signal strength decays roughly with distance (free-space path loss goes as the square of frequency-and-distance products; in practice indoor multipath makes RSSI noisy at ±30–50% error even within a few meters). The practical technique is gradient descent: walk toward/away from the suspected location and watch whether the scanner's reported RSSI rises or falls. Slow, imprecise, works on any phone with BLE, and is the only method available against non-UWB trackers.

**Ultra-Wideband ranging (IEEE 802.15.4z).** iPhone 11 and later (and many flagship Android phones) contain UWB radios that perform precise time-of-flight exchange with AirTags: nanosecond-scale round-trip timing yields centimeter-grade range, while angle-of-arrival processing across multiple antenna elements gives bearing. The "Find Nearby" arrow-and-distance UI is this math made visible — the phone measures ToF in tens-of-picoseconds-to-nanosecond quantization windows and AoA phase deltas across antennas to place the tag on your compass rose. Against a *stock* AirTag this is near-instant. Against a speaker-muted one it still works; against a physically shielded or battery-depleted tag no radio method works at all, which is where physical inspection takes over.

| Method | Typical accuracy | Hardware needed | Best used for |
| --- | --- | --- | --- |
| BLE RSSI gradient walk | ~1–5 m; degraded by multipath | Any BLE phone | Non-UWB trackers, quick sweep of vehicle interior |
| UWB ToF + AoA (802.15.4z) | ~0.1–0.3 m range; bearing to a few degrees | UWB-capable phone + UWB-tagging tracker | Final-meter localization of AirTag/SmartTag-class devices |
| NFC forensic readout | Identification only (no distance) | Any NFC phone, powered-off tag still works | Serial number, owner status, disable confirmation |

### Field Procedure: Inspection, Forensic Readout, Evidence, Disablement

The sequence below assumes you have already received a "tracker traveling with you" alert or found an unexplained hard plastic disc. Order matters — disabling before documenting destroys the only evidence most victims will ever hold.

#### Step 1 — Locate without touching

If your phone supports UWB precision finding on the detected tracker type, drive it to centimeter accuracy first: bags and pockets, then vehicle wheel wells, bumpers, under the dash, seat crevices, exterior trim. If not, do a systematic RSSI sweep in segments (vehicle cabin → chassis perimeter → personal bags), noting where signal peaks. Photograph the tag *in place* before moving it — that photo is contextual evidence showing where it was planted.

#### Step 2 — Physical inspection for tampering

- **Speaker check:** Stock AirTags chirp audibly when triggered remotely. A unit that has been detected but never beeps on any device's request likely had its speaker disconnected or removed — a known modification technique among abusive trackers. Press lightly on the steel face; a hollow or rattling sound versus the crisp click of intact internals is suggestive but not conclusive.

- **Seam integrity:** Look for pry marks, glue residue, or a misaligned seam between the white polymer shell and stainless back — signs the enclosure was opened.

- **Firmware oddities:** An AirTag that appears in scanner apps with an anomalous advertised payload length or that never exposes NFC readout despite being powered may be counterfeit hardware running modified firmware; treat such units as untrusted and handle accordingly.

#### Step 3 — NFC serial-number forensic readout

Tap the **white side** of the AirTag against the top/back of your NFC-capable phone. This works even while the tag continues advertising BLE — you do *not* need to open the battery compartment first. The readout returns:

- The tag's serialized identifier (partial serial / product model code), which can be cross-referenced with the manufacturer's status page;

- Whether it has been marked "lost" by its owner and, if so, contact details the owner chose to publish;

- The last four digits of the paired account's device serial — enough to identify whose ecosystem the tag belongs to without exposing full identity to you.

Screenshot everything before proceeding. On Android, the equivalent flow lives inside the system-level unknown-tracker scan; on iPhone it is surfaced directly after the NFC tap. Note the timestamp of each capture alongside the sighting history from your scanner app — a coherent timeline strengthens any later report to platform support channels or local authorities (rules and response processes differ by jurisdiction).

#### Step 4 — Preserve evidence state before disablement

- **Do not factory-reset the tag.** A reset wipes ownership bindings and makes attribution harder.

- **Export/record sighting history** from your tracker-detection app while entries are still cached; some implementations age out per-tag records within days.

- **Photograph the tag against a neutral background** (a plain sheet, next to a ruler or coin for scale) showing all faces plus the NFC-readout result on screen in one frame where possible.

#### Step 5 — Safe battery removal

- Orient the AirTag with the stainless steel face up and the white polymer face down.

- Place two fingertips on the steel disc and rotate *counterclockwise* (as viewed from the metal side) until the back plate detents free — no tools, minimal force; if it resists, grip the steel edge rather than pressing on the plastic shell.

- Lift the plate away; the CR2032 coin cell sits exposed, polarity-up.

- Slide or pry the cell out with a fingernail or non-metallic tool — do not short the contacts with keys or coins, which can heat a lithium cell dangerously.

- Once the battery is out, BLE advertisement stops immediately: the tag becomes radio-silent and cannot be located or triggered. Keep the cell separated from the housing in an insulating sleeve so accidental contact does not restore operation.

- If the unit showed tampering signs (no speaker response, opened seam), bag it whole — intact, unpowered — and avoid further handling beyond documentation.

A powered-off tag proves nothing to anyone afterward except through your photographs and serial record, which is why evidence capture precedes disablement in every defensible workflow.

### Residual Risks and What the Protocol Cannot Fix

The DULT ecosystem closes most of the gap between "phone hears beacon" and "victim gets warned," but honest engineering review surfaces limits:

- **Detection latency equals exposure time.** Any dwell-based algorithm grants the stalker a guaranteed head start — minutes under current thresholds, longer if the tag sleeps.

- **Non-compliant hardware.** Cheap counterfeit tags that skip DULT metadata fields fall outside cross-platform scanning; only manual RSSI sweeps find them.

- **Speaker removal defeats audio escalation,** leaving visual alerts as the sole channel — useless against a victim without their phone on their person at the critical moment.

- **Fresh batteries outlast patience.** A CR2032 in an AirTag runs for roughly a year, meaning periodic physical checks matter more than any one-time sweep.

Treat every alert as data: confirm with precision finding where available, document before disabling, and remember that the strongest single action you can take — rotating the battery out — is also the least reversible. The protocol architecture gives you the timeline; your discipline with evidence preserves it.

*Written and prepared by [Kshitij Gupta](https://www.linkedin.com/in/kshitij-gupta-855535134/).*
