Got a security warning or leaked a key? Start here
Short guides for the moment something goes wrong: a scary email from Firebase, a Supabase advisor warning, a key pushed to GitHub or an exposed .env file. Each one starts with the answer, then the urgent steps, then the proper fix.
Free, no signup. We only read what your site already shows every visitor.
Your Cloud Firestore database has insecure rules: what to do
The Firebase warning email, explained, with rules you can paste and deploy.
Open →Firebase Realtime Database insecure rules: how to fix them
Lock a Realtime Database that anyone can read, with rules and the deploy command.
Open →Supabase "RLS disabled in public" warning: how to fix it
Enable Row Level Security and write safe policies for the Supabase advisor warning.
Open →Supabase service_role key exposed: what to do now
Rotate a leaked admin key, check for damage and keep it server-side.
Open →I leaked an API key on GitHub: what do I do?
Revoke first, then clean the history and turn on push protection.
Open →Stripe secret key exposed: what to do right now
Roll a leaked sk_live key, review activity and move to restricted keys.
Open →OpenAI API key leaked: how to revoke it and stay safe
Revoke an exposed OpenAI key, check usage and proxy AI calls through your server.
Open →.env file exposed on my website: how to fix it
Block public access to .env, fix the web root and rotate what was inside.
Open →.git folder exposed on my website: how to fix it
Block /.git, stop deploying it and rotate secrets from the history.
Open →Next.js middleware bypass (CVE-2025-29927): am I affected and how to fix it
Patch the Next.js middleware auth bypass and stop relying on middleware alone.
Open →Lovable security warning: what it means and how to fix it
Understand the security issues Lovable reports and fix the Supabase side.
Open →Missing security headers: how to add them to your site
Copy-paste config for HSTS, CSP, nosniff and more in Next.js, nginx and Apache.
Open →