validate uuid online
A well-formed UUID has 36 characters, 32 hexadecimal digits and 4 hyphens at the fixed 8-4-4-4-12 positions. But "well-formed" and "valid" are not the same thing: a string can have exactly that shape and still use a version no real generator produces. This page separates what format validation confirms from what it leaves open.
Passes the shape check because it has 32 hex digits and 4 hyphens, but version 0 does not exist in RFC 9562: it is the reserved value for "no UUID", not a generated one.
Same reasoning as the Nil UUID, from the opposite side: version f and the "Future" variant match no real generator, only the top sentinel value RFC 9562 reserved in 2024.
Here the version nibble is 4 and the variant nibble starts with "10" in binary (hex a), so beyond well-formed the UUID is also semantically consistent with a real generator.
A UUID v4 is a 128-bit unique identifier generated with random bits, except for the 4 version bits and 2 variant bits, which leaves 122 truly random bits. The format is xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx, where the version digit is always 4 and y is 8, 9, a or b.
Not necessarily, and that is the core limitation of any format validator. It confirms the string has 32 hex digits and 4 hyphens in the right positions, at most that the version and variant make sense. It never confirms that specific value was ever generated, exists in a table or matches a real record: that requires a lookup, not a format check.
It depends on the context. RFC 9562 reserves the value 00000000-0000-0000-0000-000000000000 precisely to represent "no UUID" explicitly, so finding it in an optional field can be intentional. It is suspicious when it shows up where a real unique identifier was expected, because real generators (random v4, timestamp-based v7) have negligible odds of producing all zero by chance.
Because RFC 9562 fixed that position from the first specification (RFC 4122): counting the 32 hexadecimal digits without the hyphens, the 13th is always the first character of the third group of 4. Fixing the position, instead of leaving it variable, is what lets any parser read the version without having to decode the whole UUID first.