Interpret a UUID
Back
Your input: 01a0af32-0bb1-784e-a1ec-f5895cae16ff
Various notations:
URN: urn:uuid:01a0af32-0bb1-784e-a1ec-f5895cae16ff
URI: uuid:01a0af32-0bb1-784e-a1ec-f5895cae16ff
Microsoft GUID syntax: {01A0AF32-0BB1-784E-A1EC-F5895CAE16FF}
C++ struct syntax: { 0x01a0af32, 0x0bb1, 0x784e, { 0xa1, 0xec, 0xf5, 0x89, 0x5c, 0xae, 0x16, 0xff } }
As OID (ISO/ITU-T 128 bits): 2.25.2163548879858136161608294850718734079
As OID (Microsoft): 1.2.840.113556.1.8000.2554.416.44850.2993.30798.41452.16091484.11409151
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.117286219791038542.11667970704924350207
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.27307826.196180046.2716661129.1554913023
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.416.44850.2993.30798.41452.62857.23726.5887
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x7] Unix Epoch Time
Timestamp: [0x01a0af320bb1] 2026-09-17 11:48:07'729 GMT
Random bits: ????1000 01001110 ??100001 11101100 11110101 10001001 01011100 10101110 00010110 11111111
Random bytes: [0x84e?1ecf5895cae16ff]
Lookup this UUID at MagnumDB, Google, Bing