Check a Postgres connection string
Paste a Supabase or Neon URL. You get what each part means (pooler or direct, session or transaction mode, port 5432 or 6543, sslmode), the mistakes that cause most connection errors, and pg_dump and psql commands that match it. The string never leaves your browser.
Tired of juggling pooler ports?
Scribase runs the Supabase API with Neon-style branching on one project, $25 a month flat. Idle projects scale to zero instead of pausing, and supabase-js keeps working with a new URL and key.
Questions people ask
Is my password sent anywhere?
No. The checker is plain JavaScript that runs in this tab. It makes no network request, does not put the string in the URL, and stores nothing. Commands show [YOUR-PASSWORD] unless you tick the box.
What is the difference between port 5432 and 6543 on Supabase?
On the shared pooler host, 5432 is session mode (each client keeps a server connection; prepared statements and pg_dump work) and 6543 is transaction mode (connections are shared per transaction, made for serverless, no prepared statements). The direct host db.<ref>.supabase.co uses 5432.
Why do I get "Tenant or user not found" on Supabase?
The shared pooler needs the user as postgres.<project-ref>. A plain "postgres" user only works on the direct host.
Which Neon string should pg_dump use?
The direct one, without -pooler in the host. Neon pooled connections run PgBouncer in transaction mode, which breaks the SET statements pg_dump uses.