Fake Database Connection String Generator
Documentation-safe DSNs
Produces the familiar scheme://user:password@host:port/database shape you paste into .env examples, README snippets, docker-compose files, CI config, and mock app settings. Pick PostgreSQL, MySQL, MongoDB, or Redis and each URI uses the correct scheme and default port.
Hosts are limited to reserved example.com, example.net, and example.org subdomains or the localhost and 127.0.0.1 loopback addresses, and the passwords are obvious fixtures — never real or working credentials.
When to use this tool
Reach for a fake connection string when docs, demos, or tests need a realistic-looking DSN without exposing a real database. The schemes and default ports mirror what PostgreSQL, MySQL, MongoDB, and Redis clients expect, so examples read as authentic while staying obviously fictional and safe to commit.
How the randomness works
The user, database, and password segments are assembled from crypto.getRandomValues draws, with the password using the URL-safe Base62 alphabet so it never needs escaping. The host is always a reserved example.* subdomain or a loopback address. Generation runs entirely in your browser and nothing is sent over the network.