Skip to content
FlexibleToolsAI
Security Toolkit · Free, Nothing Stored

CORS Checker

See how a URL responds to cross-origin requests. The checker sends a GET with the Origin you choose and a real OPTIONS preflight with Authorization, then explains the Access-Control headers — and flags dangerous setups like reflecting any origin with credentials.

Enter the endpoint URL and the Origin to test (an unrelated origin by default, to catch servers that trust everyone). Our server sends a simple GET with that Origin and a preflight request, and shows the Access-Control-Allow-Origin, -Credentials, -Methods and -Headers responses with a plain-English verdict for each.

the site that would make the request

Instant Results

Live checks in seconds

Nothing Stored

No logs of what you check

No Sign-Up

Free, no credits or email

What Does CORS Checker Do & How Does It Work?

Enter the endpoint URL and the Origin to test (an unrelated origin by default, to catch servers that trust everyone). Our server sends a simple GET with that Origin and a preflight request, and shows the Access-Control-Allow-Origin, -Credentials, -Methods and -Headers responses with a plain-English verdict for each.

How to Use CORS Checker (Step-by-Step)

  1. 1Enter the API or page URL.
  2. 2Set the Origin you want to test (e.g. your frontend).
  3. 3Choose the method for the preflight.
  4. 4Read the findings for both requests.

What CORS controls

CORS decides whether JavaScript running on one origin can read responses from another. Without Access-Control-Allow-Origin, browsers block the read — the safe default. Allow-Origin: * lets any site read public data but never with cookies.

The dangerous misconfiguration is reflecting whatever Origin the request sends and also returning Allow-Credentials: true. Then any website a logged-in user visits can read their private data from your API.

Fixing CORS errors

Allow specific origins from an allowlist, add Vary: Origin when the header depends on the request, answer OPTIONS preflights with the methods and headers you use, and only enable credentials when needed. CORS doesn't stop requests from being sent — protect state-changing endpoints with CSRF defences too.

Frequently Asked Questions

Why test with evil.example?

An unrelated origin reveals whether the server trusts any origin. Test your real frontend origin too, to confirm legitimate requests work.

Why does my browser still show a CORS error?

Check the preflight: if OPTIONS returns an error or lacks Allow-Methods/Allow-Headers for your request, the browser stops before sending it.

What do you do with the domains and URLs I check?

Our server performs the lookup once and returns the result to your browser. We don't store the addresses you check or build a history. Private and internal addresses are blocked.

Explore More Free Browser Tools

View All 290+ Tools Directory →

All tools run client-side in your browser with zero data uploads, no sign-up, and zero tracking. Discover other popular converters and calculators:

Cryptographic Standards & Zero-Knowledge Privacy Architecture

CORS Checker is engineered to strict security and cryptographic specifications — guaranteeing zero data leakage, zero backend telemetry, and audited implementation:

  • 1. 100% Zero-Knowledge Client Execution: Passwords, private keys, hashes, and API tokens are computed strictly in your browser's local memory via Web Crypto API (SubtleCrypto) and audited @noble/hashes. Nothing is ever sent to or stored on our servers.
  • 2. Official RFC & NIST Compliance: Adheres to established security specifications including RFC 2104 (HMAC), RFC 6238 (TOTP), RFC 9106 (Argon2id), RFC 4122 (UUID v4), and FIPS 180-4 (SHA family).
  • 3. Memory-Hard & Brute-Force Resilient: Incorporates robust hashing algorithms (Argon2id, bcrypt, PBKDF2) with configurable memory and iteration costs to defend against GPU-accelerated cracking.
  • 4. Transparent & Inspectable: Every cryptographic calculation occurs visibly in client-side JavaScript. You can verify through your browser's Network tab that zero outbound requests are made with your sensitive inputs.
  • 5. SSRF-Safe Diagnostic Probing: For internet-facing checks (SSL certificates, DNS records, HTTP security headers), handshakes run through isolated proxies that never log or store queried domains.

Suggest a Feature or Improvement for CORS Checker

Need custom options, higher limits, or extra format support? Let our engineering team know!