UUID v4 Format Validator

CanonicalhexUUIDversion4ANDRFCvariantbits10,notgenericUUIDlayout/version-onlyparser or randomness/provenancecertificate. Explicitboundedofflineconvention,not authoritative external identity,eligibility,clinical or safe-use determination.

Description

A UUID v4 has a canonical hexadecimal layout plus version and variant bits.

A UUID v4 has a canonical hexadecimal layout plus version and variant bits.^{[1, 2]}

This validator checks those text features; successful formatting cannot establish how the identifier was generated.

When to use UUID v4 Format Validator

Use this tool to apply the stated uuid v4 format validator operation with an explicit input and unit basis.

How to use UUID v4 Format Validator and how it works

Establish the text or game convention described above.
Enter actualUuid and run the tool.
Read result.validRfcVariantUuidV4 using the output meanings below.
If input is rejected, correct the stated type, range, ordering or alignment issue and rerun; review successful results under the declared convention.

Input field	Meaning	Value type	Requirement
actualUuid	Uuid, on the basis specified in the algorithm.	string	required; further conditions in the algorithm

Match the entire untrimmed string against 8-4-4-4-12 hexadecimal groups, version digit 4 and variant digit 8,9,a or b. Case is ignored; a nonmatching string returns false.

valid = canonical hex layout AND version 4 AND RFC variant 10

Apply the declared units, ordering and branch conditions.

Output field	Meaning	Value type
result	Object containing the declared output fields.	object
result.validRfcVariantUuidV4	Format, version and variant check boolean; false is a successful check result.	boolean

json

{
  "input": {
    "actualUuid": "550e8400-e29b-41d4-a716-446655440000"
  },
  "output": {
    "result": {
      "validRfcVariantUuidV4": true
    }
  }
}

Limitations and assumptions

The output applies the declared operation to the values you supply. Establish the measurement basis, units, coefficients and any caller-selected rules before interpreting it. The tool does not independently collect or verify observations or decide whether a model or reference applies.

Supply explicit required fields with the documented types and dense aligned arrays. Unknown fields, wrong types and nonfinite numbers are rejected. Branch-specific constraints are explained above. A successful false boolean, negative signed difference, empty slice or unresolved tie is distinct from an input error. Very large inputs or outputs may be rejected by shared resource limits.

RFC 9562 defines UUID version and variant structure. This tool checks the canonical v4 textual layout and variant bits; it does not validate random generation, uniqueness or provenance.

Alternative or Complementary methods

Use UUID Parser to complement this result. Inspect normalized UUID text, byte values, version and variant to diagnose format differences.

Use UUID Format Validator to complement this result. Check the general canonical UUID layout and report the version nibble.

References

UUID v4 Format Validator — tool.io
RFC 9562: Universally Unique IDentifiers — IETF

Similar or alternative tools

UUID Parser
Inspect normalized UUID text, byte values, version and variant to diagnose format differences.
UUID Format Validator
Check the general canonical UUID layout and report the version nibble.