Vendor lookup · Address normalization

MAC address API

Give your network inventory
a consistent address.

Turn a MAC address into one standard format and look up its registered vendor. Local and multicast flags help you interpret the result.

Look up a MAC address

Try it

One request. Complete JSON.

An address you can use.

Validate the format, normalize it and read the registered organization. The same response keeps local addresses, multicast and invalid input clear.

Look up the registered vendor.

A global unicast address with a known assignment. The vendor names the registered assignment holder.

Request

curl "https://api.parseapi.com/mac/00:23:DF:84:45:E6" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Parse-Version: 2.0.0"

Example response

JSON200 OK
{
  "mac": "00:23:DF:84:45:E6",
  "valid": true,
  "vendor": "Apple, Inc.",
  "local": false,
  "multicast": false,
  "prefix": "0023DF"
}

Full API reference

Normalization

Different formats.
One address.

Bring addresses from different tools into the same inventory. Colons, dashes, dotted groups and bare hexadecimal digits all return uppercase colon notation.

Four supported inputs
  • 00:23:df:84:45:e6
  • 00-23-df-84-45-e6
  • 0023.df84.45e6
  • 0023df8445e6

00:23:DF:84:45:E6

A complete 48-bit address in each format.

Vendor coverage

Know what
the name means.

The vendor is the registered holder of an address assignment. Use it to label an inventory record alongside the normalized address and its flags.

Read the response fields
Registered global unicast addresses
Known 24-, 28- and 36-bit assignments are matched from a full address. The most specific assignment supplies the name. prefix identifies that matched block.
Missing names stay null
Local, multicast, private, unknown and all-zero addresses return a null vendor. A valid address can still have no registered name.
An assignment, not a device identity
A name does not establish the device model, current owner or hardware manufacturer. The local flag alone does not prove randomization.

From the lookup to your app

One key.
Your next integration.

Add vendor labels to a network inventory or normalize an address before saving it. Call the same API from your service, app or agent.

HTTP, SDKs and MCP

Copy a request above, use the MAC method in your SDK, or call the mac tool through MCP. The reference covers authentication, fields and errors.

Before you build.

Which MAC address formats work?

Pass a complete 48-bit address as six two-digit octets with colons or dashes, three dotted groups of four hexadecimal digits, or twelve bare hexadecimal digits. Mixed case is accepted. Prefix-only lookups and 64-bit addresses are not supported.

Does valid mean the device exists?

valid checks the address format. It does not confirm that a device exists, is connected or belongs to a particular person.

What if there is no vendor match?

A valid address with an unknown or private assignment returns vendor as null. Local, multicast and all-zero addresses also have a null vendor. Invalid input returns HTTP 200 with valid as false and vendor, local and multicast as null.

How current is the vendor name?

The name comes from the assignment directory held by the service when you look up the address. The response does not include a per-assignment update date. A registered assignment does not establish the current device owner or hardware manufacturer.

Can I detect randomized addresses?

local tells you whether the locally administered bit is set. It does not prove randomization. multicast identifies the group address bit, including broadcast addresses.

What does a lookup cost?

One API request on every plan, including vendor lookup. There is no separate vendor charge. Your request allowance is shared across ParseAPI products.

MAC API pricing

Start with one address.

Each MAC lookup uses one API request, including the vendor lookup. Your monthly allowance is shared across ParseAPI products.

Free

Start free

Try MAC with a free API key.

Room to grow

See plans

Choose the volume your app needs.