2026-11-18 · Daily security tips
Where do your Supabase login links send people?
Two Supabase Auth settings are easy to leave as they were on day one. The Site URL is still http://localhost:3000, so confirmation and password reset emails send real users to localhost. Or the Redirect URLs list has a broad wildcard like https://*.vercel.app/**, which matches every Vercel project, including ones strangers own. A login link can then hand a user, and their sign-in token, to a site you don't control.
Check: in Supabase, open Authentication, then URL Configuration. Is the Site URL your live domain? Does any redirect entry start with https://*. on a shared host like vercel.app or netlify.app?
Fix: set the Site URL to your real domain and list exact production paths, like https://yourapp.com/auth/callback. For Vercel previews, use the pattern from Supabase's docs that includes your own team slug: https://*-yourteam.vercel.app/**.
Is your live site exposing something like this?
The free quick check looks at what your site already serves publicly: secret keys in your JavaScript, open /.env files and /.git folders, Supabase tables readable with your public key, and missing security headers. No sign-up needed.
No app handy?
No sign-up. Read-only public-resource and protocol metadata checks. No model prompts or tool execution. Scan only sites you own or are allowed to test.
Run on every deploy or use from Cursor / Claude Code via MCP →