One missing s
A plaintext scheme carrying a password, which is the typo that sends credentials in the clear
redis://default:s3cret@redis.example.com:6380/2
Paste a Redis connection URL to see exactly what a client will do with it: which host and port, which database, which credentials, and whether the connection is encrypted.
Or drop a file anywhere on this panel. Nothing is uploaded: the analysis runs in this tab.
The answer appears here
Paste on the left and press Parse. Nothing leaves this tab.
Nothing else to flag.
No formatting problems, and nothing the rules object to. Worth remembering what that covers: this reads the file you pasted, not the account or cluster it will be applied to.
No finding matches that filter.
Real input you can load into the tool above. Each one shows a different thing going wrong, because that is what the tool is for.
A plaintext scheme carrying a password, which is the typo that sends credentials in the clear
redis://default:s3cret@redis.example.com:6380/2
The path component is a database index, not a path
rediss://cache.example.com:6380/3
These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.
The TLS scheme is `rediss://` with two s. The typo is invisible, produces a working connection, and sends the password across the network in the clear.
Instead:Check the scheme has two s wherever a password is present.
Unencoded, the URL parses into something else entirely rather than failing, so the client connects to the wrong host or database with no error.
Instead:Percent-encode the password, or supply it separately where the client allows it.
It is the database index. `redis://host/2` means database 2, and Redis Cluster supports database 0 only, so any other index cannot work against a cluster.
Instead:Leave it off unless you mean a specific database.
The scheme is registered with IANA and the shape is stable, but several parts behave differently from the HTTP URLs everyone's intuition comes from.
redis://host/2 means database 2, not a resource called 2. Redis ships with sixteen databases numbered 0 to 15, and anything higher needs the databases directive raised. Redis Cluster supports database 0 only, so a URL carrying any other index cannot work against a cluster.
A single s is the ordinary plaintext scheme. The typo is invisible, produces a working connection, and sends your password across the network in the clear. Nothing in Redis will ever mention it, because from the server's point of view nothing is wrong.
redis://:secret@host is the pre-ACL form and is still what most clients expect for a server using requirepass. With Redis 6 ACLs there is also a username, and the default user is literally called default. A username with no password authenticates nothing.
A connection string lands in shell history, process listings, container environment inspection, crash dumps and any log that records configuration. A password containing @ or / that was not percent-encoded is worse still: the URL parses into something else entirely rather than failing, so the client silently connects to the wrong host or database.
It parses the string and never connects, so it cannot tell you whether the host resolves, whether the port is open, whether TLS is actually configured on the server, or whether the credentials are correct. It also cannot know which query parameters your particular client supports, since those are a client convention rather than part of the scheme.