RedirectIQ

Create a Real Edge Redirect in Seconds — No Server, No Account

·4 min read

Enter any URL below. We'll create a real redirect — served from Cloudflare's global edge network — and hand you a working link you can click and share right now. No account, no credit card, expires in 24 hours.

That redirect just went live globally. It's a real 302 response, not a simulation — if you share that link with someone in Tokyo, they get redirected from a Cloudflare data center near Tokyo.

Why stateless, and what that gets you

Most demo features store something: a database row, a session, a record that needs cleaning up. We didn't do that here, and it wasn't laziness — it was a deliberate security choice.

The redirect link you just created contains everything needed to serve the redirect. Your destination URL and a 24-hour expiry are encoded into the token itself, then signed with a secret key using HMAC-SHA256. When someone visits the link, the Cloudflare Worker at the edge reads the token, verifies the signature, checks the expiry, and issues the redirect — all without touching a database or making a network call to any origin server.

What this means in practice:

  • Nothing to breach. There's no database storing your test URLs. Nothing was written anywhere when you created that redirect. An attacker who compromised our infrastructure would find no table of "URLs people tested."
  • Nothing to fake. The signature makes it cryptographically impossible to forge a valid redirect to a different destination or extend the expiry. Every character of the token is covered.
  • Nothing to clean up. The 24-hour expiry lives inside the token. When time runs out, the link simply stops working. No cron jobs, no TTL records, no orphaned rows.
  • Can't be turned against internal systems. The API that generates tokens rejects private IP ranges, localhost, and link-local addresses. You can't use this feature to probe services that aren't on the public internet.

The result: we can offer this publicly, without authentication, at zero ongoing cost — because there's genuinely nothing stored to abuse.

How production redirects work differently

The demo is intentionally minimal. Production RedirectIQ gives you permanent, manageable redirects with the full feature set:

  • 301 or 302 — permanent or temporary, your choice per rule
  • Path passthrough — /old/page automatically forwards to /new/page
  • Click analytics — every redirect hit logged with device, country, referrer, and timestamp
  • SSL auto-provisioned — connect any domain with a single CNAME, we handle the certificate
  • Instant deploys — rule changes go live globally within seconds, no deployment pipeline

Automate it with the API

Everything the dashboard does, the API does. If you want to generate redirects programmatically — from a CMS, a CI/CD pipeline, or your own application — it's one POST:

POST https://app.redirectiq.com/api/v1/rules
Authorization: Bearer YOUR_API_KEY

{
  "domainId": "dom_abc123",
  "matchPath": "/old-page",
  "destination": "https://example.com/new-page",
  "redirectType": "301",
  "pathPassthrough": false,
  "queryPassthrough": true
}

The rule deploys to Cloudflare's edge within seconds. What you just did manually above, your application can do at scale. Full reference at redirectiq.com/developers.

Why we exist when Cloudflare is free

A fair question: *RedirectIQ is built on Cloudflare. Why not just use Cloudflare redirect rules directly?*

You can. Cloudflare's redirect rules are free and genuinely good — we use them ourselves. But they have real limits:

  • No dashboard for non-technical teams. Marketers creating vanity URLs and SEO teams managing migrations don't want to learn Cloudflare's zone configuration.
  • No analytics. Cloudflare redirect rules don't tell you how many times a rule fired, where traffic came from, or whether your link equity is flowing to the right pages.
  • No multi-domain management. Managing redirects across 10 or 50 domains from separate Cloudflare zone dashboards is painful.
  • No API for rule management. You can't programmatically create or update Cloudflare redirect rules without a full Terraform setup.
  • Requires Cloudflare nameservers. If your domain is at Namecheap or GoDaddy, you'd have to migrate DNS to Cloudflare first.

RedirectIQ adds the product layer on top: the dashboard your whole team can use, analytics that answer real SEO questions, and an API that fits how development teams work.

Start free → — the Hobby plan is free forever with one domain and 10 redirect rules. No credit card required.