Integration Mode: use RedirHub without changing your DNS

Integration Mode connects a domain to RedirHub without changing its DNS or adding any DNS record. Your site keeps its DNS, hosting and HTTPS certificate. Your own platform downloads the domain's rules from RedirHub, serves the redirects, short links and QR code links you manage in the dashboard, and reports every visit back, so the domain shows up in the same dashboard and analytics as a DNS-connected domain.

It is made for the cases where pointing DNS to RedirHub is not an option: DNS sits with IT or a client, the domain already serves a live website, or you want short links and redirects on your main domain next to your own pages.

How it works#

1. Rules file. RedirHub publishes a plain-text rules file for every domain connected this way. Your platform downloads it about once a minute (Caddy can also get a push within a second or two), so a change in the dashboard goes live without a redeploy.
2. Check path. Your platform answers /_redirhub/check on the domain. The first correct answer proves the domain is yours and connects it; RedirHub keeps calling it to see whether your platform runs the latest rules.
3. Redirects. Exact rules redirect before your site's own routes. A catch-all only answers URLs your site returns 404 for, so a working page is never taken over.
4. Reports. Every redirect is reported back in the background, without delaying the visitor. Where the platform supports it, the 404s your site returns are reported too, so broken links show up after a migration.

If RedirHub can't be reached, your platform keeps the last rules it downloaded and keeps redirecting. The integrations fail open: an error never breaks a page.

Supported platforms#

• Cloudflare Workers: a Worker in front of your origin. Open source: redirhub/cloudflare-redirects.
• Next.js (on Vercel or self-hosted with next start): runs in your proxy or middleware. Open source: redirhub/nextjs-redirects.
• Caddy: a Caddy module for your own servers, with on-demand HTTPS for the hostnames in your rules. Open source: redirhub/caddy-redirects.

The rules file format is open, so anyone can write a client for another platform: redirhub/integration-spec.

Set it up#

1. In the dashboard, add the domain under Hostnames and choose Connect through your own platform. No DNS record is needed.
2. Pick your platform. The dashboard shows the rules address and your workspace's integration key, and a prompt with both already filled in.
3. Paste the prompt into your AI coding agent (Claude, Cursor, ChatGPT and others) or follow the platform's README by hand. Keep the integration key secret: it goes in an environment variable or secret, never in public code.
4. Deploy. The domain switches to Connected as soon as the check path answers.

DNS connection or Integration Mode?#

Use the DNS connection when the domain only redirects (a spare domain, an old domain after a move): RedirHub's edge serves it and handles HTTPS for you. Use Integration Mode when the domain already runs a website you want to keep, or when you can't change its DNS.

What Integration Mode doesn't do#

• The HTTPS certificate stays with your platform; RedirHub doesn't issue one for the domain.
• Each domain holds up to 50,000 redirect rules. Wildcard domains are not supported.
• Custom HTML, frame redirects, password protection and paused or expired links are not applied. A link with several destinations uses its main destination.

Integration Mode is included in Core, Pro and Enterprise. Redirects served this way count toward the plan's monthly visits, the same as redirects served by RedirHub's edge.