Interpret a UUID
Back
Your input: 01a17ecc-6a18-7c15-a4d3-522893c9f364
Various notations:
URN: urn:uuid:01a17ecc-6a18-7c15-a4d3-522893c9f364
URI: uuid:01a17ecc-6a18-7c15-a4d3-522893c9f364
Microsoft GUID syntax: {01A17ECC-6A18-7C15-A4D3-522893C9F364}
C++ struct syntax: { 0x01a17ecc, 0x6a18, 0x7c15, { 0xa4, 0xd3, 0x52, 0x28, 0x93, 0xc9, 0xf3, 0x64 } }
As OID (ISO/ITU-T 128 bits): 2.25.2167759568999247374931260151377294180
As OID (Microsoft): 1.2.840.113556.1.8000.2554.417.32460.27160.31765.42195.5384339.13235044
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.117514481706761237.11876926976537785188
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.27360972.1779989525.2765312552.2479485796
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.417.32460.27160.31765.42195.21032.37833.62308
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x7] Unix Epoch Time
Timestamp: [0x01a17ecc6a18] 2026-10-27 19:18:08'152 GMT
Random bits: ????1100 00010101 ??100100 11010011 01010010 00101000 10010011 11001001 11110011 01100100
Random bytes: [0xc15?4d3522893c9f364]
Lookup this UUID at MagnumDB, Google, Bing