UUID v3 Validation – Check Version 3 UUID Online

Local only

Validate the encoded UUID version using the same canonical UUID inspector as the main UUID tool.

36 chars · 1 line

Waiting for input

Valid UUID v3

UUID version validation

UUID v3 Validation: what does the validator actually check?

UUID v3 is a name-based UUID version. VetaTool can identify version 3 from canonical UUID text, but structural inspection alone cannot prove which namespace, name, or MD5 input produced the identifier. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Canonical 8-4-4-4-12 UUID validation
  • UUID version inspection
  • RFC 4122 variant checking
  • Nil UUID recognition
  • Uppercase hexadecimal support
  • Browser-local validation

Steps

  1. Paste the UUID and confirm the first hexadecimal digit of the third group is 3.
  2. For a provenance check, convert the expected namespace ID and name to their canonical octet sequences, concatenate them in network byte order, and compute MD5.
  3. Use all 128 MD5 bits as the UUID layout, then replace the version field with 3 and the RFC variant bits with 10 before formatting the canonical UUID text.
  4. Compare that recomputed UUIDv3 with the value you received; VetaTool's inspector only confirms the encoded structure and does not perform this derivation.

UUID v3 uses version nibble 3

When the first hexadecimal digit of the third group is 3 and the variant bits are RFC-compatible, the inspector labels the value UUID v3.

A provenance check requires the original namespace ID and name because UUIDv3 hashes their canonical octets with MD5 before the version and variant bits replace hash bits.

Version detection is not full semantic validation

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.

UUID v3 Validation example

RFC 9562 UUIDv3 test vector for the DNS namespace and www.example.com. UUIDv3 consumes the full 128-bit MD5 result before setting the version 3 and RFC variant bits.

UUID input

5df41881-3aed-3515-88a7-2f4a814cf09e

Validation result

Valid UUID v3

Common questions

Frequently asked questions

Does UUID v3 validation recompute the MD5 namespace/name hash?

No. The inspector does not have the original namespace and name octets, so it cannot reproduce the MD5 derivation; recompute UUIDv3 separately when provenance matters.

Does this prove the UUID was generated by a version 3 algorithm?

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.

Recommended next steps

UUID v5 ValidationInspect canonical UUID text whose version nibble identifies name-based UUID v5.MD5 vs SHA-1 HashCompare plain MD5 and SHA-1 digests when reviewing why name-based UUID v3 uses MD5 while UUID v5 uses SHA-1.UUID Version DetectionRead the version nibble from a canonical UUID and identify values such as UUID v1.

Debugging a specific UUID issue? Browse UUID troubleshooting.