Tesla, Inc. — 6 MA-L prefixes + 1 MA-M block
Summary
- // what this is
- Tesla is registered to MAC prefix
0C:29:8Fand 5 more in the IEEE OUI database. When a device's MAC address begins with0C:29:8F, that block was registered by Tesla — the OUI identifies the maker of the network hardware, which is not always the brand on the device. - // analyst note
- Multiple OUI assignments across two registry classes (MA-L + MA-M) and two registered addresses indicate real manufacturing scale, clearing the bar for a standalone vendor entry rather than a bare single-OUI shell.
About this vendor.
Tesla, Inc., the electric-vehicle and clean-energy manufacturer, holds six MA-L (24-bit) OUI prefixes plus one MA-M (28-bit, IEEE 802c fine-grained) block in the IEEE registry — a modest but non-trivial footprint that reflects genuine hardware diversity rather than a single-product shell. Five of the six MA-L blocks are registered as "Tesla,Inc." at the company's legacy Palo Alto, CA address; the sixth (54:F8:F0) is registered under a differently formatted "Tesla Inc" string at 1 Tesla Road, Austin, TX — the Gigafactory Texas site that now serves as Tesla's corporate HQ — and is treated here as a distinct row rather than silently merged with the Palo Alto blocks. The MA-M block (DC:44:27:10/28) signals Tesla has exhausted an MA-L pool for at least one device category, consistent with high-volume manufacturing. Interfaces bearing these OUIs appear across vehicle telematics/infotainment systems, the Powerwall home battery, the Tesla Gateway, and Wall Connector EV chargers. A data-quality trap worth flagging: the Wall Connector Gen 3's own WiFi radio module carries prefix 80:91:33, which belongs to component supplier AzureWave Technology, not Tesla — don't conflate a supplier's chip OUI with the vehicle/product manufacturer's OUI. Tesla's connected-vehicle stack also has a multi-year documented security-research history, from a 2016 WiFi-to-CAN-bus compromise chain to a 2026 cellular/WiFi tracking disclosure.
- IEEE assignment
- 6 MA-L prefixes (0C:29:8F, 4C:FC:AA, 54:F8:F0, 90:E6:43, 98:ED:5C, D4:4F:14) → Tesla, Inc. / Tesla Inc [Confirmed] — the IEEE MA-L registry (lines 17152, 22961, 23279, 31810, 31813, 32998); cross-checked against Netify third-party MAC-vendor listing (https://www.netify.ai/resources/macs/brands/tesla)
- Registry / block detail
- 5 of 6 MA-L blocks registered as "Tesla,Inc." at 3500 Deer Creek Road, Palo Alto CA 94304; the 6th (54:F8:F0) registered under a differently-formatted "Tesla Inc" string at 1 Tesla Road, Austin TX 78725 — kept as a distinct row, not merged [Confirmed] — the IEEE MA-L registry
- MA-M block
- DC:44:27:10/28 → "Tesla,Inc.", Palo Alto CA [Confirmed] — the IEEE MA-M registry line 5533
- MA-S block
- none — two rows containing the literal substring "Tesla" are unrelated companies: 00:1B:C5:0/36 = "Tesla Controls" (San Diego, CA; unrelated building-controls company) and 8C:1F:64:F5/36 = "SemaConnect, Inc" at "4961 Tesla Drive, Bowie MD" (Tesla is a street name, not the org)[Confirmed] — the IEEE MA-S registry (lines 5302, 5779)
- HQ / country
- registry address is Palo Alto, CA, US for 5 of 6 MA-L blocks + the MA-M block; Tesla's operational HQ has since relocated to Austin, TX, which the 54:F8:F0 row reflects [Likely] — the IEEE MA-L registry, tesla.com
- Company status
- active [Confirmed] — tesla.com
- Device types
- vehicle telematics/infotainment modules (WiFi/Bluetooth LE/cellular) in Model S/3/X/Y and Cybertruck; Powerwall; Tesla Gateway; Wall Connector EV chargers [Confirmed] — https://www.tesla.com/support/energy/powerwall/own/connecting-network, https://www.tesla.com/support/energy/powerwall/own/registering-your-wall-connector-with-powerwall
- Third-party component caveat
- Wall Connector Gen 3's WiFi radio module carries MAC prefix 80:91:33, registered to AzureWave Technology Inc. (Taiwan), a chip supplier — not a Tesla-registered prefix[Likely, single web-search source] — https://teslamotorsclub.com/tmc/threads/gen-3-wall-connector-charger-does-not-show-up-on-my-wifi-network.189606/
- Security research context
- documented multi-year history — Tencent Keen Security Lab WiFi-to-CAN-bus remote compromise chain (2016, published 2020) and companion Black Hat 2017 paper; NCC Group Bluetooth LE relay unlock attack (2022); Northeastern University cellular/WiFi tracking and interception weaknesses in Model 3/Cybertruck (reported Feb 2026) [Confirmed, multiple independent sources] — https://keenlab.tencent.com/en/2020/01/02/exploiting-wifi-stack-on-tesla-model-s/, https://techcrunch.com/2022/05/18/bluetooth-attack-unlock-tesla/, https://news.northeastern.edu/2026/02/18/connected-cars-hacking-research/
- Dates
- no assignment/registration date is published by IEEE for any Tesla MA-L or MA-M row; correctly left null rather than sourced from third-party "date registered" scrapes [Confirmed] — the IEEE MA-L registry, the IEEE MA-M registry
- Related vendors
- none — Tesla Controls and SemaConnect are unrelated companies incidentally matching the substring "Tesla", not Tesla, Inc. subsidiaries
- Analyst note
- multiple OUI assignments (6 MA-L + 1 MA-M, with one MA-L block issued from a second, Austin-based address) indicate device-manufacturing scale beyond a bare single-block registrant — Tesla clears the vendor-substance bar for a standalone entry.