SkyBell Technologies, Inc. is an Irvine, California smart-home security maker best known for hardwired Wi-Fi video doorbells. The company holds three IEEE MA-L (24-bit OUI) blocks — 68:F0:D0, 9C:54:DA, and D0:C1:93 — split across two name variants in IEEE's public registry: the earlier D0:C1:93 block is registered to "SKYBELL, INC" while the two later blocks (9C:54:DA, 68:F0:D0) carry "SkyBell Technologies Inc.", a registry-name change that tracks a roughly 2019 rebranding of the same entity at the same 1 Jenner, Suite 100, Irvine address. The devices behind these prefixes are AC-powered (16–24 VAC) Wi-Fi doorbell cameras operating on 2.4 GHz 802.11 b/g/n, with 1080p HD video, a ~180-degree field of view, two-way audio, color night vision, and PIR motion sensing — the standard consumer-IoT camera profile: network-accessible, cloud-dependent, and mobile-app-controlled. SkyBell sells both direct-to-consumer and heavily through professional security integrators; its hardware is widely resold under the Alarm.com ADC-VDB101/102/105/106 part numbers and was historically offered through a Honeywell Home reseller partnership. No SkyBell-specific CVEs were located in NVD, and no CISA advisories name the brand, though the smart-doorbell category as a whole carries documented IoT vulnerability classes (hardcoded credentials, auth bypass, unpatched firmware). As with all OUI work, note that IEEE publishes no registration dates for these blocks — any "date registered" on third-party MAC lookup tools is a database artifact, not an IEEE fact.
- IEEE assignment
- 3 prefixes → SkyBell, registered Irvine, CA, US, across two name variants [Confirmed] — IEEE MA-L (enrichment/registries/oui.csv)
- Registry / block size
- MA-L (24-bit OUI) for all three blocks; not present in MA-M (mam.csv) or MA-S (oui36.csv) [Confirmed] — IEEE oui.csv. NOTE: IEEE's public OUI data publishes NO assignment/registration date (oui.csv columns are only Registry, Assignment, Organization Name, Organization Address); any "date registered" on third-party tools (e.g. maclookup.app) is a database artifact, not an IEEE fact.
- Prefixes (all MA-L)
- 68:F0:D0 ("SkyBell Technologies Inc."), 9C:54:DA ("SkyBell Technologies Inc."), D0:C1:93 ("SKYBELL, INC") [Confirmed] — IEEE oui.csv / maclookup.app
- HQ / country
- 1 Jenner, Suite 100, Irvine, CA 92618, US (registry address) [Confirmed] — IEEE MA-L (registry rows)
- Company status
- active [Confirmed] — skybell.com
- Name variants
- "SKYBELL, INC" (earlier, D0:C1:93) and "SkyBell Technologies Inc." (later blocks); same Irvine entity/address, registry-name change tracking a ~2019 rebrand [Likely — inferred from two name variants at one address] — IEEE oui.csv, maclookup.app
- Device types
- Wi-Fi video doorbell cameras and smart-home security accessories (Trim II, Slim I/Slim Line models, Chime accessory, companion mobile app) [Confirmed] — skybell.com, security.org review
- Device specs
- hardwired AC 16–24 VAC; Wi-Fi 802.11 b/g/n at 2.4 GHz; 1080p HD video, ~180° field of view, two-way audio, color night vision, PIR motion sensing [Confirmed] — truehomeprotection.com data sheet (ADC-VDB101/102/105/106), security.org
- Partnerships / integrations
- Alarm.com (resold as ADC-VDB101/102/105/106), RapidSOS / HOME911 first-responder integration, historical Honeywell Home reseller partnership [Confirmed] — securitybase.com, honeywellhome.com, skybell.com
- Security context
- no SkyBell-specific CVEs in NVD and no CISA advisories naming the brand located; broader smart-doorbell category has documented IoT vulnerability classes (hardcoded credentials, auth bypass, unpatched firmware) but none named SkyBell [Confirmed (absence-of-finding as of 2026-06-21)] — nvd.nist.gov, latesthackingnews.com (other brands), skybell.com safety page
- Allocated date
- Unknown — IEEE publishes no registration dates for OUI/MAC prefix assignments [Confirmed] — IEEE oui.csv column set
- Analyst note
- A globally-administered SkyBell OUI reliably identifies SkyBell doorbell hardware for asset classification; the device class is cloud-dependent consumer IoT, so treat it as a network-accessible camera endpoint. Do not present any third-party "date registered" as an IEEE registration date.