UUID Verifier

Validate UUIDs instantly. Check format, version, variant and get detailed information.

UUID Verifier

Validate UUIDs instantly. Check format, version, variant and get detailed information.

Paste one or more UUIDs to begin validation.

1

Enter UUID to Verify

Separate multiple UUIDs with spaces, commas, or new lines.

Canonical, compact, braced, and URN formats are accepted.0 UUIDs found
2

Verification Results

No UUIDs verified.

#UUIDStatusVersionVariant
Results will appear here.
Waiting for UUID input.
3

UUID Details

Select a verified UUID.

Waiting
UUID
Format
Version
Variant
Status
Length
Randomness
Timestamp

Format Breakdown

xxxxxxxxtime_low
(8 hex)
xxxxtime_mid
(4 hex)
xxxxtime_hi_and_version
(4 hex)
xxxxclock_seq
(4 hex)
xxxxxxxxxxxxnode
(12 hex)
8

UUID Information

A valid UUID must:

  • Be 128 bits long (32 hexadecimal digits)
  • Have canonical groups in 8–4–4–4–12 positions
  • Have a valid version (1, 2, 3, 4, 5, 6, 7, or 8)
  • Have a recognized UUID variant

UUID Versions Quick Guide

v1Time-basedv2DCEv3Name MD5v4Randomv5Name SHA-1v6Reordered timev7Unix timev8Custom

Common UUID Examples

Version 1 — Time-based6ba7b810-9dad-11d1-80b4-00c04fd430c8
Version 3 — Name MD56fa459ea-ee8a-3ca4-894e-db77e160355e
Version 4 — Random550e8400-e29b-41d4-a716-446655440000
Version 5 — Name SHA-13fa85f64-5717-5562-b3fc-2c963f66afa6
Version 7 — Unix time01890f2e-3c7b-7f89-9b1e-1e8c8f901a2b

All validation is performed locally. UUID data never leaves your browser.

Practical guide

Using UUID Verifier with confidence

Reviewed by LipiCode Editorial Team

What this tool helps you do

UUID verification checks textual structure and can identify version and variant bits. It can show that a value is well formed, but it cannot prove the identifier exists, belongs to a particular record, or was generated securely.

When it is useful

  • Validating imported identifiers
  • Checking an API parameter
  • Inspecting UUID version metadata
  • Normalizing identifiers before storage

A practical example

Validate an incoming value before converting it to a database UUID type. Then perform authorization and existence checks independently against application data.

Limitations and common mistakes

Accepting a syntactically valid UUID must not bypass access control. Braces, URN prefixes, whitespace, and noncanonical forms may require an explicit normalization policy.

Frequently asked questions

Can a valid UUID still be wrong?

Yes. Syntax validation says nothing about whether it identifies the intended object.

Does uppercase change a UUID?

No. Hexadecimal case does not change the underlying 128-bit value.

Read the related in-depth guide