Cloud & Platform

Database Connection String Parser

Parses any of the three common connection string styles and never puts the password in the output.

Loading the tool…

Processing happens locally in your browser. What you paste or load is processed by this page and is not uploaded to a server. Nothing is stored unless you use a control that says it stores something, and you can clear anything this site has kept from the privacy page.

How to use this tool

  1. Paste your connection strings, one per line. JDBC, URI and ODBC key-value styles are all recognised.
  2. Select Parse strings.
  3. Check the TLS warning. If nothing in the string asked for encryption, the driver most likely connected in plaintext.
  4. Copy the result into your ticket if you need to — the password has been replaced with dots.

What connection string parser does

A connection string packs six or seven things into one line in one of three incompatible syntaxes, and the thing you usually need from it is the one part you cannot safely show anyone. So the password is replaced with dots in every output here, which makes the result safe to paste into a ticket, a chat or a runbook — the parsing itself happens entirely in your browser, so pasting the string here is not the disclosure either.

JDBC strings, scheme://user@host/database URIs and semicolon-separated ODBC key-value strings are all recognised, including multi-host lists and mongodb+srv. Every result is also checked for TLS: if nothing in the string asks for encryption, that is called out, because most drivers quietly default to plaintext when it is not requested and nobody notices until an audit does.

Frequently asked questions

The parsing runs entirely in your browser and nothing is transmitted anywhere, so the string does not leave your machine — and the password never appears in the output, only dots. That said, the safest habit is to redact it yourself before pasting anything into any tool, including this one. The redaction here exists so the result can be shared, not to make the input safe.

Because most drivers default to an unencrypted connection when nothing asks for one, and the request has to be explicit — sslmode=require for PostgreSQL, encrypt=true for SQL Server, tls=true for several others. A string with no such parameter usually means the traffic is in plaintext, which nobody notices until an audit or a packet capture does.

It tells the driver to look the real host list up in DNS rather than read it from the string. That is why such a string names one hostname and connects to a replica set of three — and why the endpoints your client actually talks to are not visible here. It also implies TLS by default, unlike the plain mongodb scheme.

Three: JDBC strings beginning jdbc:driver://, URI style with scheme://user:password@host:port/database and a query string, and semicolon-separated key=value strings as used by ODBC and ADO.NET. Multi-host lists are split out individually, which is useful for confirming a replica set or a failover partner is where you think it is.