Interpret a UUID
Back
Your input: dd11bb2e-c704-8e0d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:dd11bb2e-c704-8e0d-87ea-5ce32bd83b97
URI: uuid:dd11bb2e-c704-8e0d-87ea-5ce32bd83b97
Microsoft GUID syntax: {DD11BB2E-C704-8E0D-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdd11bb2e, 0xc704, 0x8e0d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.293851452631745881983323296309773351831
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56593.47918.50948.36365.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15929719166568009229.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3708926766.3338964493.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56593.47918.50948.36365.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdd11bb2ec704e0d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdd11bb2e]
Custom data block2 (16 bit): [0xc704]
Custom data block3 (12 bit): [0xe0d]
Custom data block4 (14 bit): [0x07ea]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0xdd11] 0b1101110100010001
Milliseconds: [0xbb] 733 (deviation -2ms..2ms)
Seconds: [0x2e] 46
Minute of day: [0x04c7] 1223 (20:22)
Day of year: [0x0de] 222 (Day=10, Month=8)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-08-10 20:22:46'733 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing