Definition

The node ID is a 48-bit field occupying bits 80–127 (the last 12 hex characters) of a UUID v1. It was designed to be a hardware identifier for the machine that generated the UUID — ensuring uniqueness across different hosts even when timestamps are identical.

In the original RFC 4122 specification, the node ID was the MAC (Media Access Control) address of one of the host’s network interfaces.

Position in the UUID v1 layout

UUID v1 layout (hex):
xxxxxxxx-xxxx-1xxx-yxxx-xxxxxxxxxxxx
         ←timestamp→      ←node ID→
                          ↑ 12 hex chars = 48 bits

Example UUID v1: 550e8400-e29b-11d4-a716-446655440000

The last segment 446655440000 is the node ID — in this case, 44:66:55:44:00:00 as a MAC address.

Privacy problem with MAC-based node IDs

When a real MAC address is used as the node ID:

  1. Hardware fingerprinting: Any UUID v1 generated by that machine reveals its network hardware identifier.
  2. Cross-context linkage: UUIDs from different applications on the same machine share the same node ID — enabling correlation even across different services.
  3. Network topology disclosure: MAC addresses encode the NIC manufacturer (first 3 bytes = OUI), revealing hardware vendor information.

RFC 9562 addresses this by deprecating UUID v1 in favour of UUID v6 (reordered timestamp) and UUID v7 (Unix timestamp + random bits), neither of which has a node ID field. See UUID Security.

RFC 9562 recommendation

RFC 9562 §5.1 explicitly deprecates MAC address-based node IDs:

“The node field SHOULD be generated using a pseudo-random or random value […] using a randomly generated value is preferred.”

When UUID v1 implementations cannot avoid the node ID (legacy compatibility), RFC 9562 recommends setting the multicast bit (bit 40 of the node ID) to 1, signalling that the node ID is not a real MAC address:

Randomly generated node ID with multicast bit set:
a4:b3:c2:d1:e0:ff → a5:b3:c2:d1:e0:ff (multicast bit = 1)

UUID v7: no node ID

UUID v7 eliminates the node ID entirely:

UUID v7 layout (hex):
xxxxxxxx-xxxx-7xxx-yxxx-xxxxxxxxxxxx
←ms ts→       ↑v7   ↑var ← rand_b →
                         ← 62 bits random →

The 74 bits of randomness (rand_a + rand_b) in UUID v7 provide stronger uniqueness guarantees than a MAC address while leaking no hardware information. See Random Bits — UUID entropy.

UUID v6: same node ID problem

UUID v6 reorders the timestamp for better database sort performance but retains the node ID field from UUID v1. It is a transitional format — new systems should prefer UUID v7. See Time-Based UUID.

Frequently asked questions

What is the node ID in a UUID?

The node ID is bits 80–127 of a UUID v1 — the last 12 hex characters (6 bytes). In the original RFC 4122 specification, this was the MAC address of the network interface on the host that generated the UUID. RFC 9562 deprecated this field and recommends using random bytes instead to avoid leaking network hardware information.

Does UUID v7 have a node ID?

No. UUID v7 has no node ID field. The 128-bit layout is: 48 bits timestamp, 4 bits version (0111), 12 bits rand_a, 2 bits variant, 62 bits rand_b. All non-timestamp, non-version bits are random — there is no host identifier. This is one of the privacy advantages of UUID v7 over UUID v1. See UUID v4 vs v7.

Is the node ID a privacy risk in UUID v1?

Yes, when the node ID is a real MAC address. MAC addresses are hardware identifiers that can be used to fingerprint the generating machine across different UUID values. This is why RFC 9562 deprecates UUID v1 and recommends UUID v7, which uses random bits in the equivalent field. See UUID Security.