Skip to content
AdminKit

Using MAC vendor lookup to spot a rogue device on your network

AdminKit explains how a MAC vendor lookup helps identify an unfamiliar device on your network: it narrows an address down to a registered manufacturer, which combined with the device's IP, hostname and behavior is often enough to identify a known gadget rather than an intruder — within clear limits, since randomization (RFC 9542) and spoofing can both defeat the lookup.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • A MAC vendor lookup names the company that registered an address’s prefix with the IEEE. It narrows “unknown device” down to a maker, not to one specific unit.
  • On a modern home network, “no vendor” is a normal result. Android 10 and later, and Apple devices since iOS 14, join Wi-Fi with a private, randomized address by default.
  • You can spot a randomized address by eye: if the second hex digit is 2, 6, A or E, the locally administered bit is set and no vendor lookup will match it.
  • Confirm a device with more than its MAC address: hostname, DHCP lease time, traffic, and when it joins and leaves. A MAC address can be changed in software.
  • If a device really isn’t yours, change the Wi-Fi password. Blocking one MAC address is easy to get around.

Why start with “unidentified” rather than “intruder”?

An unfamiliar entry in a router’s client list is common and usually harmless — a device you own simply isn’t showing a recognizable name, or it reconnected under a different randomized address than last time. This guide walks through the practical steps for narrowing that entry down before deciding whether it’s actually a problem, using AdminKit’s MAC vendor lookup as the first identification step rather than the only one.

Randomized addresses also make “new device” alerts noisier than they look. Apple’s own support note says that if you manage a router configured to notify you when a new device joins, you are notified when a device first joins with a private address. The same phone can also come back with a different private address after you erase it, reset its network settings, or tell it to forget the network. So a “new device” alert, on its own, is often one of your own phones or laptops wearing a new address.

How do you find the device’s MAC address?

Most home routers and access points have a page in their admin interface — often called “connected devices,” “DHCP clients,” or “attached devices” — listing every client currently or recently on the network, along with its IP address, hostname (if the device reports one) and MAC address. If you’re on a network already and want a second source, running arp -a from a connected computer (Windows, macOS and Linux all support this command) lists MAC-to-IP pairs for hosts that device has recently exchanged traffic with, which is a useful cross-check against what the router itself reports. Microsoft’s arp reference describes -a as displaying “the current ARP entries”; on Linux, ip neigh show prints the same neighbour table, including IPv6 neighbours.

# Windows, macOS, Linux: IP-to-MAC pairs this computer has recently seen
arp -a

# Linux: the same neighbour table, IPv4 and IPv6
ip neigh show

The ARP cache only holds devices your computer has talked to recently, so an idle device may be missing from it. If it is, ping its IP address once (taken from the router’s list) and run arp -a again. Each place to look gives you a different piece of the picture:

Where you lookWhat it showsWhat it can miss
Router’s DHCP client listIP, MAC, hostname, often lease start or expiryDevices with a static IP that never asked for a lease
Router’s wireless client listMAC, signal strength, connected bandWired devices
arp -a on a computerIP-to-MAC pairs that computer has seen recentlyDevices it hasn’t exchanged traffic with
The device’s own settings screenIts current Wi-Fi address, and whether it is privateNothing, if you can get to the device

How do you look up the vendor?

Enter the unfamiliar MAC address into AdminKit’s MAC vendor lookup. It accepts the full address (colon- or hyphen-separated, Cisco dot notation, or 12 bare hex digits) or just the first three octets. The result tells you one of three things, covered in full in how to read a MAC address vendor lookup result:

  • A matched manufacturer name — the address’s OUI prefix is a real, IEEE-registered assignment, narrowing the device down to a specific company’s product lines.
  • No match on an otherwise normal-looking prefix — the addressing bits suggest a factory-assigned address, but that specific prefix isn’t in AdminKit’s copy of the published registry. A block assigned after that copy was taken won’t match until the copy is refreshed.
  • A locally-administered or randomized flag — the address was never drawn from a vendor’s registered block at all, most often because it belongs to a phone or laptop randomizing its Wi-Fi address per network, as described in RFC 9542.

The lookup checks the longest IEEE block first. RFC 9542 lists three prefix lengths the IEEE assigns: 24-bit MA-L (the classic OUI), 28-bit MA-M and 36-bit MA-S. A small MA-S block can sit inside a range that looks like someone else’s OUI, so the more specific match wins. The result also reports the matched prefix, the block type, and whether the address is multicast. A device’s own unicast address should never have the multicast bit set.

How can you tell a randomized address at a glance?

RFC 9542 §2.1.1 defines two special bits in the first octet. The lowest bit (M) marks a group or multicast address. The next bit (X, the “universal/local” bit) is zero for a global, IEEE-assigned address and one for a locally administered one. IEEE MA-L, MA-M and MA-S prefixes are always assigned with the local bit set to zero, so an address with the bit set to one can’t match any vendor block. On a device’s own unicast address, that bit shows up in the second hex digit:

Second hex digit of the first octetLocal bitWhat it usually means on your network
0, 4, 8 or C0 (global)A factory address from an IEEE block. A vendor lookup can match it.
2, 6, A or E1 (local)A randomized or software-set address. No vendor to find.
Any odd digit (1, 3, 5, 7, 9, B, D, F)M bit setA multicast or broadcast address, not a single device

Two example addresses, both synthetic: the first is taken from the documentation range RFC 9542 §2.1.4 reserves, and the second is the same address with the local bit flipped.

00:00:5E:00:53:01   first octet 0x00 = 0000 0000   local bit 0 -> look up the vendor
02:00:5E:00:53:01   first octet 0x02 = 0000 0010   local bit 1 -> randomized or software-set

How do you combine the vendor with what you already know?

A vendor match narrows “unknown device” down to a maker, not a specific unit — a manufacturer routinely reuses the same OUI across an entire product catalog. Combine it with context the router or arp -a already gave you:

  • IP address and DHCP lease time — a lease that started recently, around when you first noticed the unfamiliar entry, is a useful timing clue.
  • Hostname, if the device reports one — many IoT devices and smart TVs broadcast a recognizable default hostname even without a friendly name set.
  • Traffic pattern, if your router shows bandwidth per client — a device pulling meaningful traffic at odd hours is a different finding than one that’s essentially idle.
  • Presence over time — note when the entry appears and drops off. A device that leaves when a family member goes to work, or appears when the TV turns on, usually identifies itself.

A vendor name matching a brand of smart plug, camera, or streaming device you already own is usually enough, combined with these, to close the question without further action. A simple worksheet keeps the checks consistent:

What you foundLikely explanationNext step
Vendor matches a brand you own, hostname looks like a defaultOne of your own devicesRename it in the router so you recognize it next time
No vendor, local bit set, hostname like a phone or laptopA private Wi-Fi address on a phone, tablet or laptopCheck each device’s Wi-Fi details screen for its current address
Vendor is a network-chip maker, no hostnameAn IoT device using a generic Wi-Fi modulePower devices off one at a time and watch the list
Two devices showing the same MAC, connections droppingPossible spoofingTreat as suspicious; see the spoofing section below
Nothing matches after all of the aboveStill unidentifiedChange the Wi-Fi password and see what fails to reconnect

Why does a “no vendor” result not mean the worst?

A “no vendor” or “locally-administered” result is the expected outcome for a large share of modern personal devices, not a red flag by itself: Android 10+ and recent iOS, iPadOS and desktop operating systems randomize the MAC address used per Wi-Fi network by default, specifically to prevent the kind of tracking an OUI lookup enables. If the unfamiliar entry’s hostname or IP otherwise looks like a guest’s phone or your own secondary device, a vendor-less result is consistent with that, not evidence of something hidden.

The details differ by platform, which is why the same phone can show up as two “different” devices over a few weeks:

PlatformDefault behaviourWhen the address changes
Android 10 and laterA randomized address per network, kept for that network (“persistent”)Android 12 and later can re-randomize at connection time for some networks (“non-persistent”), for example after a DHCP lease expires and the phone has been away for more than 4 hours
iOS 18, iPadOS 18, macOS Sequoia 15 and later“Fixed” private address on networks with WPA2 or stronger; “Rotating” on weak or open networksRotating addresses change every 2 weeks; a reset of network settings or forgetting the network also gives a new one

The Android rows come from the Android Open Source Project’s MAC randomization behavior page; the Apple rows from Apple’s private Wi-Fi address support article. On every platform, the user can turn the feature off for a network, in which case the device uses its factory address and a vendor lookup works again.

What can’t a MAC address prove, and how does spoofing fool the lookup?

A MAC address is easy to change in software on most operating systems — a practice called MAC spoofing — so a match against a device you recognize, or even an address identical to one you own, is informative rather than conclusive. It’s also strictly a local-network identifier: a MAC address never travels past the first router hop, so it only ever tells you about a device on your own segment, never about something several hops away. If you suspect deliberate spoofing rather than just an unidentified device, look for a stronger signal than the MAC alone — two devices intermittently fighting over the same address is a concrete sign, as is a device’s traffic pattern not matching what its claimed vendor’s product would normally do. See ARP spoofing for the related local-network attack this overlaps with, and DHCP for how the lease information you’re cross-referencing is assigned in the first place.

What should you do next?

Open AdminKit’s MAC vendor lookup and work through the unfamiliar address from your router’s client list. If what you actually want to confirm is whether a device is exposing something to the internet rather than just identifying it, follow up with AdminKit’s open ports check on your own public IP. This guide is part of AdminKit’s IP & network cluster of network identification guides and tools.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

I see an unfamiliar MAC address in my router's device list — is it definitely an intruder?

Usually not. Most unfamiliar entries turn out to be a device you own but don't recognize by its raw MAC address — a smart plug, a TV, a guest's phone, a new IoT gadget, or one that reconnected under a different randomized address. Treat it as 'unidentified' first and work through identification before assuming it's unauthorized; disconnecting or changing credentials is a step for after you've confirmed it's actually not yours, not the first reaction.

Where do I actually find the MAC addresses connected to my network?

Most home routers and access points have a 'connected devices,' 'DHCP clients,' or 'attached devices' page in their admin interface listing each client's IP, hostname (if any) and MAC address. From a device already on the same network, the command `arp -a` (Windows, macOS and Linux all support it) lists MAC-to-IP mappings for hosts it has recently communicated with — useful as a cross-check against the router's own list.

Why does one of my 'unknown' devices show no vendor at all?

Two different causes look identical in the result: the address may be locally-administered or randomized, meaning it was never drawn from an IEEE-assigned manufacturer block in the first place (common for phones and laptops — see RFC 9542), or the prefix may be a recent assignment that IEEE's published registry doesn't list. Either way, 'no vendor found' doesn't mean suspicious; it's the expected result for a huge share of modern personal devices, which randomize their Wi-Fi MAC address per network by default.

Can someone spoof a MAC address to make a rogue device look like a trusted one?

Yes — a MAC address is easy to change in software on most operating systems, so a vendor match or an address that matches a device you own is informative, not proof. If you suspect active spoofing rather than just an unidentified device, cross-check more than the MAC: the IP's DHCP lease time, the device's actual traffic pattern, and whether two devices are claiming the same address at once (which usually shows up as intermittent connectivity for the legitimate one).

What should I actually do once I've confirmed a device isn't mine?

Change your Wi-Fi password (this disconnects every device until they re-enter the new one, including the unauthorized one) and, if your router supports it, move to WPA3 or at least WPA2 with a strong passphrase if it wasn't already. MAC-based blocking alone is a weak long-term control, since a MAC address is easy to spoof back to an allowed one once an attacker learns it; a strong, rotated Wi-Fi password is the control that actually removes access.

Does a vendor match tell me which specific device, or even which room, it's in?

No — it identifies the registered manufacturer of the address's prefix, not a specific unit, and manufacturers routinely reuse the same prefix across many unrelated products. A vendor match narrows 'unknown device' down to a plausible category (router, camera brand, IoT vendor) that you then confirm using other context you already have, like the device's IP range, hostname, or where you can see it join and drop from the network.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.