UUID Variant 8 – Validate RFC-Compatible Variant Nibble

Local only

Demonstrate the lower accepted boundary of the UUID validator's RFC-compatible variant nibble range.

36 chars · 1 line

Waiting for input

Valid UUID v4

UUID variant inspection

Is a UUID with variant nibble 8 valid?

The first hexadecimal digit of a UUID's fourth group participates in variant encoding. VetaTool's current inspector accepts hexadecimal 8 through B as its RFC-compatible range, so a canonical UUID v4 with a fourth group beginning in 8 passes. 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. Confirm the UUID uses canonical text and a supported version nibble.
  2. Inspect the first hexadecimal digit in the fourth UUID group.
  3. Compare the resulting validation label with variant values 9, A, and B.

Variant and version are separate checks

The version nibble is read from the third group while the validator reads the variant nibble from the fourth group.

Passing both checks yields the version label. This does not prove every version-specific field was generated according to a particular algorithm.

Variant nibble 8 example

The fourth group begins with 8 and the version nibble is 4.

UUID input

550e8400-e29b-41d4-8716-446655440000

Validation result

Valid UUID v4

Common questions

Frequently asked questions

Does the label show the UUID variant?

The current UI label reports validity and UUID version. Variant acceptance is part of the validation decision rather than a separate output label.

What happens below hexadecimal 8?

The current inspector rejects variant nibble values below 8 as Invalid RFC 4122 UUID.

Debugging a specific UUID issue? Browse UUID troubleshooting.