GLOBAL UUID DATABASE - 58564 UUIDs, 130484 comments.

Last UUIDs added:

A selection of UUIDs :

10 random UUIDs from the database :

What it this website ?

There was a need for a global UUID database, indexing all the known UUIDs in the world, because randomly copypasting things on search engines isn't something anyone should do. This website is an answer for the UUID indexing need, made with love and dedication by your neighbourly django adept.
Anyone can contribute to the database by accessing an UUID URL in the form shown above, and leaving a comment. Leaving a comment registers the UUID in the database, and the next folk on the Internet will thank you for this.
I also made a script to automatically push some Microsoft-related UUIDs from a Microsoft Windows operating system equipped with Microsoft PowerShell. Feel free to run the following command line in an elevated powershell instance : iex (iwr The code is made to be editable, and should allow one to gather more UUIDs from his own Microsoft Windows equipped detonation VM, piping the results into the function 'Out-GridView' instead of 'push'.
  iex (New-Object System.Net.WebClient).DownloadString('')
Another thing to know while contributing, is that the best-ranked comment gets elected as UUID name, so if you find the authoritative name for some UUID, feel free to upvote yours.

What is an UUID ?

There are a lot of links below, but if you're reading this you might want the definitino right now. UUID are 128 bits identifiers, concieved to be globally unique (hence the other name for those identifiers, Globally Unique IDentifier, GUID). Their generation does not require any form of central registration authority.
Their uniqueness is mostly based on the entropy embedded in the 128 bits, slightly lower than 128 bits for UUID respecting the specification, which have some bits reserved for the version.
Possible UUID versions : The UUID specification defines several parts for the hexadecimal representation of the 128 bits : Each of those fields can have its own section, let's begin with the most important one, trivially visible, the time-high-and-version field, which is visible in the middle of an UUID.

Version and Variant

The Variant of an UUID is the number of non-zero bits in the second half of the UUID, which is after the bit 64, or starting at the first MSB of the 9th byte. (I need to check those offsets with the endianness issues). Possible values are : The Version of an UUID is stored as an uint4 in the first nibble of the 7th byte, which is the first character of the middle field in the hexadecimal representation of an UUID. The allowed versions have been listed above, and nothing above 5 should be seen. It's worth mentioning that most of the valid UUID I collected in the database were UUIDv1 (based on time and MAC) and UUIDv4 (random).
Excellent snippets from the cryptanalysis linked below
The UUID version is defined     : Ui [7] = ( Ci [7] & 0x0F ) | 0x40.    
Identifies belonging to RFC 4122: Ui [9] = ( Ci [9] & 0x3F ) | 0x80.  
The Java documentation claims that "Variant 2" UUID are "Leach-Salz", but have the good property of listing the bitmasks :
The layout of a variant 2 (Leach-Salz) UUID is as follows: The most significant long consists of the following unsigned fields:

  0xFFFFFFFF00000000 time_low
  0x00000000FFFF0000 time_mid
  0x000000000000F000 version
  0x0000000000000FFF time_hi

  The least significant long consists of the following unsigned fields:
  0xC000000000000000 variant
  0x3FFF000000000000 clock_seq
  0x0000FFFFFFFFFFFF node


The timestamps embedded in the UUIDv1 and UUIDv2 are 60bit timestamps, they should be the number of 100-nanosecond intervals between the generation time and 1582-10-15 00:00:00, date of the Gregorian reform of the Christian calendar.
Because Microsoft chose the 1601-01-01 00:00:00, date of the first 400-year cycle reset of the newly-applied Gregorian calendar, some UUID have been shifted by 17 years, 1 month and 15 days.
Finally, because the UNIX epoch started on 1970-01-01 00:00:00, some UUID have been miscalculated using the latter timestamp as starting point, hence having an offset of 470 years.
Those three timestamps are shown on the UUID detailed pages, as there is no canonical way to determine which timestamp starting point was used.

Clock sequence

This field is the third source of entropy for the UUIDv1, defined in the RFC 4122. The RFC did some attempts at defining methods to add entropy in this field, it should be considered random, and might be shared by UUID generated during the same boot of a specific operating system.

UNIX ids

Defined for UUIDv2, I still need to read the spec, lol :D

Should I add all the UUIDs in the world ?

Yes, as long as they are global. Don't add disk partitions uuids specific to your hardware, but add anything that anyone might want to look up online. Ideally, I would like to collect all the strange Microsoft Windows UUIDs, and all the strange UUIDs from all the strange places that might exist.
I already made some scripts to push new UUIDs to the database, collected from various sources such as websites, source code listings, and workstations. Those scripts are listed below :
Automation script to push long lists : github gist
Automation script to push MSDN copypasted CSIDL : github gist
Automation script that contains several sources : :

What about publishing data and collecting IPs ?

I don't store IP addresses except in HTTP logs, and all the data is CC-BY-NC-SA.
Complete UUID list (text/plain streamed data) : full

What's next ?

I definitely need to implement the following features : I should also document my operations in some sort of technical blog maybe, it's fun and I'm learning a lot of things. All the static UUID sources from a single Windows workstation will be embedded and documented in the /c collection script anyways. (For now, I track my discoveries in a twitter thread.)

Some links about UUIDs are presented below. I would like to express my sympathy to other archivists ( Harald Tveit Alvestrand, Simon Mourier, the lad at , Jason Scott from, as well as all the volunteers. )


Sources that have been or will be integrated (most can't be complete and must be maintained):