Are generated MAC addresses real / tied to actual devices?
No — randomly generated for testing, won't return a match in a vendor lookup unless it happens to collide with a real registered prefix.
Generate to see MAC addresses here.
Generate random MAC addresses locally, with control over the vendor OUI prefix and the unicast/multicast and universal/local administration bits.
Addresses are generated locally using the Web Crypto API. Nothing is uploaded or stored.
No — randomly generated for testing, won't return a match in a vendor lookup unless it happens to collide with a real registered prefix.
Yes — type a vendor name (Apple, Cisco, VMware, and others from the same database as MAC Address Lookup) into the Vendor OUI search box and pick a match to fix its OUI as the first 3 bytes; the remaining 3 stay random for each address you generate. With a vendor picked, the Address Type and Administration controls lock to that vendor's real bits instead of the manual toggles, since overriding them would corrupt the prefix — clear the selection to go back to a fully random address.
Colon- or hyphen-separated, or Cisco dot notation (aabb.ccdd.eeff) — in upper- or lowercase.
Up to 50 — pick 1, 5, 10, 20, or 50.
The second bit of the first byte flags this — universal addresses use a real IEEE-assigned OUI; local ones are self-assigned and won't map to any vendor. Picking a vendor prefix locks this control, because the prefix already fixes that bit: almost every IEEE block reads Universal, but 18 of the 40,020 registered OUIs are historical assignments that carry the local bit anyway (DEC's AA:00:00–AA:00:04, 3Com's 02:C0:8C, and a handful of other 1980s registrations), and those lock it to Local. The self-assigned ranges some tools mint for virtual interfaces — Docker's 02:42:AC, QEMU/KVM's 52:54:00 — are not IEEE registrations at all, so they are not in the picker; choose Local with no vendor prefix to generate that kind.
No, entirely client-side.