Namespace fossils
The DNS/URL/OID/X.500 namespaces all share the 6ba7b8 prefix because they were minted once in 1997 and frozen forever—v5 lets you build atop those “root UUIDs.”
Tip: Press Ctrl/Cmd + Enter to regenerate with the same settings.
XXXXXXXX = time_low XXXX = time_mid 5XXX = time_hi_and_version (version = 5)XX XX = clock_seq (variant in high bits) XXXXXXXXXXXX = node
A UUID v5 generator creates stable, repeatable identifiers from names. If you want the same input to always map to the same ID, UUID v5 is a great fit. It is commonly used for IDs derived from URLs, domain names, user names, or other strings where you want consistency across systems. Unlike random UUIDs, the output is deterministic, so you can regenerate the same ID whenever you need it.
UUIDs are 128‑bit values written as 36‑character strings with hyphens. Version 5 is name‑based, meaning it combines a namespace (a category) with a name (the specific value). That pairing ensures you can reuse the same name in different namespaces without collisions. For example, “example.com” in the DNS namespace is different from “example.com” in a custom namespace you define for internal projects.
The generator takes the namespace UUID and the name, encodes the name in UTF‑8, and hashes the combined bytes with SHA‑1. It then uses the first 16 bytes of that hash to form the UUID, setting the version and variant bits required by RFC 4122. The resulting pattern looks like xxxxxxxx-xxxx-5xxx-yxxx-xxxxxxxxxxxx. The “5” indicates version 5, while the rest of the digits come from the hash.
UUID v5 is useful for data migrations, syncing records between databases, and generating consistent IDs for APIs without storing a lookup table. It is also handy for software projects where you want predictable identifiers for configuration keys, feature flags, or resource names.
Built‑ins include DNS (6ba7b810-9dad-11d1-80b4-00c04fd430c8), URL (6ba7b811-9dad-11d1-80b4-00c04fd430c8), OID (6ba7b812-9dad-11d1-80b4-00c04fd430c8), and X.500 DN (6ba7b814-9dad-11d1-80b4-00c04fd430c8). You can also supply a custom namespace UUID to define your own identifier space.
Note: SHA‑1 here is used for identifiers, not cryptographic signatures.
Everything runs locally in your browser, so your input values remain private. Use this tool whenever you need consistent, human‑derived identifiers that work across applications and databases.
The DNS/URL/OID/X.500 namespaces all share the 6ba7b8 prefix because they were minted once in 1997 and frozen forever—v5 lets you build atop those “root UUIDs.”
v5 takes the first 16 bytes of SHA-1 (normally 20), then overwrites a nibble to force version 5. So even though SHA-1 outputs 160 bits, only 128 survive.
Because input is UTF-8, https://example.com/a and https://example.com/A are distinct. You can fingerprint REST endpoints, blog slugs, even emoji paths.
Teams use v5 to mint stable IDs for assets (fonts, sprites, docs) so CDN caches and databases stay consistent across rebuilds without storing the raw paths.
If two lines in batch mode hash to the same UUID, it means they were literally the same bytes—v5 gives you a built-in duplicate detector while you generate.