How do you read a MAC address vendor lookup result?
AdminKit's MAC vendor lookup result tells you one of three things: a matched manufacturer name means the address's first three bytes, its OUI, were factory-assigned to that company by IEEE; no match means the prefix isn't in the public registry; and a locally-administered or randomized flag means the address was never vendor-assigned, so there is no manufacturer to find.
By AdminKit team, Netbase JSC · Updated
Key takeaways
- A MAC vendor lookup has three possible outcomes: a matched manufacturer, no match for a prefix that looks factory-assigned, or a locally administered (often randomized) address that has no manufacturer at all.
- A match names the company that registered the prefix with IEEE. It doesn’t name the product, and many devices from one maker share a prefix.
- You can spot a locally administered address by eye: if the second hex digit is 2, 6, A or E, there is no vendor to find.
- Modern phones and laptops use randomized Wi-Fi addresses by default, so OUI lookup works best for fixed devices such as routers, cameras and printers.
- A MAC address only means something on your own local network segment, and it can be changed in software.
What can a MAC vendor lookup result tell you?
AdminKit’s MAC vendor lookup takes the MAC address you enter and checks its first three bytes — the OUI — live against AdminKit’s own copy of the IEEE OUI registry via its Check API (GET /v1/tools/mac-vendor). The result you get back is always one of three distinct things, and reading it correctly means telling them apart rather than treating “no vendor shown” as a single catch-all failure:
- A matched vendor name — the OUI prefix is a real, IEEE-registered assignment, and the result shows the company it was issued to.
- No match on a prefix that looks like it should be real — the first byte’s addressing bits look globally-assigned, but the specific prefix isn’t in the published registry (yet, or at all).
- A locally-administered or randomized flag — the address was never drawn from an IEEE-assigned block in the first place, so there is nothing to look up.
Each of these points to a different conclusion about the device the address came from, covered below.
Which fields does the result contain?
The lookup returns the same handful of fields every time, whether or not a vendor was found:
| Field | Meaning |
|---|---|
mac | Your input, normalized to upper-case hex with colons |
is_oui_only | true if you entered only a 3-byte prefix rather than a full address |
found / organization | Whether a registered vendor matched, and its name as IEEE publishes it |
matched_prefix / assignment | The registry prefix that matched, and its block type: MA-L, MA-M or MA-S |
locally_administered / multicast | The two flag bits in the first byte (see below) |
Example response for a randomized phone address (illustrative input)
{
"mac": "DA:A1:19:00:00:01",
"is_oui_only": false,
"found": false,
"organization": null,
"matched_prefix": null,
"assignment": null,
"locally_administered": true,
"multicast": false
}
Here found is false and locally_administered is true: the second hex digit is A, so the address was generated locally and no vendor lookup could succeed.
What does a matched vendor name confirm?
Every Ethernet or Wi-Fi interface’s MAC address starts with three bytes (24 bits) assigned by the IEEE Registration Authority to the manufacturer that requested them — the OUI, or in IEEE’s current naming, an MA-L (MAC Address Block Large) assignment. IEEE also issues two smaller block sizes for manufacturers needing fewer addresses: MA-M (28-bit prefix) and MA-S (36-bit prefix, drawn from an OUI-36). AdminKit’s lookup matches against all three sizes, so a hit tells you which exact tier of assignment the prefix came from as well as the registered company name.
| Block | Prefix length | Addresses per block | Prefix written as |
|---|---|---|---|
| MA-L | 24 bits | 16,777,216 | 6 hex digits |
| MA-M | 28 bits | 1,048,576 | 7 hex digits |
| MA-S | 36 bits | 4,096 | 9 hex digits |
The lookup tries the longest prefix first, because an MA-M or MA-S block is a separate, more specific assignment than the MA-L range its digits happen to fall in. AdminKit’s copy of the registry was built from IEEE’s three public CSV files on 2026-10-28 and holds 54,327 prefixes across the three block sizes.
What a match does not tell you is which specific physical device the address belongs to. A manufacturer can, and routinely does, reuse the identical OUI across an entire product catalog — routers, switches, cameras, printers, smart plugs — since IEEE assigns the prefix to the company, not to a product line. If a lookup tells you “Vendor X” and your network has three devices showing that same prefix, you’ve learned the maker of all three, not which one is the router versus the camera versus the printer. Combine the vendor name with other context you already have — IP address, hostname, DHCP lease name, or where the device physically sits on your network — to pin down which device is which.
The registered company is also not always the brand on the box: if a device uses a network module bought from another company, its address can come from that supplier’s block rather than the brand’s own.
Why does a genuine-looking address return no match?
Sometimes a lookup returns no vendor even though the address’s addressing bits look like a normal, globally-assigned prefix (the universal/local bit is zero, so it isn’t locally-administered — see below). This almost always means the specific prefix simply isn’t in IEEE’s published registry: IEEE adds new MA-L, MA-M and MA-S assignments on an ongoing basis, and AdminKit’s copy reflects whatever the registry publishes, so an address using a very recently issued block can briefly show no match even though it’s a perfectly genuine, factory-assigned address. This is a gap in registry coverage, not evidence that the address itself is fake or suspicious.
Why does a locally administered address have no vendor?
The second-least-significant bit of a MAC address’s first byte is the universal/local (U/L) bit, defined in RFC 9542 (§2.1.1, formerly RFC 7042): a zero means the address is a global one under the control of whoever owns the IEEE-assigned prefix, while a one means IEEE itself classifies it as a local identifier, generated outside any vendor assignment. IEEE 802c’s Structured Local Address Plan further subdivides that local address space into ranges for different uses. A locally-administered address was never drawn from a manufacturer’s registered block in the first place, so when AdminKit’s lookup flags one, reporting no vendor is the correct answer, not a failed lookup — there is genuinely nothing to find.
The least-significant bit of the same byte is the individual/group bit: one means a multicast (group) address, which a single device’s interface doesn’t use as its own source address. Both bits sit in the second hex digit of the address, so you can read them without any tool:
| Second hex digit | U/L bit | I/G bit | Meaning |
|---|---|---|---|
| 0, 4, 8, C | 0 | 0 | Globally assigned, unicast: a vendor lookup can match |
| 2, 6, A, E | 1 | 0 | Locally administered, unicast: often a randomized address, no vendor |
| 1, 5, 9, D | 0 | 1 | Multicast from a registered block |
| 3, 7, B, F | 1 | 1 | Locally administered multicast |
This is also exactly what happens with randomized MAC addresses, which set the same U/L bit to mark themselves as local: Android 10 and later randomizes the Wi-Fi MAC address used per network by default, and iOS/iPadOS 14 and later does the same with its Private Wi-Fi Address feature (as of iOS/iPadOS 18, users can additionally choose a fixed-per-network or rotating-every-two-weeks private address), with Windows offering an equivalent opt-in “random hardware addresses” setting. These defaults exist specifically to stop the kind of passive tracking an OUI lookup enables — a modern phone presenting a different, vendor-less address to every network it joins is working as intended, not malfunctioning. Fixed infrastructure like routers, switches, printers and most IP cameras still ships with its real factory-assigned MAC and has no reason to randomize it, which is why OUI lookup remains reliable for identifying that kind of device on your network even as it becomes unreliable for personal phones and laptops. See randomized and locally-administered MAC addresses explained for how that per-network randomization actually works.
Android’s MAC randomization documentation describes the mechanism directly: Android “randomizes the address by setting the locally administered bit to 1, and the unicast bit to 0. The other 46 bits are randomized.” Apple’s private Wi-Fi address page explains that each device identifies itself to each network using a different Wi-Fi address and lists the Off, Fixed and Rotating choices in iOS 18 and later.
What can’t this lookup confirm?
This guide on reading a MAC vendor lookup result is part of AdminKit’s DNS cluster, alongside the other local-network identification guides it links to below.
A MAC address never leaves the local network segment it was sent on — routers replace the source MAC with their own at every hop — so a MAC address is only ever meaningful for identifying a device on the same local network you’re checking it from, never for a device several hops away or one you only saw mentioned in a remote server’s logs. It’s also easy to change in software (MAC spoofing) on most operating systems, so a vendor match is informative, not a cryptographic guarantee of origin. Use a MAC vendor lookup to get a reliable, well-sourced hint about the maker of an unfamiliar device sitting on your own LAN — a router, a camera, an IoT gadget with no helpful hostname — not as proof of exactly which product, or whose, it is. See using MAC vendor lookup to spot a rogue device for the full walkthrough of combining a result like this with other context to actually identify an unfamiliar entry in your router’s client list. If you want to see how this free, no-account lookup stacks up against other free options, AdminKit’s comparison of free MAC vendor (OUI) lookup tools lines up macvendors.com and maclookup.app’s own published randomization and block-size details against what’s described above.
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
What does a matched vendor name in the result actually confirm?
Only that the address's first three bytes (24 bits) — its OUI — were assigned by the IEEE Registration Authority to that specific company. It confirms the registered owner of a prefix, not which physical product the address belongs to: a manufacturer can and does reuse the same OUI across routers, cameras, printers and many other unrelated product lines, so the result narrows down the maker, not the model.
Why does the lookup return no vendor for an address that looks like a normal MAC address?
Two different reasons produce the same empty result, and the lookup result distinguishes them: either the second-least-significant bit of the first byte marks the address as locally-administered or randomized (see the next question), or the prefix is simply missing from IEEE's public registry — new assignments are added over time, and an address using a very recently issued block can briefly have no match even though it is a genuine, factory-assigned prefix.
What does a 'locally-administered' or 'randomized' flag mean, and why is there no vendor for it?
Every MAC address has a universal/local bit in its first byte: zero means the address was globally assigned by IEEE to a manufacturer, one means it was generated locally instead, outside any IEEE assignment, as defined in RFC 9542 and the IEEE 802c Structured Local Address Plan. A locally-administered or randomized address was never drawn from a vendor's registered block, so there is no OUI to resolve and the lookup correctly reports no manufacturer — this is expected behavior, not a failure of the tool or the registry.
Why does my phone's MAC vendor lookup fail, but my router's succeeds?
Android 10+ and iOS/iPadOS 14+ both randomize the MAC address a phone uses per Wi-Fi network by default, specifically to prevent the kind of passive tracking an OUI lookup enables, so a phone usually presents a locally-administered address with no vendor to find. Fixed infrastructure — routers, switches, printers, IP cameras and most other IoT devices — still ships with its real, factory-assigned MAC by default, which is why OUI lookup works reliably for those device types but not for a modern phone's per-network Wi-Fi address.
Can a vendor name tell me exactly which device on my network this is?
It narrows down the maker, not the device. If a lookup shows a specific router or camera manufacturer among several candidates on your network, that is a strong hint about which entry is which, especially combined with the device's IP address, hostname or DHCP lease name. But two different devices from the same manufacturer share the same OUI, so treat a vendor match as one clue to combine with others, not a unique identifier on its own.
Can I trust a MAC address I see in a log or a lookup result to be genuine?
Only as much as you trust whatever reported it. A MAC address is easy to change in software (a practice called MAC spoofing) on most operating systems, and it never leaves the local network segment — routers do not forward it past the first hop — so a MAC address seen in a remote server's logs is not the originating device's real address at all, only the last hop's. Treat a MAC vendor lookup as useful for identifying a device's maker on your own local network, not as a trustworthy identifier captured from anywhere further away.
Sources
- IEEE — Public OUI/MA-L registry
- IEEE Registration Authority — MA-L, MA-M, MA-S assignments
- RFC 9542 — IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters, §2.1.1
- Android Open Source Project — MAC randomization behavior
- Apple Support — Use private Wi-Fi addresses on Apple devices
Want AdminKit to watch this for you?
Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.
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.