Web & TLS
CORS inspector
Compare same-origin, untrusted and null-origin GET responses. You can add one fixed OPTIONS preflight; no PUT request, credentials or request body is sent.
How to use CORS inspectorSteps, privacy & next steps
Compare cross-origin response policies using controlled, uncredentialed probes.
Run this check
- Enter the exact public URL and confirm permission.
- Leave preflight off for the three GET probes, or explicitly include the fixed OPTIONS diagnostic.
- Review same-origin, untrusted and null-origin responses against your intended browser clients.
What you need
- An approved public HTTP(S) endpoint. Optional preflight advertises PUT and content-type only.
Your input & privacy
The target receives three bounded GETs and, only when selected, one fixed OPTIONS request. Results are temporary.
Read the result
Compare the sampled policies and Vary behavior. Validate intended and rejected requests in an authorized browser workflow before changing CORS.
Keep in mind
- No PUT, request body, credentials or browser exploit is sent.
- Reflected origins can be intentional on public endpoints. Policy observations do not prove access to private data.