MAC Address Vendor OUI Lookup & Formatter

Inspect MAC addresses, decode IEEE OUI vendor identifiers, convert formats (Colon, Hyphen, Dot, Plain), and check Unicast/Multicast bits client-side.

🛡️ 100% Client-Side Privacy: Your network & configuration payloads are processed locally in your browser memory and never transmitted across any server.
MAC Address Input String (e.g. 00:1A:2B:3C:4D:5E) (Ctrl+Enter) 0 chars
Processed Output / Technical Report 0 chars

MAC Address OUI: IEEE EUI-48 Architecture & Hardware Vendor Identification

Media Access Control (MAC) addresses are 48-bit unique identifiers assigned to Network Interface Controllers (NICs). The first 24 bits represent the Organizationally Unique Identifier (OUI) assigned by IEEE to identify the hardware manufacturer.

Infrastructure Parameters & Protocol Matrix

Directive / Configuration KeyProduction Bound & Recommended Setting
IEEE StandardIEEE 802-2014: Standard for Local and Metropolitan Area Networks
Address Format48-bit (EUI-48): 6 octets separated by colons or hyphens (XX:XX:XX:XX:XX:XX)
OUI Block SizeMA-L (24-bit OUI: 16M devices) | MA-M (28-bit) | MA-S (36-bit)
Special Control BitsBit 0 (I/G): Unicast (0) vs Multicast (1) | Bit 1 (U/L): Global (0) vs Local (1)

Production Deployment & Reliability Checklist

Infrastructure Configuration & Command Examples

Python 3 OUI Lookup Function

def parse_mac_oui(mac_address: str):
    clean_mac = mac_address.replace(":", "").replace("-", "").upper()
    oui = clean_mac[:6]
    first_byte = int(clean_mac[:2], 16)
    is_multicast = bool(first_byte & 0x01)
    is_locally_administered = bool(first_byte & 0x02)
    return {"oui": oui, "multicast": is_multicast, "local_admin": is_locally_administered}

Linux CLI Inspection

# View network interface MAC addresses
ip link show

# Check local ARP table for neighbor MAC addresses
ip neigh show

Production Pipeline Automation & Configuration Hygiene

Managing modern infrastructure manifests requires automated linting, schema validation, and strict environment parity across development, staging, and production clusters. Integrate declarative validation utilities (such as yamllint, kubeconform, or shellcheck) directly into CI/CD pipelines to intercept syntax regressions before provisioning cloud resources. Never commit static authentication credentials into repository manifests; leverage dynamic secret injection, scoped service accounts, and GitOps synchronization controllers to guarantee immutable delivery. Establish automated canary deployments with metric-based auto-rollback triggers to prevent faulty infrastructure rollouts.

Official IETF RFCs & Systems Standards