Hi and Welcome

Sometimes one example isn't enough.

AnotherExample gives developers a real, controlled second origin for debugging CORS and other browser integration problems.

example.com and example.org are reserved by IANA for documentation. AnotherExample provides a stable, real HTTPS origin you can use for CORS, cookies, redirects, and integration testing.

Featured tool

CORS Debugger

Compare your failing browser request against a controlled second origin, see where the behavior differs, and understand what to investigate next.

Open CORS Debugger →

Try the endpoints

Run a real cross-origin request from this page and inspect the result.

Ready.

Endpoints

ANY /api/echo

Returns method, headers, query parameters, body, IP, and timestamp.

ANY /api/cors/open

Permissive CORS with Access-Control-Allow-Origin: *.

ANY /api/cors/credentials

Reflects the request Origin and enables credentialed CORS testing.

ANY /api/status/:code

Return an intentional HTTP status from 200–599.

ANY /api/delay/:ms

Delay a response by up to 10,000 milliseconds.

GET /api/redirect

Test 301/302/303/307/308 redirects to safe predefined targets.

GET /api/cookie/set

Set a test cookie with Lax, Strict, or None SameSite behavior.

GET /api/cookie/check

See whether the browser sent a Cookie header back.

GET /api/health

Simple service health check.

Quick examples

fetch('https://anotherexample.com/api/cors/open')
  .then(r => r.json())
  .then(console.log);

curl https://anotherexample.com/api/status/418

curl https://anotherexample.com/api/delay/1000

curl -i 'https://anotherexample.com/api/redirect?target=example&status=302'

Cookie testing

/api/cookie/set?sameSite=Lax
/api/cookie/set?sameSite=Strict
/api/cookie/set?sameSite=None
/api/cookie/check
/api/cookie/clear

Use test data only. Request-inspection endpoints may reflect headers and bodies. Never send production passwords, API keys, session tokens, personal data, or other secrets.