Protego field desk
All tools

CORS Misconfiguration Checker

Check a public endpoint for risky cross-origin response policies.

Quick answer

Test one public URL with three credential-free GET requests carrying different Origin headers. The checker reviews the response policy for arbitrary, null and target-host lookalike origins. Findings matter most when sensitive responses can be read with credentials. Results describe a point-in-time observation, not a site-wide security guarantee.

Protego requests this URL without credentials. Use a public endpoint you are authorized to test. Do not include tokens or secrets in the URL.

Check the rest of your website

Use the free vulnerability scanner to review related website configuration.

Free website vulnerability scan
  • TLS and certificates
  • Security headers
  • Cookie flags
  • SPF and DMARC
  • Exposed paths
  • WAF detection

Frequently asked questions

What does this CORS checker send?

Up to three GET requests with an arbitrary reserved .invalid origin, null, and a target-host prefix lookalike under .invalid. No cookies, authorization headers or request bodies are sent. Response bodies are cancelled. Only test public endpoints you are authorized to check.

Does wildcard origin with credentials expose account data?

Browsers reject a credentialed CORS read when Allow-Origin is * even if Allow-Credentials is true. It is a configuration error, not evidence that an attacker can read an account. Arbitrary exact origin reflection with credentials is more concerning.

Why is the null origin risky?

Sandboxed documents and some local contexts serialize their origin as null. Allowing null with credentials can grant an untrusted document access to sensitive responses. Whether an attack works depends on the endpoint, authentication and browser cookie policy.

Is allowing any origin always a vulnerability?

No. Public resources may intentionally allow non-credentialed cross-origin reads. Sensitive credentialed data needs a narrow trusted-origin policy and independent authorization. This test does not sign in, inspect data or prove exploitability.

Does this test preflight requests or follow redirects?

No. It sends GET only and stops on a redirect to stay within three requests. Test the final public URL separately. Allow-Methods, Allow-Headers and Max-Age are reviewed if advertised, but a full OPTIONS preflight policy is not tested.

What should I fix after a finding?

Use exact trusted-origin comparisons and enable credentials only where needed. When the response changes by Origin, include Vary: Origin for caches. Restrict advertised methods and headers to application needs. Repeat checks on authenticated endpoints in your own controlled environment.

Can a clean result prove my site is secure?

No. This is one URL at one time, without credentials. CDN behavior, error pages, other endpoints and authenticated responses can differ. A blocked request or failed lookup yields no verdict. CORS is a browser read policy and does not replace CSRF defenses.

References

Rules checked against these sources on November 16, 2026.