Need help securing your website or systems?
We help businesses with:
- Web Development
- Ecommerce Integrations
- Automation
- Technical SEO
Two unrelated but frequently-needed things live here: strong passwords, and RFC 4122 v4 UUIDs - both generated using the browser's Web Crypto API (`crypto.getRandomValues`), not `Math.random()`, which is not a cryptographically secure source and shouldn't be used for either.
When you'd use this
Generating a strong password for a new account, or a batch of test UUIDs for seeding a database, mocking API responses, or assigning temporary unique IDs during development.
Common errors
A password rejected by a site's own password rules despite looking strong usually means it hit a length cap or a character-set restriction that site imposes - check the generator's character options against what that specific form actually allows.
Frequently asked questions
Are these passwords actually random, or could they be predicted?
Every character choice and the final shuffle use crypto.getRandomValues() - the Web Crypto API's cryptographically secure random source - rather than Math.random(), which is not safe for anything security-sensitive since its output isn't guaranteed unpredictable. Nothing generated here is transmitted or logged anywhere.
What makes a UUID v4 different from a sequential ID?
A v4 UUID is 122 bits of randomness formatted into the standard 8-4-4-4-12 hex layout - collisions are astronomically unlikely without any central coordination, which is exactly why it's the standard choice for distributed systems that need unique IDs without a database round-trip to check for duplicates.