DevTools Logo

MAC Address Lookup

MAC Address Lookup

Resolve the vendor behind a MAC address from its OUI prefix using a bundled subset of the IEEE registry — with unicast/multicast and UAA/LAA flags, entirely in your browser.

Colon, dash, bare (AABBCC…) or Cisco dot notation — detected automatically.

Try a sample:

Examples

Identify a Wi-Fi device

Input
00:1B:63:84:45:E6
Output
Apple · OUI 00:1B:63 · unicast · UAA

A textbook burned-in NIC: the prefix resolves to the vendor and both signal bits read clean.

Recognize a randomized phone MAC

Input
02-11-22-33-44-55
Output
Unknown vendor · unicast · LAA

The x2 prefix carries the locally-administered bit — the address was software-set, typical of phone MAC randomization.

Spot a multicast group address

Input
01:00:5E:00:00:FB
Output
multicast · I/G bit set

This address is an IPv4 multicast group (mDNS), not a physical interface — the lookup flags it from the I/G bit.

About this tool

Every network interface card leaves the factory with a Media Access Control address burned into it, and the first half of that address is not random — it is an Organizationally Unique Identifier (OUI) assigned by the IEEE Registration Authority to a specific manufacturer. The MAC Address Lookup takes the address you paste, normalizes it, extracts that 24-bit OUI prefix, and matches it against a bundled subset of the IEEE MA-L registry — 292 common manufacturers and 12,925 OUI prefixes, including Apple, Samsung, Cisco, Intel, Dell, HP, Huawei, TP-Link, Ubiquiti, Raspberry Pi and Espressif — so you can go from an anonymous device name in a router table to an actual company in a second. The data comes from the IEEE Registration Authority, it ships with the tool, and the whole computation happens in your browser, so no address you type is ever sent to a server.

The tool accepts all four notations you will meet in the wild: colon-separated (00:1B:63:84:45:E6, the Linux and IEEE style), dash-separated (00-1B-63-84-45-E6, common on Windows), bare hex (001B638445E6, how databases store it) and Cisco's dotted form (001b.6384.45e6, which pairs hex quartets with dots). It detects the format automatically, validates that the input is exactly twelve hexadecimal digits, and can re-emit the same address in any of the three separated notations — handy when pasting between tools that refuse each other's dialects.

Beyond the vendor, two signal bits in the first byte tell you what kind of address you are looking at. The I/G bit separates unicast addresses (one physical NIC) from multicast addresses (a group subscription, like the 01:00:5E IPv4 multicast range or 33:33 IPv6 multicast prefix). The G/L bit separates universally administered addresses — genuinely burned in by the vendor — from locally administered addresses, which software set on purpose: modern phones randomize their Wi-Fi MACs per network, virtual machines and containers frequently assign x2/x6/xA/xE prefixes, and spoofing tools set the bit to dodge network filters. Seeing the LAA bit set tells you instantly that the vendor prefix may describe software, not hardware.

Honesty matters when a prefix is not in the registry: the tool reports "unknown vendor" rather than guessing a nearby entry, because IEEE assignments number in the tens of thousands and this tool bundles only the 24-bit MA-L prefixes of common manufacturers, not the complete MA-L listing or the MA-M and MA-S sub-blocks. Locally administered addresses (phone randomization, VMs, Docker's 02:42 prefix) are never matched to a vendor at all, because their prefix is not an IEEE assignment. The lookup stays entirely local — no network request leaves your device — and if you need to generate test MACs instead of looking real ones up, the MAC Address Generator sits in the same toolbox; for the subnet arithmetic around the addresses you find, the Subnet Calculator is one click away.

What this tool does not do

  • The bundled registry is a subset of the IEEE MA-L (24-bit) assignments — 292 common vendors, 12,925 prefixes — not every MAC address. Unknown prefixes are reported honestly, and MA-M/MA-S sub-allocations are not included.
  • EUI-64 and 64-bit addresses (16 hex digits) are outside this tool's scope; it validates 48-bit addresses of exactly twelve hex digits.
  • The lookup reads an address you already have — it cannot discover the MAC of a device you do not control or scan a network.

How to use this tool

  1. Paste the MAC address

    Enter the address in any notation — colon, dash, bare or Cisco dot. The format is detected automatically and validated to twelve hex digits.

  2. Read the vendor and OUI

    The result card shows the manufacturer behind the 24-bit OUI prefix, the prefix itself, and an honest "unknown vendor" when the prefix is not in the bundled registry.

  3. Check the signal bits

    Read the unicast/multicast flag (I/G bit) and the UAA/LAA flag (G/L bit) to tell real hardware from multicast groups, randomized phones or spoofed interfaces.

  4. Copy in your notation

    Pick colon, dash or Cisco dot output, then copy the normalized address or the full details summary for your ticket or report.

Use cases

Auditing a DHCP client table

Paste each MAC from your router's lease list to see which manufacturer owns every device on the network — and which entries are randomized or spoofed.

Normalizing mixed-notation inventories

Re-emit addresses from spreadsheets, Cisco configs and Windows exports in one consistent notation before importing them anywhere else.

Troubleshooting network filters

Check the UAA/LAA bit when a MAC ACL blocks a device: a locally-administered address usually means randomization or a virtual interface, not the sticker value.

MAC address structure

FieldWhat it carries
OUI (first 24 bits)IEEE-assigned manufacturer identifier, e.g. 00:1B:63 = Apple
NIC (last 24 bits)Serial number the vendor assigns within its OUI
I/G bit (byte 1, bit 0)0 = unicast (one NIC), 1 = multicast (group address)
G/L bit (byte 1, bit 1)0 = UAA (burned-in), 1 = LAA (locally/spoof-set)
Colon notation00:1B:63:84:45:E6 — IEEE, Linux, most documentation
Dash notation00-1B-63-84-45-E6 — Windows ipconfig style
Bare notation001B638445E6 — database and inventory style
Cisco dot notation001b.6384.45e6 — IOS show-interface style

The tool detects all four input notations and re-emits the address in any of the three separated ones.

Common mistakes

Mistake:Treating every lookup result as the true hardware vendor.

Fix:Phones randomize Wi-Fi MACs and VMs assign arbitrary locally-administered addresses — when the LAA bit is set, the OUI describes software choice, not the manufacturer.

Mistake:Assuming an unknown prefix means a fake address.

Fix:The bundled registry is a curated subset of the IEEE database; an "unknown vendor" result means the prefix simply is not listed here — verify against the full IEEE registry before concluding anything.

Mistake:Dropping leading zeros when converting notations.

Fix:Each byte needs both hex digits — 001b.6384.45e6 pasted as 1b.6384.45e6 is five bytes short; let the tool normalize the notation instead of editing digits by hand.

Frequently asked questions

What is an OUI and where does the vendor name come from?

OUI stands for Organizationally Unique Identifier: the first 24 bits (first three bytes) of a MAC address, assigned by the IEEE Registration Authority to a specific manufacturer. Apple owns 00:1B:63, for example, so any address starting with those bytes describes an Apple-assigned NIC. The remaining 24 bits are a serial number the vendor hands out within its own OUI. This tool matches your prefix against a bundled subset of the IEEE registry (292 common vendors, 12,925 OUI prefixes), so the lookup runs locally in your browser with no network request.

Why does a valid MAC address come back as "unknown vendor"?

The IEEE registry contains tens of thousands of OUI assignments across its MA-L, MA-M and MA-S programs, and this tool bundles only a subset — the 24-bit MA-L prefixes of common manufacturers — so it does not cover every MAC address. An honest tool cannot name a vendor it has no data for. "Unknown vendor" means exactly that: the prefix is structurally valid but not in the bundled subset (or, for locally administered addresses such as Docker's 02:42, was never an IEEE assignment). That is different from an invalid address, which the tool reports separately when the input is not twelve hexadecimal digits. For an exhaustive match, cross-check unknown prefixes against the IEEE's public search.

What do the unicast/multicast and UAA/LAA flags mean?

Two bits in the first byte classify the address. The I/G bit (bit 0) says whether the address targets one interface (unicast) or a group subscription such as IPv4's 01:00:5E multicast range (multicast). The G/L bit (bit 1) says whether the address is universally administered — genuinely burned in by the vendor — or locally administered, meaning software set it deliberately. Seeing LAA set is the tell-tale of a randomized phone MAC, a virtual machine interface or a spoofed address.

Why do phone MAC addresses stop matching their real vendor?

Modern mobile operating systems randomize the Wi-Fi MAC address per network for privacy, and randomized addresses use locally-administered bits rather than the manufacturer's OUI. The lookup will show an unknown or unrelated vendor plus the LAA flag — that flag is the useful signal, because it tells you the address was software-chosen rather than factory-assigned. If you need the device's real identity, read its MAC from the settings screen where the randomization option lives.

Which MAC address formats does the tool accept?

All four notations in common use: colon-separated (00:1B:63:84:45:E6), dash-separated (00-1B-63-84-45-E6), bare hexadecimal (001B638445E6) and Cisco's dotted form (001b.6384.45e6). The format is detected automatically — separators, not case, decide the dialect — and the input must normalize to exactly twelve hexadecimal digits, which is what a 48-bit MAC address is. The result can be re-emitted in colon, dash or Cisco dot notation so you can paste into whichever tool expects that style.

Is my MAC address sent anywhere when I look it up?

No. The parser, the OUI registry and the bit decoding all run inside your browser tab, and no network request carries your input anywhere. The address persists only in your own browser's local storage between visits so the field refills on return, and the Clear control on the restored-input notice wipes both the field and the saved copy. Nothing is logged server-side because nothing reaches a server.

References & standards