Web security terms, explained
Short, accurate answers to "what is it, am I affected, how do I fix it". Each page says honestly which of our scans can check the issue and which cannot.
Free, no signup. We only read what your site already shows every visitor.
XSS
Untrusted text runs as script in your visitors' browsers.
Read →CSRF
Another site makes a logged-in user's browser act on your site.
Read →SQL injection
User input rewrites your database query.
Read →CORS
Which other sites a browser lets read your API responses.
Read →Content Security Policy (CSP)
A header that limits which scripts and resources a page may load.
Read →HSTS
Tells browsers to use only HTTPS for your domain.
Read →Clickjacking
Your site hidden in a frame so users click without knowing.
Read →Open redirect
Your site forwards visitors to any address in a URL parameter.
Read →SSRF
An attacker makes your server fetch an address they pick.
Read →IDOR
Changing an ID in a request exposes another user's data.
Read →Supabase Row Level Security (RLS)
Postgres policies that decide who can read and write each row.
Read →Firebase Security Rules
The rules that decide who can read and write Firebase data.
Read →API key leak
A secret key ends up in public code, a repo or a bundle.
Read →JWT
A signed token that proves who the user is.
Read →Exposed source maps
Public .map files hand over your original front-end source.
Read →OWASP Top 10
The ranked list of the most critical web application risks.
Read →