36 chars · 1 line
Waiting for input
36 chars · 1 line
Waiting for input
UUID version validation
UUID v6 uses a reordered time-based layout designed for improved sort behavior compared with older time-based forms. VetaTool can identify the version 6 nibble but does not decode or validate its embedded timestamp fields. This tool is free to use. No account or payment is required.
Last updated
A version nibble of 6 produces the Valid UUID v6 label when canonical format and variant checks also pass.
The validator does not extract a v6 timestamp or compare its time fields for internal consistency.
VetaTool reads the UUID version nibble and RFC-compatible variant range. It does not reconstruct how the identifier was generated or validate every version-specific timestamp, namespace, hash, random, or custom field.
Treat the result as structural UUID inspection. Protocols and applications can impose additional requirements beyond the encoded version number.
RFC 9562 UUIDv6 test vector with the reordered Gregorian time layout; VetaTool validates the encoded version and variant but does not decode its timestamp fields.
1ec9414c-232a-6b00-b3c8-9f6bdeced846Valid UUID v6Common questions
No. For UUID v6, the inspector reports the encoded version and validates format and variant bits without decoding the reordered Gregorian timestamp fields.
No. The validator confirms canonical text, the encoded version nibble, and RFC-compatible variant bits. It does not verify generator provenance or all version-specific field semantics.
Debugging a specific UUID issue? Browse UUID troubleshooting.