Free CORS Misconfiguration Tester
Test any URL for dangerous CORS misconfigurations · origin reflection, wildcard-with-credentials, and null-origin acceptance that can leak authenticated data.
Free account required to run the check. What you type here is kept through sign-in.
How to use it
- Enter the URL of an API endpoint or page, for example https://api.example.com/me.
- Run the test. SimplyScan sends requests from its servers with six different Origin headers, plus a preflight request.
- Read the verdict and the line for each origin: what your server answered and whether that answer is safe.
- Replace any reflected or null origin with a fixed list of the sites you trust, then test again.
Example
An API that trusts whatever site asks: the classic credentialed reflection.
Input
https://api.example.com/me
Result
Grade F · Critical CORS misconfiguration Origin: https://attacker.example (arbitrary) Access-Control-Allow-Origin: https://simplyscan-cors-probe.example Access-Control-Allow-Credentials: true Reflects an arbitrary attacker origin AND allows credentials Origin: null No CORS header returned for this origin. Safe.
What the verdicts mean
- Safe (grade A)
- Either no CORS header comes back for foreign origins, or the server always answers with one fixed origin. Browsers then block other sites from reading the response.
- Reflects an arbitrary origin
- The server copies whatever Origin it receives into Access-Control-Allow-Origin, so it trusts every website. This gets grade C on its own.
- Reflection with credentials (grade F)
- Any website a signed-in user visits can read this endpoint's responses with the user's cookies. That leaks account data.
- Accepts the null origin
- Sandboxed iframes and data: URLs send Origin: null, so trusting null is almost as open as trusting everyone.
- Wildcard *
- Fine for truly public data. Browsers refuse * together with credentials, but sending both usually means the configuration was never thought through.
- Look-alike origins
- The test also sends evilexample.com-style and attacker.example.com-style origins to catch prefix and suffix checks that match more than they should.
Use an allow-list
Supabase Edge Function
const ALLOWED = new Set(["https://example.com", "https://app.example.com"]);
function corsHeaders(req: Request) {
const origin = req.headers.get("Origin") ?? "";
return ALLOWED.has(origin)
? { "Access-Control-Allow-Origin": origin, "Vary": "Origin" }
: {};
}Express (cors package)
app.use(cors({
origin: ["https://example.com", "https://app.example.com"],
credentials: true,
}));Go deeper
Page updated
Frequently asked questions
What CORS problems does this find?
It sends requests with crafted Origin headers and inspects the response: reflecting any origin back, allowing '*' together with credentials, accepting a 'null' origin, or reflecting arbitrary origins with Access-Control-Allow-Credentials · all of which can expose authenticated data to malicious sites.
Why can't a browser tool do this itself?
Browsers block JavaScript from setting the Origin header and from reading cross-origin responses, so the request is made server-side from SimplyScan with the chosen Origin, and the raw CORS response headers are reported back to you.
Is CORS a security feature or a restriction?
Both. Browsers block cross-site reads by default, and CORS headers are how your server relaxes that. A misconfigured header switches the protection off.
Does CORS protect my API from scripts and servers?
No. CORS only governs browsers. Every endpoint still needs real authentication and authorisation checks.
Want the full picture?
This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.
Run a full security scanRelated tools
Exposed Files Scanner
Check whether your site accidentally exposes .env, .git/config, backup archives, or other high-risk files.
Supabase RLS Checker
Discover tables advertised by your public API and check whether anonymous reads return rows.
SSL Checker
Instantly verify a site's SSL certificate · trusted chain, hostname match, issuer and days until it expires.