Tools

CORS tester

Send a live cross-origin request from this browser tab and see exactly what a page on this origin may read. The request goes from your browser straight to the URL you enter; nothing is proxied, stored, or logged.

What the live request proves

The header checker answers a static question about pasted headers. The tester answers the live one: can a page on this origin read a response from that URL right now. It sends the method and headers you choose from this browser tab with no cookies, then reports the real status and the headers and body the browser exposes to JavaScript. It always runs from cors.dev, so a server that allows only your own app's origin refuses it by design.

Browsers hand JavaScript the same TypeError for every failure. To tell a CORS refusal from a network failure, the tester follows a refusal with one plain HEAD request to the same URL and, if that fails too, asks Cloudflare's public DNS whether the hostname exists. For a static read of headers you already captured, use the CORS header checker.

When you cannot fix the server

If the API is yours, the fix lives on your server: return the right Access-Control-Allow-Origin value and the tester reports a readable response. If the API belongs to someone else, no browser setting or client-side trick can change their policy. The response has to travel through a path that adds permission.

That path is either a small backend you own or a managed proxy. cors.dev runs one: keyless GET and HEAD requests to any public host through https://proxy.cors.dev/, and a free account adds Connections, publishable keys, and an activity view. Compare the proxy and backend options.