CORS Response Validator
Validate a saved Access-Control response. Check the declared origin, credentials and recorded preflight method and headers locally.
Check CORS on a Saved Catalog Response
Paste response header lines or a capture with HTTP status lines. For recorded preflight checks, include the preflight status and declare the request method and header names.
A saved response uses its last final block by default. Headers and results stay on this device.
CORS Response Validator: how to use it
- Paste saved response header lines or a capture with HTTP status lines.
- Enter the declared request origin and credentials mode. For a recorded preflight, supply the request method and header names.
- Check the findings and selected response block. Copy or download the JSON report.
Limits and notes
Use up to 50,000 characters and 300 fields in the selected response. Evaluates the supplied scenario using common Fetch CORS checks. Browser context and other responses in an exchange may affect the outcome. The tool uses saved evidence on this device.
How your privacy works →CORS Response Validator: common questions
Is the request URL the same as the origin?
Enter the requesting page’s origin, for example https://catalog.example.com. The server’s URL and resource path are separate.
Why does a wildcard origin fail with credentials?
A credentials-included request requires an exact matching serialized origin and Access-Control-Allow-Credentials with the exact value true.
What does a passing preflight tell me?
It tells you the selected preflight response matches the declared input fields. Assess the separate actual response to check response sharing.