Interpret a UUID
Back
Your input: 01a05a17-afdd-7127-8d3d-e0b50c35614c
Various notations:
URN: urn:uuid:01a05a17-afdd-7127-8d3d-e0b50c35614c
URI: uuid:01a05a17-afdd-7127-8d3d-e0b50c35614c
Microsoft GUID syntax: {01A05A17-AFDD-7127-8D3D-E0B50C35614C}
C++ struct syntax: { 0x01a05a17, 0xafdd, 0x7127, { 0x8d, 0x3d, 0xe0, 0xb5, 0x0c, 0x35, 0x61, 0x4c } }
As OID (ISO/ITU-T 128 bits): 2.25.2161822786690138453769947397236285772
As OID (Microsoft): 1.2.840.113556.1.8000.2554.416.23063.45021.28967.36157.14726412.3498316
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.117192648092905767.10177537801125716300
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.27286039.2950525223.2369642677.204824908
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.416.23063.45021.28967.36157.57525.3125.24908
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x7] Unix Epoch Time
Timestamp: [0x01a05a17afdd] 2026-08-31 23:11:36'925 GMT
Random bits: ????0001 00100111 ??001101 00111101 11100000 10110101 00001100 00110101 01100001 01001100
Random bytes: [0x127?d3de0b50c35614c]
Lookup this UUID at MagnumDB, Google, Bing