Understanding MAC Address Formats and Bit-Level Analysis
A MAC (Media Access Control) address is the 48-bit hardware identifier permanently assigned to every network interface card during manufacturing. Ethernet switches use MAC addresses to build their forwarding tables, DHCP servers bind IP leases to them, and 802.1X port-based authentication validates them before granting network access. Every device on a local segment — laptops, phones, printers, IoT sensors, virtual machines — carries at least one MAC, making it the foundational Layer 2 identity. This MAC address formatter converts between the four standard notations (colon-separated for Linux/macOS, hyphen-separated for Windows, Cisco dot-grouped for IOS CLI, and bare hex for scripts and databases), validates the input with specific error messages, and performs deterministic bit-level analysis that reveals how the address will behave on the wire.
The 48-bit address splits into two functional halves. The first 24 bits form the OUI (Organizationally Unique Identifier), assigned by the IEEE to a hardware manufacturer; the last 24 bits are the vendor-specific NIC identifier, allocated by that manufacturer to each individual interface. More critically, the first octet encodes two flag bits in its two least-significant positions. Bit 0 (the LSB) is the Individual/Group (I/G) flag: a value of 0 means the frame targets a single unicast destination, while 1 means multicast (a group of receivers, including broadcast FF:FF:FF:FF:FF:FF). Bit 1 is the Universal/Local (U/L) flag: 0 indicates the address was assigned globally by the IEEE through the OUI system, while 1 marks it as locally administered — set by software rather than burned in at the factory. IEEE 802-2014 §8.1 defines these semantics. The tool displays the first octet in binary with both flag bits colour-highlighted and labelled, giving you an instant read on whether a MAC is manufacturer-issued or randomised.
As a worked example, take the MAC address 00:1A:2B:3C:4D:5E. Converting format is straightforward: hyphen notation gives 00-1A-2B-3C-4D-5E, Cisco dot notation produces 001A.2B3C.4D5E, and bare hex is 001A2B3C4D5E. The first octet is 0x00, which in binary is 00000000 — I/G bit is 0 (unicast) and U/L bit is 0 (globally unique, so this OUI was assigned by the IEEE to a registered vendor). To derive the EUI-64 interface identifier used by IPv6 Stateless Address Autoconfiguration (SLAAC, defined in RFC 4291 §2.5.1), the algorithm splits the 6-byte MAC after the third octet, inserts the fixed bytes FF:FE to extend it to 8 bytes, then flips the U/L bit: 0x00 XOR 0x02 = 0x02. The resulting EUI-64 is 02:1a:2b:ff:fe:3c:4d:5e — this becomes the 64-bit interface identifier that a host concatenates with its /64 network prefix to form a full 128-bit IPv6 address without needing DHCPv6.
Network engineers encounter format conversion daily: copying a MAC from Linux ifconfig output (colon notation) into a Cisco port-security command (dot notation), or pasting a Windows ipconfig result (hyphen notation) into a DHCP reservation that requires bare hex. Virtualisation administrators generate locally-administered MACs for VMs so they never collide with real hardware OUIs. Security analysts check the U/L bit to determine whether a captured address is a permanent manufacturer identifier (useful for device tracking) or a privacy-randomised temporary address — since 2014, Apple iOS, Android, and Windows all randomise the MAC when scanning for Wi-Fi networks, always setting the locally-administered bit to avoid claiming a real OUI. Forensic investigators use the EUI-64 derivation in reverse: given an IPv6 SLAAC address from a firewall log, they extract the embedded MAC to identify the originating physical NIC.
A common pitfall is assuming the OUI directly names the device manufacturer visible to a consumer — in practice, many devices carry the OUI of the chipset vendor (Qualcomm, Intel, Broadcom) rather than the product brand. This tool extracts and displays the OUI and NIC-specific halves but deliberately does not resolve them to a vendor name. The reason is simple and stated honestly: the IEEE MA-L registry that maps OUIs to companies updates on an ongoing basis, and any offline copy bundled into a web tool becomes stale within weeks, returning confident but incorrect vendor identifications. Rather than risk misinformation, the tool links directly to the authoritative IEEE OUI lookup at standards-oui.ieee.org where the data is always current. The random MAC generator produces a valid locally-administered unicast address by setting bit 1 of the first octet to 1 and clearing bit 0 to 0 — the identical bit pattern that operating-system privacy randomisation uses, making the generated address safe for test environments and virtual machines. Every operation runs entirely in your browser through pure JavaScript arithmetic; no MAC address, partial or complete, is ever transmitted over the network.
