UUID v2 Validation – Check Version 2 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 v2

UUID version validation

UUID v2 Validation: what does the validator actually check?

A canonical UUID whose first digit in the third group is 2 is labeled UUID v2 when its RFC variant bits are also accepted. VetaTool reports that encoded version without claiming to validate DCE Security UUID semantics. 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 2.
  2. Confirm the fourth group begins with an RFC-compatible variant nibble from 8 through B so the structural inspector can report UUID v2.
  3. If your system depends on DCE Security semantics, validate the embedded domain and local-identifier fields with a DCE-aware implementation; the version 2 nibble alone does not prove those rules.

UUID v2 is identified by the version nibble

The version number is encoded in the first hexadecimal digit of the third UUID group. In this example that digit is 2, so the inspector reports UUID v2.

UUID v2 has specialized historical semantics. The validator does not inspect domain, local identifier, or other DCE-specific meaning.

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 v2 Validation example

This structural sample carries version nibble 2 and an RFC-compatible variant. RFC 9562 reserves UUIDv2 for DCE Security while leaving its detailed field semantics to the DCE specifications.

UUID input

550e8400-e29b-21d4-a716-446655440000

Validation result

Valid UUID v2

Common questions

Frequently asked questions

Is UUID v2 accepted by this validator?

Yes. Canonical UUID text with version nibble 2 and RFC-compatible variant bits is labeled Valid UUID v2.

Does this prove the UUID was generated by a version 2 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 Version DetectionRead the version nibble from a canonical UUID and identify values such as UUID v1.UUID v4 ValidationConfirm canonical UUID text with version 4 and RFC-compatible variant bits.UUID Generator & Validator OnlineGenerate UUID v4 batches or validate canonical UUID format, version, and variant locally.

Debugging a specific UUID issue? Browse UUID troubleshooting.