Free tools that run in your browser. Use any tool without an account.

Favourites Cart
Sign in
Join free

CORS Tester

browser check

  • Free
  • Nothing stored
  • No account needed

This tool checks, from your browser, whether a URL allows cross-origin requests. It sends one live request (for example a GET or OPTIONS preflight), reports readable headers and gives a curl command.

Fetches public data to give your answer. We do not keep your inputs. Report a problem
Advertisement

About CORS Tester

This is a browser-side CORS tester you run in your own tab. You use it to confirm whether an API or URL actually lets browser scripts read its responses. The tool sends the request from your browser with the HTTP method, custom headers and cookies you choose. It reports whether the browser allowed the page to read the response, shows the preflight OPTIONS step when applicable, and lists which response headers are readable by JavaScript. It also prints a curl command you can run to inspect the raw response headers. FreeToolr does not receive or store the request or response because the request goes directly from your browser. This makes the result reflect your network and browser environment, which is more realistic than a server-proxied simulation for debugging client-side CORS problems.

How to use it

  1. 1Enter the target URL you want to test.
  2. 2Choose the HTTP method and add any custom request headers.
  3. 3Toggle credentials on or off to include cookies or auth.
  4. 4Run the test to send the live browser request and see results.
Advertisement

Worked example

Input: URL https://api.example.com/data, Method POST, Header X-My-Header, Credentials: on. Result: Browser sent an OPTIONS preflight. Server response lacked Access-Control-Allow-Headers: X-My-Header, so the browser blocked the actual POST. Readable headers: none. curl to inspect raw headers: curl -i -X OPTIONS 'https://api.example.com/data' -H 'Origin: https://freetoolr.com' -H 'Access-Control-Request-Method: POST' -H 'Access-Control-Request-Headers: X-My-Header'.

How it works

Checks from the visitor's browser whether an API or URL allows cross-origin requests: sends the request with the chosen method, headers and cookies, says whether the browser let the page read the response (including the preflight check when one is needed), lists the headers the page may read, and gives a curl command to see the raw CORS headersThe request goes straight from the browser; FreeToolr does not see itWorks in the browser with nothing to install

Source: MDN Web Docs - CORSWHATWG Fetch Standard. Last checked 7 November 2026.

What it is good for

  • Tests from your browser so results match your network and origin.
  • Shows whether the browser actually let JavaScript read the response.
  • Gives a curl command so you can inspect raw server headers yourself.
  • Cannot simulate a different calling origin the way a proxy can.
  • Results reflect your network and browser only, so behavior may differ elsewhere.
Advertisement

Questions people ask

What does this tester check?

It checks if a browser can read a cross-origin response. It sends the chosen request from your browser, runs any needed preflight, and reports which response headers are exposed to JavaScript.

Why does curl succeed but the browser fails?

Curl is a non-browser client and does not enforce CORS rules. Browsers block access unless the server returns the proper Access-Control-* headers. See MDN for details.

When does a preflight happen?

A preflight OPTIONS request runs when you use non-simple methods or add custom headers. If the server's OPTIONS reply lacks the correct Access-Control-Allow-* values, the browser will not send the main request.

How do I allow credentialed requests?

You must return Access-Control-Allow-Credentials: true and set Access-Control-Allow-Origin to the exact origin. Wildcard * is not allowed with credentials.

Does FreeToolr see my request or response?

No. The request is sent directly from your browser and not routed through FreeToolr. The site only runs client code in your tab to report results.

Why might results differ across countries or networks?

Network middleboxes or corporate proxies can block or strip OPTIONS or other headers. If you test behind a strict firewall results may differ from tests on other networks.

Help keep every tool free

FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.

Advertisement
Advertisement