Validate GUID

Paste any GUID to validate, detect, decode and decompile its version, variant, timestamp (Unix milliseconds / ISO time), RFC variants, Node Identifier (Possibly MAC-address derived) if relevant, embedded fields (time_low, time_mid, time_hi_and_version, clock_seq_hi_and_reserved, clock_seq_low, node), Security warnings and helpful notes.
This validator supports all GUID (also known as a UUID) versions: v1, v2, v3, v4, v5, v6, v7 and v8.
Do it all locally inside your browser for free. No API calls needed. No data sent anywhere.

Input

Supports braces, hyphens, and urn:uuid:

Result

Paste a GUID to see analysis.

Comparison of GUID Versions

Versions	v1	v2	v3	v4	v5	v6	v7	v8	empty-nil
Type	Time + Node (historically MAC)	DCE Security (UID/GID)	Name (MD5)	Random	Name (SHA-1)	Ordered time v1	Time ordered + random	Custom / User-defined	Empty / Nil (all zeros)
Deterministic?	No	No	Yes	No	Yes	No	No	Depends	Yes
Sortable?	Yes ~100 nanoseconds	Partial ~100 nanoseconds	No	No	No	Yes ~100 nanoseconds	Yes Millisecond	Depends	N/A
Secure?	MAC leak (historically)	Leaks IDs	MD5	Yes	SHA-1	Yes	Yes	Custom	No (not unique)
Typical Use	Distributed systems	Legacy DCE systems	Namespace-based IDs	General purpose (Recommended)	Stable API IDs	Database indexing	Latest most modern	Experimental, app-specific	Sentinel / “no value” / placeholder
Standardized	RFC 4122 -> RFC 9562 (July 2005 -> May 2024)	RFC 4122 -> RFC 9562 (July 2005 -> May 2024)	RFC 4122 -> RFC 9562 (July 2005 -> May 2024)	RFC 4122 -> RFC 9562 (July 2005 -> May 2024)	RFC 4122 -> RFC 9562 (July 2005 -> May 2024)	RFC 9562 (May 2024)	RFC 9562 (May 2024)	RFC 9562 (May 2024)	RFC 4122 -> RFC 9562 (July 2005 -> May 2024)
Notes	Includes timestamp + Node (historically the MAC address). Ordered but exposes hardware info.	Embeds POSIX UID/GID + MAC address. Rarely supported and considered obsolete.	Deterministic, but MD5 is cryptographically broken.	Pure randomness (122 random bits). Extremely low collision probability.	Deterministic like v3 but uses SHA-1, which is no longer fully secure.	Improved v1 format with sortable structure + privacy-safe design.	Combines millisecond timestamps with strong randomness. Ideal for distributed systems.	Flexible GUID / UUID layout reserved for application-defined use. Not recommended for generic scenarios.	Not a real identifier, used to represent “no value”. Never generate or use it for uniqueness.

By using this site, you agree to our Privacy Policy and Terms of Service. You are not permitted to use the GUIDs (also known as UUIDs) generated by this site or use any other content, services and information available if you do not agree to these terms.
Disclaimer: All information is provided for general educational and technical reference only. While we aim to keep the content accurate, current and aligned with published standards, no guarantees are made regarding completeness, correctness or suitability for any specific use case.
GUID specifications, best practices, security guidance, database behavior and ecosystem conventions (including cloud platforms and identifier formats) may change over time or differ by implementation. Examples, recommendations and comparisons are illustrative and may not apply universally.
This content should not be considered legal, security, compliance or architectural advice. Before making critical design, security or production decisions, always consult the latest official standards and vendor-specific documentation.
Always evaluate behavior in your own environment.
Standards Compliance: The GUIDs generated by this site conform to RFC 4122 and RFC 9562 specifications whenever possible, using cryptographically secure random number generation.