MAC Address Format: OUI, Local Addresses and Test Examples

Read a 48-bit MAC address, distinguish OUI prefixes from local addresses, and use documentation examples with explicit parser and collision rules.

By Vincent RuanPublished June 25, 2026Last updated September 6, 20264 min read

Illustration for this article: Read a 48-bit MAC address, distinguish OUI prefixes from local addresses, and use documentation examples with explicit parser and collision rules.

MAC address format for Ethernet and Wi-Fi is six octets, or 48 bits. 00:00:5e:00:53:01 is an example from the IANA documentation block. It labels a network interface on a local link; it is not a person identifier or proof of a device manufacturer [rfc7042].

Read the format before looking up an OUI

NotationValueNormalization target
Colon separated00:00:5e:00:53:0100:00:5e:00:53:01
Hyphen separated00-00-5E-00-53-0100:00:5e:00:53:01
Dotted groups0000.5e00.530100:00:5e:00:53:01
Three spellings of the same documentation address.

Pick which input spellings your application accepts, validate the complete format, and then normalize. Blindly deleting punctuation can turn malformed input into an accepted address. Do not strip arbitrary characters and assume the remaining twelve digits prove the original input was valid.

What the first-octet bits mean

The least significant bit of the first octet is I/G: 0 for an individual address and 1 for a group address. The next bit is U/L: 0 for universal administration and 1 for local administration. For a locally administered unicast address, (firstByte & 0x03) === 0x02 [ieee-guidelines].

ExampleI/GU/LInterpretation
00:00:5e:00:53:0100Unicast documentation example
02:00:00:00:00:0101Locally administered unicast; may be used by a real interface
01:00:5e:90:10:0110Multicast documentation example
ff:ff:ff:ff:ff:ff11Broadcast; not a unicast device address
Bit checks for common fixture categories. These checks do not establish ownership.

Why an OUI lookup may not identify the hardware

IEEE registries describe assignments to organizations. The familiar first-three-byte lookup covers MA-L assignments, but smaller allocation products use longer prefixes. Lookup software needs the matching registry and longest applicable prefix; it should return unknown for a local address instead of asserting a vendor [ieee-ra].

RegistryAssigned prefix bitsAddresses per assignment
MA-L2416,777,216
MA-M281,048,576
MA-S364,096
Assignment sizes from IEEE registration documentation; counts follow 2^(48 − prefix length).

Even a registry match identifies the registered organization, not necessarily the retail brand or the current user. A software-configured address is another reason to treat vendor lookup as descriptive metadata rather than authentication.

Documentation addresses versus working test interfaces

For published examples, use the 256 unicast values from 00:00:5e:00:53:00 through 00:00:5e:00:53:ff. For group-address examples, RFC 7042 also provides 01:00:5e:90:10:00 through 01:00:5e:90:10:ff. Those are specific documentation allocations [rfc7042].

For a VM or interface on an isolated test network, locally administered unicast addresses are appropriate when you control allocation. They are also used by real devices: Apple documents private Wi-Fi addresses for its hardware [apple-private]. A local bit cannot distinguish synthetic traffic from production traffic.

A worked local-address mask

Start with six random bytes. For a first byte of hexadecimal AD, applying (0xad & 0xfc) | 0x02 produces AE. Clearing the bottom two bits and then setting bit 1 leaves a local unicast address. The possible second hexadecimal digits are 2, 6, A and E.

StepBinary first byteHex
Input10101101AD
AND FC10101100AC
OR 0210101110AE
Calculated bit transformation; the remaining five bytes are unchanged.

This leaves 46 variable bits, or 70,368,744,177,664 possible local unicast values. That is a large space, not a uniqueness guarantee. Keep an allocation set for a test network and retry on duplicates. Fixed sequential values may be easier to inspect than random ones in a small isolated lab.

MAC parser test cases and expected results

InputExpected resultReason
00-00-5E-00-53-0100:00:5e:00:53:01Case and separator normalization
0000.5e00.530100:00:5e:00:53:01Dotted grouping
00:00:5e:00:53RejectOnly five octets
00:00:5e:00:53:ggRejectNon-hexadecimal characters
00:00-5e:00:53:01Reject under this policyMixed separators
ff:ff:ff:ff:ff:ffParse; reject for a unicast-interface fieldSyntax and interface policy are separate
02:00:00:00:00:01 repeated twiceParse; flag duplicate in the same test networkLocal administration does not ensure uniqueness
Example application policy: accept complete colon, hyphen or dotted formats; store lowercase colon notation.

Fakenamely’s current identity and bulk schemas do not export a MAC field. Use these examples or implement the mask in your fixture builder. Pair it with the IP range guide for Layer 3 tests; keep IP routing policy separate from MAC format validation.

References & sources

  1. RFC 7042: IEEE 802 parameters and documentation values — IETF
  2. Guidelines for EUI, OUI and CID — IEEE Registration Authority
  3. IEEE Registration Authority and assignment registries — IEEE
  4. Use private Wi-Fi addresses on Apple devices — Apple

Frequently asked questions

What is the format of a MAC address?

For Ethernet and Wi-Fi, it is a 48-bit value written as six hexadecimal octets, for example 00:00:5e:00:53:01. Hyphens and three groups of four hexadecimal digits are also common display formats.

Does a locally administered MAC avoid all real devices?

No. Physical devices and virtual interfaces can use locally administered MACs, including private Wi-Fi addresses. Setting the local bit avoids claiming a universal assignment; it does not guarantee uniqueness or identify a test device.

Which MAC addresses are reserved for documentation?

RFC 7042 reserves 00-00-5E-00-53-00 through 00-00-5E-00-53-FF for unicast documentation examples. This block has 256 values. It is distinct from the locally administered address space.

Can the first three bytes always identify a vendor?

No. A 24-bit OUI applies to MA-L assignments. MA-M and MA-S registrations use longer prefixes, and a locally administered address cannot reliably identify its hardware vendor from the prefix.

How do I create a locally administered unicast MAC?

Generate six bytes, then set the first byte to (byte & 0xfc) | 0x02. Format all six bytes as two hexadecimal digits each. Track allocated values and reject duplicates within the network you control.

More on technical identifiers

Put this to work