UUID v3 generator

The Randogram UUID generator produces a universally unique identifier of version 3.
A version 3 UUID is the MD5 hash of a namespace and a name: the same name always yields the same identifier. Here the name is random, so every run returns a new value; if you need a reproducible identifier, compute it from your own namespace. For new work the standard suggests version 5 — it uses SHA-1 instead of the outdated MD5.
You can also use the public UUID generator API

Questions and answers

Why does version 3 return a new value every time?
Because the name the hash is computed from is random — the form asks for neither a namespace nor a name. Version 3 itself is deterministic: the same name in the same namespace always gives the same identifier. To get that behaviour, compute the hash yourself from your own values.
Is it a problem that version 3 is built on MD5?
Not for identifiers: the hash is there to spread names evenly across the value space, not to vouch for anything. The weaknesses of MD5 matter where a hash certifies data. For new work the standard still suggests version 5 with SHA-1.
How does version 3 differ from version 5?
Only in the algorithm: version 3 computes MD5, version 5 computes SHA-1 and keeps its first 128 bits. The rules for placing the version number and the variant are the same. The same input produces different identifiers in the two versions, so they must not be mixed within one system.