Forensics Utilities: Free, fast, zero-storage forensic analysis tools for cybersecurity and digital investigation
Home / Tools / UUID / GUID Forensic Decoder
RFC 4122 // Windows Little-Endian GUID Forensics

UUID / GUID Forensic Decoder & v1 MAC Analyzer

Deconstruct 128-bit UUIDs and Microsoft GUIDs into their atomic components. Recover exact sub-microsecond creation timestamps from UUID v1, extract physical hardware IEEE 802 MAC addresses, query vendor OUIs, and transpose Little-Endian binary registry values.

UUID v1 Timestamp & Epoch Math
Hardware MAC & Vendor OUI Resolution
Windows Registry Little-Endian Transposition
> FORENSIC DECONSTRUCT UUID VERSION 1
Origin Time: 2001-09-11 12:46:40 UTC
Hardware NIC: 00:02:B3:3B:A8:8B
• OUI: Intel Corporation (Unicast)

Enter UUID / GUID or Raw Binary Registry Bytes

Supports standard hyphenated strings, curly-braced registry GUIDs, URNs, or raw 16-byte hex sequences. 0 characters
CANONICAL RFC 4122 STRING
--
VERSION 1 RFC 4122
UUID Version v1
Time-based (v1)
Generates unique IDs using Gregorian time & host MAC.
Specification Variant Layout
Leach-Salz (RFC 4122)
High bits: 10x (Standard network format)
Clock Sequence 14-bit state
--
Prevents collision if system clock rolls backwards
Windows Registry LE Hex Byte Dump
--
Data1/Data2/Data3 byte-swapped for Registry/MFT
UUID v1 Temporal Forensics (Creation Timestamp)
60-BIT GREGORIAN TICKS
UTC Time (Precise)
--
--
Local Browser Time
--
--
Unix Epoch Seconds
--
-- ms
Gregorian 100ns Ticks
--
Since 1582-10-15 00:00:00 UTC
Origin Hardware / IEEE 802 Node Forensics
PHYSICAL HARDWARE NIC
Extracted MAC Address
--
Unicast / Physical Hardware
Hardware Manufacturer (OUI)
--
Prefix: --
Forensic Notice: This is a Version 4 UUID. Version 4 UUIDs are pseudo-randomly generated and do not contain hardware MAC addresses or Gregorian timestamps. Version 3 and 5 are MD5/SHA1 namespace hashes.
BATCH TIMELINE ENGINE

Batch UUID Forensic Timeline Generator

Paste multiple UUIDs (from Registry dumps, LNK logs, NTFS $OBJECT_ID, or CSV reports) to generate an instant timeline.

# UUID / GUID Version UTC Creation Timestamp Hardware MAC Address OUI Vendor Type
No batch data processed yet. Paste GUIDs above and click "Generate Forensic Timeline".

Forensic Significance of UUID / GUID Analysis

In computer incident response, digital forensics, and criminal investigations, Universally Unique Identifiers (UUIDs) and Globally Unique Identifiers (GUIDs) serve as foundational pieces of forensic evidence. While modern specifications (such as UUID Version 4) rely on pseudo-random numbers, legacy specifications—especially UUID Version 1—were engineered using physical hardware identifiers and precise high-resolution timestamps.

How Investigators Leverage UUID Version 1 (Temporal & Hardware Forensics)

Unlike random tokens, a UUID v1 provides two forensic anchor points that can prove user intent, link disparately seized storage drives, and confirm machine attribution:

1. Windows LNK & Distributed Link Tracking

When shortcut files (.lnk) or NTFS files with $OBJECT_ID attributes are created, Microsoft's Distributed Link Tracking Service assigns a Version 1 UUID containing the host computer's physical MAC address and creation second.

2. Machine Attribution & Hardware OUI

The 48-bit Node ID corresponds to the physical network card (NIC). The first 3 bytes form the Organizationally Unique Identifier (OUI), identifying the hardware manufacturer (such as Intel, Apple, Dell, or VMware).

3. Windows Registry Little-Endian Transposition

Windows stores binary GUIDs in the Registry (Shellbags, UserAssist, CLSIDs) using mixed Little-Endian format (Data1, Data2, Data3 inverted). Converting raw bytes without byte-swapping causes invalid dates and phantom versions.

4. Historical Case Precedent: Melissa Virus

In 1999, the author of the Melissa virus was traced and arrested because Microsoft Word 97 documents generated internal GUIDs containing the author's physical network adapter MAC address.

UUID Version Comparison Reference

Version Generation Method Forensic Artifacts Recoverable Investigative Value
UUID v1 60-bit Gregorian Time + 48-bit MAC Sub-microsecond UTC creation time, physical MAC, vendor OUI Extremely High
UUID v2 DCE Security (POSIX UID/GID) Local POSIX user/group ID and domain timestamp High
UUID v3 MD5 Hash over Namespace Namespace correlation (deterministic hash) Moderate
UUID v4 Cryptographic PRNG (122 random bits) Collision resistance only; zero timestamp or hardware data Low
UUID v5 SHA-1 Hash over Namespace Namespace correlation (deterministic hash) Moderate

Frequently Asked Questions (FAQ)

October 15, 1582 is the date the Gregorian calendar was officially introduced by Pope Gregory XIII. RFC 4122 adopted this zero-point because it standardizes international calendrical arithmetic and prevents negative timestamps for historical document indexing.

RFC 4122 specifies that if a host machine has no physical network card or is configured for user privacy, bit 0 of the first octet of the node ID is set to 1 (making it a multicast address) and the remaining bits are randomized. If bit 0 is 0, it is guaranteed to be a genuine physical network adapter.

No. ForensicsInsider tools operate 100% in local browser memory. All BigInt bitwise arithmetic, endianness transpositions, timestamp computations, and MAC OUI vendor lookups execute client-side. Zero bytes leave your machine.